Self-Managing Teams?
One of the most important aspects of agile project management is the ability for teams to self-organize. But as Damon Poole writes in this post (http://agile.dzone.com/articles/the-use-self-managing-teams-ou), understanding exactly what that means can be a little difficult to say. Poole is committed to digging up some answers and to do so, he’s looking outside of agile and will report back with future posts on this topic.
From my own experience working in agile environments, the concept of self-organization has always been pretty clear (and its benefits have been just as clear). Because most agile frameworks or methodologies divide responsibilities through well-defined roles, there has never been any confusion. That is, the team is responsible for completing the work it agrees to in a given iteration and, therefore, must work together to determine how it will be completed. Poole wonders if this means that individual team members decide what tasks to tackle in addition to how and when. I think that self-organization entails all of those decisions. However, it’s important to point out that these decisions aren’t made independently by individual members of the team. It’s the team that self-organizes. Thus each member weighs in and, collectively, a consensus is reached. The benefits of this approach are obvious. It allows the team to take on more ownership of the work, thereby increasing their investment in its success. Managers, on the other hand, are relieved of their “babysitting” duties. Instead, they can focus on big picture concerns, such as release planning and prioritizing outstanding work.
How would you expand this definition of “self-organization”? Do you think Poole is making it more complicated than it really is or is he on to something? And do any of you have experience with self-organization outside of a dev team?