Skip to content

Nurturing the self-organizing team

September 2, 2008 by Artem

Picture courtesy of Budslife@Flickr
Scrum is a team empowerment framework. Scrum is an agile product management process that is based on the clear separation of what's and how's - Product Owner is responsible for what's, the development team is responsible for how's. This clear separation puts big bet on the team's ability to self-organize and figure out what exactly process and practices are best for it.

In my practice I've seen teams that gelled successfully, communicated with their customers frequently and were indeed able to self organize to whatever was needed for the frequent delivery of good software wanted by the customers. However, I also experienced teams that are struggling despite the credit from management. Their Product Owner (or Product Owner teams) were able to fix the product priorities for a sprint, they did explicitly tell that they want less features and more quality, they did allow their teams to work on architecture as much as they needed and still the quality wasn't on par with the expectations. The testers tested according to the scripts (and not according to what the user might want do), POs often were able to find obvious bugs during the sprint review demos, etc. Despite all the trust credit these teams just didn't self-organize.

Self-organization rarely happens on its own. Self-organization requires a common goal, boundaries and knowledge of some simple rules. Learning the self-organized team behaviors takes time and determination. The whole team has to walk a path from rookie to an expert and needs different styles of support from directing to delegating. A good Scrum Master or decent Agile coach rarely if ever tells the team to do whatever they want from the day one of the Agile adoption. Learning the new way of working takes time and in the very beginning the amount of guidance might be even bigger, than in the world of command'and'control. Coach just has to be clear that it is temporary and is needed only because the team is new to the process.

Scrum is an excellent process that suites many teams and by empowering them can lead to the truly amazing results even under the tough conditions. However, the ability to utilize high level of empowerment and self-organization isn't something to be developed overnight. It is something to nurture and to care about.

Comments

Maybe some teams will never

September 2, 2008 by pbielicki, 17 weeks 6 days ago
Comment id: 1829

Maybe some teams will never ever be self-organized no matter how long they will work together and how many agile/lean coaches they will meet? Isn't it something like marriage (I don't mean that team members should sleep together or something)? Isn't it that some people will work together pretty well and some other combinations will suck? It's about people (no training could change people's characters) and I think that finding a good agile team is difficult and if you find one you should treat it like a precious stone.

I was lucky to work with very good and very self-organizing teams but not always. I just come to the conclusion that as we all know not every engineer is a brilliant one the same can be applied to the teams. Not all teams could be self-organizing - not all teams could work together.

One more thing "Self-organization rarely happens on its own" - well, I was lucky then :)

Self-organization rarely happens on its own.

November 20, 2008 by Anonymous (not verified), 6 weeks 4 days ago
Comment id: 2017

"Self-organization rarely happens on its own."

What an odd sentence.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Best of AgileSoftwareDevelopment.com