AGILE IN ACTION

Saturday, 30 June 2007

What is the Declaration of Interdepence trying to say?

Posted by Simon Baker

Via InfoQ .

Tim Lister translates the Declaration of Interdependence into plain language in his introduction to agile leadership . Here’s the gist of Tim’s message:

1. We increase return on investment by making continuous flow of value our focus.

At least with the time we had, we delivered as many of the most valuable features we could.
2. We deliver reliable results by engaging customers in frequent interactions and shared ownership.
We make pace and rhythm visible early and we force the interaction with the customer into a partnership.
3. We expect uncertainty and manage for it through iterations, anticipation and adaptation.
Requirements emerge, they are not gathered. Let things evolve. Start with what the customer says he wants - use it as a warm-up exercise. The customer may say he wants so and so but, more often than not, he has no idea what he really needs nor what he could get. It’s often possible to deliver something that he’s never even dreamed of.
4. We unleash creativity and innovation by recognising that individuals are the ultimate source of value, and creating an environment where they can make a difference.
Push decisions down and out. Don’t worry who is where in the hierarchy find the right home for the decision. Are you the right person to make the decision? You might have the authority to make it but you do you have the right experience and the confidence to make it? Make the workplace safe for people to make decisions.
5. We boost performance through group accountability for results and shared responsibility for team effectiveness.
The great projects have emotion and people care. Emotion comes from collocation and dedication. Their sense of pride is tied up in the success of the project. Every person knows that they can’t succeed unless the team succeeds. Early wins beget later wins. Iterations provide shorter delivery timeframes. Delivering working software every iteration (and not parts of specifications) gives the epiphany of ‘working’ and that’s a real adrenaline boost.
6. We improve effectiveness and reliability through situational specific strategies, processes and practices.
To be truly efficient, the process itself must embrace change.

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)
      1. What is the Declaration of Interdepence trying to say?
      2. Some wisdom to share
      3. Energized Work Website in beta
      4. The Pickled Effect
      5. Accounting practices can get in the way of delivering value
      6. A new start at Energized Work
      7. Proposed session for XPday
      8. Supportive, ignorant or hostile?
      9. A true leader
      10. Is the Agile Alliance irrelevant?
      11. A social network for people interested in agile and lean product development
      12. Social associations
      13. Improve continuously
      14. Keep it lean
      15. Bad managers and good leaders
    8. May (24)
    9. April (14)
    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)