How Do We Change from Individuals in Workgroups to Effective, Self-Organizing Agile Teams?

May 18, 2012 Matthew Badgley

A colleague of mine at VersionOne, Dan Naden who works to support the agile community, delivered several open questions from a recent Agilepalooza and asked for help answering. The one that jumped out at me and my experiences was, “How do we change from individuals in workgroups to effective, self-organizing agile teams?”

When I first started looking at this question, I was keying in on the word “individuals” and how individual team members impact our ability to come together and self-organize. The more ideas I got down on paper, the more I came to the conclusion that it is generally not the individual team members who prevent teams from self-organizing and becoming effective. It is usually everything but the individuals that prevent teams from self-organizing. Based on my experience where I’ve lived through an inability to self-organize to efficient self-organization — the individuals are usually never the primary blockers. The things that I’ve seen prevent teams from becoming effective and self-organized are:

  • Agile Teams Are Too Large. Teams that are too big will not self-organize; the team members are made insignificant because their contributions may or may not impact the overall product delivery… not to mention that when teams are too large you will usually see the Alpha team members overpower and control the non-Alpha team members. This is why the recommended team size is in the single digits (I’ve seen the range of 5-8) thrown out there. Not only does right-sizing the team make planning more efficient, but it also reduces the discussion circle, thus making it easier to share information and shorten the time to make and react to decisions that impact the team and the projects.
  • Workspace Challenges. Studies have shown that the right workspace leads to highly productive teams. In talking with many agile teams, it’s obvious that the wrong workspace fosters silos, as well as the perception of meetings purgatory. Ideally teams are co-located and share a workspace that is conducive to easy chair-spinning conversation. A workspace with plenty of whiteboards, private zones, and an information radiator will ensure a well informed, collaborative team. When this cannot be achieved, the use of rapid and personal communication tools can help teams. IRC chat, video chat and online collaboration tools are good ways for team members to collaborate.
  • No Vision. There are multiple layers of vision: company, product, project and team. Obviously a team can control their vision; however, it’s usually a product of the upstream visions. So if the leadership and stakeholders are not sharing the vision – and more specifically, if the team does not have a shared vision of what they are working toward – then there is nothing to bring the team together to achieve. A clearly communicated and shared provision gives a group of individuals a common goal to achieve; this improves focus on decision-making and a clear definition of what it means to be done.
  • The 3 Cs. And I’m not talking about Ron Jeffries’ Card, Conversation and Confirmation. I’m referring to a Command-and-Control Culture. It seems that even once a leadership team decides to adopt agile and they genuinely buy into agile values and principles, the individuals on the teams are still reluctant to take ownership for how to win (a.k.a. achieve). It’s not until the the team is forced to make decisions do they actually make decisions. Team members who have worked in a culture that’s historically command-and-control tend to have either a victim mentality in that they simply don’t believe change is happening, or they are simply scared to put their necks out there in fear of reprisal, even when there has never been a history of this kind of action. The only way that I’ve experienced changing this culture is to have the leadership share the vision and then leave the room (a.k.a. get out of the way). When the team has success, leadership shouts it from the rooftops. And when failure occurs, leadership should ensure that learning and accountability ensues — however, doing so from a distance.
  • Lack of Shared Trust. A core challenge that organizations (the whole organization) have is the inability to trust others to make decisions. This usually stems from two factors: (1) a command-and-control culture that is a result of traditional project/product failures, and/or (2) management team members who have been key to the organization over a period of years and have lived the battles — thus, they feel that because of their experiences they must be a part of the decision. Remember that trust can go both ways; if the teams don’t have that shared vision, then trust of those making decisions is surely lacking.

So how do we change from individuals in workgroups to effective, self-organizing agile teams? We give our teams the environment they need to be productive, provide a clear and shared vision, have leadership get out of the way (yet be there when needed) and finally, we celebrate our small wins and ensure that we learn from our failures. I’ll assume that this stuff sounds familiar; however, if it doesn’t, give the Agile Manifesto a read: I’m sure there are more organizational behaviors, and I’m certain that individuals impact our ability to self-organize. But I firmly believe that everyone has the ability to work as a self-organized team, and if they are empowered to do so, they will do it effectively.

Please let me know what you think. What are some organizational challenges you’ve experienced which have prevented teams of individuals from becoming effective, self-organizing teams? Or do you think the organization has nothing to do with it; it’s the individual team members?

The post How Do We Change from Individuals in Workgroups to Effective, Self-Organizing Agile Teams? appeared first on VersionOne Blog.

Previous Article
DevOps, the Agile Cadence and Modern Code Languages…an Opportunity for IT Optimization?
DevOps, the Agile Cadence and Modern Code Languages…an Opportunity for IT Optimization?

I had an interesting conversation with an IT executive around IT’s changing cadence.  We were talking about...

Next Article
Subversion Edge 3.0.1 Released
Subversion Edge 3.0.1 Released

As I detailed in the previous post, Apache Subversion 1.7.5 was released today and with that release it is ...