Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Self-Organization & Subtle Control: Friends or ...

Mike Cohn
June 19, 2012

Self-Organization & Subtle Control: Friends or Enemies?

In this keynote presented at the Munich Scrum Gathering, Mike Cohn addresses whether the idea of exerting subtle control over a Scrum team is contradictory to the desire for teams to be self-organizing.

Mike Cohn

June 19, 2012
Tweet

More Decks by Mike Cohn

Other Decks in Business

Transcript

  1. © 2003–2009 Mountain Goat Software® ® What is a self-organizing

    team? L Self-organizing does not mean L the team gets to decide what goal they pursue L or even necessarily who is on the team L Self-organizing is about the team determining how they will respond to their environment L 0=3<0=064AB ;4034AB20=8=UD4=24C70C environment) 2
  2. ® © 2003–2009 Mountain Goat Software® Complex adaptive systems 

    A dynamic network of many agents  acting in parallel  acting and reacting to what other agents are doing  Control is highly dispersed and decentralized  Overall system behavior is the result of a huge number of decisions made constantly by many agents A CAS is characterized by: John Holland in Complexity: The Emerging Science at the Edge of Order and Chaos by Mitchell Waldrop 3
  3. © 2003–2009 Mountain Goat Software® ® Some examples L Ant

    colony or bee hive L Flock of geese heading south L Us right now L A crowd batched up to get into a concert or sporting event L A family preparing, eating, and cleaning up after a meal L Cars and drivers on the highway L A software team 4
  4. © 2003–2009 Mountain Goat Software® ® Control is not evil

    L Simple rules or incentives are used to guide or direct behavior L “Drive this direction and on this side on the highway.” L For bioteams, these are provided by nature L “Produce honey” L For our teams, L Rules and incentives can be added by managers or leaders...or in some cases by team members 5
  5. ® © 2003–2009 Mountain Goat Software® ~Philip Anderson, The Biology

    of Business Self-organization does not mean that workers instead of managers engineer an organization design. It does not mean letting people do whatever they want to do. It means that management commits to guiding the evolution of behaviors that emerge from the interaction of independent agents instead of specifying in advance what effective behavior is. 6
  6. ® © 2003–2009 Mountain Goat Software® ~Takeuchi & Nonaka Although

    project teams are largely on their own, they are not uncontrolled. Management establishes enough checkpoints to prevent instability, ambiguity, and tension from turning into chaos. At the same time, management avoids the kind of rigid control that impairs creativity and spontaneity. “The New New Product Development Game”, Harvard Business Review, January 1986. 7
  7. ® © 2003–2009 Mountain Goat Software® ~Peter DeGrace & Leslie

    Stahl Wicked Problems, Righteous Solutions To be sure, control is still exercised; but, it is subtle and much of it is indirect. 8
  8. © 2003–2009 Mountain Goat Software® ® What this is not

    L We’re not talking about L Being deceptive or sneaky L Manipulating people L Nothing I’m going to advocate needs to be secret L But there may be reasons why you don’t broadcast your reasons 9
  9. ® © 2003–2009 Mountain Goat Software® Two models of subtle

    control Containers, Differences & Exchanges 1 Anderson’s Seven Levers 2 10
  10. ® © 2003–2009 Mountain Goat Software® L A boundary within

    which self-organization occurs L Company, project, team, city, role, nationality Container L There must be differences among the agents acting in our system L Technical knowledge, domain knowledge, education, experience, power, gender Differences Transforming Exchanges L Agents in the system interact and exchange resources L Information, money, energy (vision) Glenda Eoyang: Conditions for Self-Organizing in Human Systems 11
  11. © 2003–2009 Mountain Goat Software® ® Using the CDE model

    L />D20=8=UD4=247>F0C40<B4;5>A60=8I4B by altering the: L Containers L formal teams, informal teams, clarify (or not) expectations L Differences L Dampen or amplify them within or between containers L Exchanges L Insert new exchanges, new people, new techniques or tools 12
  12. © 2003–2009 Mountain Goat Software® ® Containers L Enlarge or

    shrink teams L Enlarge or shrink the responsibility boundary of teams L Change team membership L Create new teams or groups 13
  13. © 2003–2009 Mountain Goat Software® ® Differences L Don’t require

    consensus L Creativity comes from tension L (D84C38B06A44<4=C8B=>C0B6>>30BT4A24 debate that leads to behavior change L Ask hard questions L +74=4G?42CC40<BC>T=3B>;DC8>=B 14
  14. © 2003–2009 Mountain Goat Software® ® Transforming exchanges L Encourage

    communication between teams and groups L Who isn’t talking who should? L Add or remove people from exchanges L Change reporting relationships L Relocate people L Compliance with external groups L Encourage learning 15
  15. ® © 2003–2009 Mountain Goat Software® An Example Would you

    alter a Container, Difference or Exchange in this case? LThe team consists of four developers, two testers, a database engineer and you. The developers and testers are not working well together. Developers work in isolation until two days are left in the iteration. They then throw the code “over the wall” to the testers. 16
  16. ® © 2003–2009 Mountain Goat Software® Two models of subtle

    control Containers, Differences & Exchanges 1 Anderson’s Seven Levers 2 17
  17. © 2003–2009 Mountain Goat Software® ® L Self-organization is not

    something that happens one time L A team is never done doing it L The team continually re-organizes in a sense-and- respond manner to its environment L As you see the team self-organize you can 8=UD4=241DC=>C2>=CA>;>A38A42C8CB?0C7 L We can view this as the evolution of a team The self-organizing path 18
  18. ® © 2003–2009 Mountain Goat Software® ~Philip Anderson Self-organization proceeds

    from the premise that effective organization is evolved, not designed. It aims to create an environment in which successful divisions of labor and routines not only emerge but also self-adjust in response to environmental changes. This happens because management sets up an environment and encourages rapid evolution C>F0A378674ATC=4BB=>C1420DB4<0=064<4=C70B mastered the art of planning and monitoring F>A:U>FB “Seven Levers for Guiding the Evolving Enterprise,” in The Biology of Business edited by John Henry Clippinger III. 19
  19. © 2003–2009 Mountain Goat Software® ® Variation, selection & retention

    L Evolution is the result of three elements: L Variation, selection and retention L Consider a giraffe: L Variation: A random mutation that leads to a longer neck L Selection: The long neck helps it reach food others can’t; so it it more likely to survive and breed L Retention: The mutation is passed to its descendants 20
  20. © 2003–2009 Mountain Goat Software® ® *4E4=;4E4AB5>A8=UD4=28=6 team evolution 1.

    Selecting the external environment 2. 4T=8=6?4A5>A<0=24 3. Managing meaning 4. Choosing people 5. )42>=T6DA8=6C74=4CF>A: 6. Evolving vicarious selection systems 7. Energizing the system Philip Anderson, “Seven Levers for Guiding the Evolving Enterprise.” 21
  21. © 2003–2009 Mountain Goat Software® ® Select the external environment

    L More than just the physical environment L What business are we in? L (OK, maybe you20=SC8=UD4=24C78B>=41DCB><4>=4 can L The company’s approach to innovation L Fast follower or innovator? Are mistakes OK? When? L Types of projects worked on and the rate at which they are introduced to the organization L Expectations about multitasking and focus 22
  22. © 2003–2009 Mountain Goat Software® ® Define performance L The

    principle of selection tells us that the traits that help us survive will be the ones retained L Managers and leaders send messages about which traits should survive L What message is your organization sending about the relative importance of short vs. long-term performance? L What messages are sent if the organization: L Provides training L Supports working at a sustainable pace L Allows employees time to explore wild ideas L Doesn’t exchange meeting a deadline for unmaintainable code 23
  23. © 2003–2009 Mountain Goat Software® ® Manage meaning L Individuals

    in a CAS respond to the messages they receive; e.g., L bees responding to a “danger” message L ants responding to a “food found over here” message L Leaders can push messages into the system L e.g., putting the the team in touch with customers L Or keep messages out L Meaning often comes from the stories, myths and rituals that are repeated L Q.4F8;;142><4?A>TC01;4C78B@D0AC4AR L “Our GM counts the cars in the lot every day at 5 PM” 24
  24. © 2003–2009 Mountain Goat Software® ® Decision-making style Gender Motivation

    Eye color Choose people L ;40A;HF7>8B>=C74C40<8=UD4=24B7>FC74HB4;5 organize L Adjust L Some people are like “glue” and pull a team together and keep it there Team size Location Background Experience Skepticism 25
  25. © 2003–2009 Mountain Goat Software® ® Reconfigure the network L

    Communication paths (formal and informal) can be more important than the individuals L />D20=8=CA>3D24>AA4<>E4U>FB L To other teams, experts in the organization, customers 26
  26. ® © 2003–2009 Mountain Goat Software® US Russia Team 1

    Team 2 US Russia Team 1 Team 2 Reconfiguring the network for a global team Distributed Scrum: Agile Project Management with Outsourced Development Teams at HICSS 2007 by Jeff Sutherland, et al. 27
  27. © 2003–2009 Mountain Goat Software® ® Evolve vicarious selection systems

    L Variation—Selection—Retention L Selection was determining which variations will be retained L Can take a long time L So we often use vicarious selection systems L This is an animal that can smell that a food is poisonous, rather than eating it L Using only the marketplace as our selection mechanism takes too long L Organizations also evolve vicarious selection systems L Retrospectives, Google’s 20% policy, compensation 28
  28. © 2003–2009 Mountain Goat Software® ® Energize the system L

    Unless energy is pumped into the system, entropy will set in L Make sure the group has a “clear, elevating goal”† or an “igniting purpose”‡ L Motivation L Project chartering: Vision box, press release, magazine review, elevator statement L Opportunity L To learn, a bigger role, to go onto even better projects, and so on L Information L Customer visits, training, conferences, brown-bags †Larson and LaFasto: Teamwork and ‡Lynda Gratton: Hot Spots 29
  29. ® © 2003–2009 Mountain Goat Software® To: All Microsoft Employees

    Subject: Internet Tidal Wave The Internet is a tidal wave. It changes the rules. It is an incredible opportunity as well as an incredible challenge. I am looking forward to your input on how we can improve our strategy to continue our track record of incredible success. May 25, 1995 Bill G . 30