InfoQ

News

Coaching Self Organizing Teams

Posted by Mark Levison on Aug 07, 2008 12:09 AM

Community
Agile
Topics
Teamwork
Tags
agile2008 ,
Self-organizing Team

Joseph Pelrine promised to teach us "hard science for soft skills" with respect to coaching teams. Joseph feels that coaching as a discipline lacks the scientific background and rigor that it needs: "Air guitar and attitude" won't do - Allan Kay. His goal to is to supply that rigor.

The discussion started off examining why teams, even ones that are experiencing problems don’t want to change. His thesis is that most of the time people and teams are in stasis and so resistant to change. To make change occur we have to raise the heat just enough people no longer feel comfortable in their current environment. The use of heat has analogy in cooking – most people on turn heat on or off but as coaches we need to understand five levels

  • Burning – food is tastes burnt, teams fall apart.
  • Cooking – flavors in food are well integrated, teams adapt to new ideas
  • Stagnating – bacteria grows in food, teams stagnate and start to stop using tools
  • Congealing – teams are starting to lose their flexibility and lock in their habits
  • Solid/Frozen – bureaucracy has set in, there are forms to fill out and sign offs everywhere.

Controversially Joseph claims that when we see teams that stop doing TDD or other practices that its often because the heat has been turned off. Working in a rigorous fashion he recommends that we only make one change at a time in response to problems we want to improve.

In addition he says that Bruce Tuckman’s: Forming, Storming, Norming, Performing Model is incomplete.

There are 3 major objections to Tuckman's model:
- entry conditions: we somehow assume that groups will automagically fall into this model and come out in an optimized way. Alpha male dominance will prevail as a group trait if the heat is not turned up so that the members can't maintain (not revert to) their ingrained behavioural patterns.
- exit conditions: upon reaching the performance stage, team members have reached a way of working, i.e. a consensus reality regarding the way they view and react to the external stimuli of the world. As this behaviour gets fixed, it (of necessity) diverges increasingly from reality, which in effect means that the team's behaviour becomes increasingly neurotic.
- the Tuckman model (at least the way most people interpret it) carries the implicit assumption that the performing stage is the optimal stage for teams, the goal that is to be reached. Remember - the Duke Ellington band used to have knife fights on the tour bus, Laurel and Hardy refused to talk off-stage, etc...

One model that Joseph offers to organize change is the ABIDE model (comes from David Snowden)

  • Attractors: Bonuses, Other rewards, Free Lunches…
  • Boundaries: Change/Remove Barriers between dev and test…
  • Identities: Roles – invite to switch roles or at least role play other…
  • Diversity or Dissent: change the make up of the team, bring in some one with a different background of the team i.e. a .NET developer to Java team.
  • Environment: remove cube walls, add burn down charts, add monitors everywhere displaying information, even just rearrange the existing seating plan

InfoQ has previously interviewed: Blend of Science, Process &Teamwork and presented: Dealing With the Organizational Challenges of Agile Adoption.

Readers can find more about this session on this reporter's blog.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Not Sure I agree by Yves Hanoulle Posted Aug 7, 2008 5:17 PM
  1. Back to top

    Not Sure I agree

    Aug 7, 2008 5:17 PM by Yves Hanoulle

    I think I understand the example of the Duke Ellington band. If I do understand it I have 2 remarks: 1 We don't know what they would have done if they would have gotten allong well. They could have created even better music. 2: the storming stage is about finding "Norms" how this team/band works together. It looks like the "norm" of the Duke ellington band was "fighing". I also think that the coaches should use different leading styles when the team is in a different phase. I blogged about that some months ago: http://paircoaching.wordpress.com/2007/09/18/how-to-grow-a-self-organizing-team/ The way I understand the model is a team moves along the 4 phases and goes back to the different phases. So when there is a new team member, the team goes back to the first phase. Bruce Tuckman actually added a 5th phase On top of that most groups never make it to the 3the phase because they are scared of the storming phase.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.