InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Ensuring Success for Self Organizing Teams

Posted by Vikas Hazrati on Jul 07, 2009

Sections
Process & Practices
Topics
Adopting Agile ,
Agile
Tags
Self-organizing Team

Self organization is defined as a phenomenon in which the internal organization of the system increases in complexity without being guided or managed by an outside source. Self organization is deemed to be a fundamental attribute of Agile teams. However, successful self organization needs a lot of support from not only the team members but also the management and the organizational environment. In order to help the team move towards self organization, the right level of management involvement is required.

Esther Derby suggested that most teams moving towards self organization face two extremes of manager involvement

  1. Helicopter Managers – who step in too soon to rescue thereby depriving the team to think and solve problems together.
  2. Absentee Managers – who would not step in at all irrespective of whether the team has all the necessary skills to tackle the problem.

Esther suggested the following guidelines for making self organizing teams successful

  1. If the team has sufficient skills to solve the problem then give them space else ask questions to help them get unstuck. This would help in building the skills eventually.
  2. When time is not of the essence give the team time to work the issue. This would improve the team feeling and collaboration.
  3. If the solution space is limited in scope and impact, or the decision is reversible, give the team space to solve the problem, even it there's a good chance they'll get it wrong the first time.

Esther added,

There's always a trade off between expediency and a learning opportunity. Self-organizing teams can outperform manager-let teams....but only if the managers are willing to navigate the balance.

Similarly, Dave Nicolette suggested the following factors for growing effective self-organizing teams.

  1. Clearly define the boundaries – Without this the team is lost on how much they can manage themselves and when should they invoke management help. Without the definition of boundaries, teams err on side of caution and do not take any decision without seeking permission.
  2. Tolerate mistakes and allow time for learning – management should not jump in at the first problem. They should allow the team to learn from their mistakes and take corrective action on their own.
  3. Keep the team challenged, yet not frustrated- The manager should be aware of the team’s skill level and limitations. He should be able to provide the team with enough challenges to keep them in a state of learning and growth.

A study done a few years on the successful model of self managing teams, placed a lot of emphasis on the balanced involvement of management with the team. The right balance allowed the teams to flourish in their decision making and problem solving capabilities.

Thus it is important to build some structure around the teams on the path of self organization. It is important for the managers to be aware of the skill level of the team to step in or stay back at the right moment and act as a catalyst for the team to reach a state of self organization.

 

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.