Tag: team building

  • Agile Patterns For Success – Team Work

    Agile Patterns For Success – Team Work

    I recently spent some time digging deep into the world of the Agile Manifesto and related methods for software development. This research included a look at agile patterns and anti-patterns. That is my focus in this article. There was an underlying theme that I kept coming across and do not see emphasized often enough. Spoiler alert, that theme is teamwork. There are many aspects of Agile that make it an effective way to approach software. However, the true power and ability to succeed comes from how it empowers the team.

    The Team Defined

    First, we need to be clear about how the team is defined in Agile. This is often the development team but can also include the scrum master and product owner. For our purposes in the article, we will focus on the development team. Many of these patterns make the entire team better. Nevertheless, I want to focus on the development team as they are the workhorses for our software project. These are the people that most impact success or failure when we build a solution.

    Unleash The Team

    It should be common sense that the biggest factor in any calculation is the one that becomes the largest focus. In sports, you hear about a player that “has to be stopped.” In politics and advertising, you hear about ket demographics. Businesses have flagship products and cornerstone customers. The odd thing is that we miss this concept when we consider teams. There may be an individual that is the most productive or effective on a team. However, the team is key, not just the individual. We have seen this played out in numerous contexts and multiple times over the years. Yes, a leader can make a sizable difference. On the other hand, most leaders are measured by how they motivate their team and increase productivity.

    The best leaders remove obstacles for their team. They reduce “red tape,” streamline processes, and empower team members. There is another way to view this. The best leaders unleash their team members to be the best team they can be. That takes us back to a focus on the team, not the leader. In case this example seems a bit abstract, managers are leaders.

    Professionals Are Professional

    The essential cog in the whole Agile Manifesto is that a development team is built of professionals. The members were hired because someone saw them as bringing value to the organization. Why would we throw that out once we place them on a team? It would seem to be common sense to trust these professionals to know how to do their job best. They know what their experience and skills are as well as where they work best.

    That leaves managers to listen to their staff and find ways to clear obstacles. It may seem trivial or lack glamour. On the other hand, it makes a statement that team members are valued as individuals. They are trusted to make the team the best it can be. Sure, there can be conflicts and a need for team members to learn how to work together. However, how often are we able to make other people like or trust each other? Managers are not miracle workers. Do not force employees into a hole. Let them define their role.

    Agile Patterns Are Not Suited For Everyone

    The second most important idea that needs to be understood in this pattern is that some teams are not suited to Agile. We need to have a team that has some experience, has self-awareness, and is driven to succeed. The team can develop these criteria as they go, but they need a starting point. A team full of similar or junior members will struggle. If there is not enough time for the members to branch out and differentiate themselves, Agile will not work. This concept goes back to that trust factor.

    When the team is trusted to “get the job done,” let them do the work. When you question whether the team can succeed, then do not burden them with Agile. They have to be able to make decisions and have confidence in those. Members that have no experience will rarely be able to do this. Instead, they will suffer from stress and lack of direction. Agile will be the worst direction to take.

    Agile patterns start and begin with the team. When you have a team that has the ability to over-achieve then turn them loose. Your trust and vote of confidence will be rewarded.

  • Resilience – A Strong Metric

    Resilience – A Strong Metric

    I was recently attending a conference (virtually, of course) that focuses on leadership and the related trends. Every year there is an idea or two that is the current hot topic. This focus has included familiar things like EQ and grit in the past years. One somewhat new theme this year was resilience. It is a trait we have all heard of, but it may be the next big thing to measure in getting the “best” employees. It may also be a metric you can use to determine how to improve yourself professionally and in your personal life.

    Resilience Assumes Challenges

    There is an old phrase, “hope for the best and plan for the worst.” It is safe to say that most of us accept that life will be full of challenges. It is hard to live very long without that being proven out. Therefore, our ability to react to and overcome obstacles is a critical factor in our success. You hear this concept in sports all the time. Every championship team had moments where they overcame a challenge and advanced on the path to becoming a champion. Every business’s success is the same. There are “overnight” successes that come faster than expected. However, most companies have a long and bumpy history that continues to the current moment.

    A Measure of Succes

    When you assume that every journey will include obstacles you must also accept that every journey has an opportunity for being derailed. There are substantial obstacles to face like the global shutdown due to COVID. However, there are more often smaller obstacles like a change in requirements or delays or miscommunication. We are required to overcome all of these to reach success. That logically flows to the idea of building a team that possesses resilience. This trait can come from individuals or it can be how the team members support each other. Sometimes there is not only safety in numbers, but also resilience.

    Positive Attitude

    The points made thus far are realistic, not pessimistic. Stuff happens. We can rail against it or bemoan our situation. Nevertheless, it is where we find ourselves. When we face these situations we can move forward or dwell on our misfortune. It seems obvious that moving forward is the best approach. However, we sometimes get stuck in these challenging moments. Resilient people take these sort of setbacks in stride. That is not only a valuable trait, it is also one that is relatively easy to see. Of course, levels of resilience can be difficult to measure, but it is not hard to see if someone possesses some level of it.

    Tactics and Approaches

    At the risk of being obvious, I think it is worthwhile to look at some of the things we see in resilient individuals or teams. There are actions that come from this trait and show that tendency to push forward. Here are some things to look for that can easily be worked into an interview (or self-reflection).

    • Acceptance – Moving requires action. Thus, the time spent on bemoaning a situation increases the time spent on it.
    • Blame – Looking for blame or a way to shift responsibility to others does not contribute to overcoming the obstacle.
    • Progress – Resilient people and teams move through options and avoid getting stuck on a single option as well as analysis paralysis.
    • Optimistic – It is hard to tackle a problem that you think is a lost cause. Resilience almost requires some element of a positive attitude or at least hope.
    • Analysis – One can spend too long analyzing a situation. However, resilient people have the ability to dig into a challenge in an unemotional way in order to see where things went wrong or look for ways out of it.
    • Roll With It – Much like acceptance, resilience often includes an ability to “shrug off” setbacks. Thus, challenges are assumed to exist and do not slow down teams or individuals with this trait. This factor points back to that “plan for the worst” concept.
    • Absolutes and Clarity – In my personal experience, I find that resilient people are less likely to talk in absolutes when talking about an approach. They leave open the idea that changes to their plans may (or will) be required.

    Nothing New Under The Sun

    All of us have been exposed to the resilient trait in people and teams. However, it can often be lost in the shuffle of other skills and attributes we look for in a team or hire. Therefore, it is worth our time to consider how it can factor into our approach and processes. There is no question that finding the right hire and building a team are complex and complicated feats. Likewise, we must avoid letting critical factors fall through the cracks.

  • Use Research Time To Improve Your Team

    Use Research Time To Improve Your Team

    The schedule of every IT team I have worked with is full.  There is always a steady stream of tasks to be done and technical debt to address.  This makes it easy for a manager or team lead to keep the whole team working at 100% (or more) day in and day out.  The problem with this full steam ahead approach is that it does not provide time for research of new technologies and skill development.

    Popular Example

    Google made news many years ago when they scheduled a day a week for employees to research and develop skills.  Their instincts were tapped to the tune of 20% of their time.  This is not a small investment in employees and the company itself.  As it turns out, Google has been a pretty successful company.  You can see all sorts of products that have come out of that investment in their employees.  Just take a little time and browse the Google labs projects.  Many of these came out of that time allotted for research.

    This example is a good one for us to consider in scheduling projects and workloads.  Google is known for their innovation and skilled workers.  Some of this success comes from the employees that have been hired, but some of the credit goes to management.  This success did not come overnight but what if your organization is considered world-class a few years from now?

    Running The Numbers

    I am not sure a 20% investment of time is going to pass most companies.  However, what is the cost of 10% of their time?  Specifically, consider the typical IT worker does not work forty hours per week.  Fifty or more is common.  That is a 25% increase in “typical” work week hours.  Therefore, you can look at the hours worked Monday through Thursday, and that often meets the typical forty-hour workweek.  Providing a “research on Fridays” benefit would effectively be doing so with “free” hours.

    The cost of blocking out half the day on Friday for research or personal projects would be easy to absorb by any organization.  It used to be built into a lot of consulting companies.  They had a little thing called “bench time” that was non-billable work while waiting on a contract.  That has disappeared from many companies as they try to improve margins and reduce costs.  However, that has a price.  I worked at a company that used their bench time to create commercial software products.  They could have turned those consultants loose as soon as the billable jobs ended.  Instead, they turned them into resources to create another revenue stream.

    Making It Work

    A program like this is not to be taken lightly.  There is plenty of room for abuse and missing the point.  I have found that a few ground rules and some structure will go a long way.  The first step is to build in some accountability.  This has a danger of becoming micromanaged, but it is too valuable to ignore.

    The level of accountability I am talking about is regular status and setting goals.  Since this is research work, then the goals can be flexible.  However, there must be something for the employees to aim for.  This can be a challenge for those that are not self-starters.  Help them lay out a plan for what they want to accomplish.  Just make sure that you push them to lead the discussion and work on something that appeals to them.

    When you have a team that is working for you and has a “bonus” each week of doing something to advance their career everyone wins.  The employees will get better while becoming more loyal to your organization.  There is a danger of employees growing to the point where they leave to start their own companies, but I would argue that as good publicity.  When you have an environment that fosters success, you will have a steady stream of people that want to fill those holes.