AGILE IN ACTION

Monday, 23 April 2007

Self-organisation again

Posted by Simon Baker

Read Jeremy Miller ‘s post: Self Organizing Teams are Superior to Command n’ Control Teams . One of the things he says is:

People in a self-organized team are able to make decisions themselves and accordingly adapt to changing situations. Command and control grunts have to wait for the boss to tell them what to do. That introduces latency in the development process as the team waits for the leader to shake free to deal with a decision.
He’s right. The latency is proportional to the distance the decision maker is away from the point where the decision is needed. This is often far away from the coal face (hierarchically, geographically, or both). And it gets worse. Small decisions aren’t possible because the latency is too great - you’ll spend all your time waiting around - and because decisions are bigger than they need to be, they aren’t easily reversible. (If you try to reverse them you have to traverse the hierarchy again adding more latency). This means it’s more difficult to fail fast, learn, and try something else.

Self-organisation only works if people are (and importantly feel that they are) empowered to make decisions, own the necessary authority, are prepared to be responsible and hold one another accountable to their commitments.

Creative Commons Licence

Recent Posts

  1. System failure is inevitable so design for a fast recovery
  2. Delight comes as a surprise in unexpected places
  3. Help create business agility. Bake quality in
  4. Governance - Friend or Foe?
  5. 70% Forum
  6. Measuring purpose. Measuring customer delight
  7. Stop pushing features and start delighting users
  8. Lost without a goal
  9. Emotion creates the common language
  10. Five sneaky ways to kill an initiative

Archives

  1. 2012 (16)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
    1. December (11)
    2. November (7)
    3. October (17)
    4. September (8)
    5. August (7)
    6. July (13)
    7. June (15)
    8. May (24)
    9. April (14)
      1. Does the Agile Manifesto need refactoring? Should it be extended?
      2. Self-management and self-leadership
      3. Improve quality to increase productivity
      4. Self-organisation again
      5. Breaking habits
      6. Self-organisation
      7. Put customers first and everything else follows
      8. I just came from there ...
      9. Defect tracking tools and waste
      10. Individuals and interactions over processes and tools
      11. Are you missing the point?
      12. Scrum Master, Master of Ceremonies and Quartermaster
      13. When you put it like that ...
      14. Become a certified Agile Software Specialist!
    10. March (19)
    11. February (7)
    12. January (10)
  7. 2006 (128)
  8. 2005 (63)
  9. 2004 (2)

Tags

agile (43) big visible chart (15) conference (40) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)