AGILE IN ACTION

Thursday, November 23, 2006

Supporting change

Posted by Simon Baker
Tags: agile, change

Compromised agility or agile mediocrity can be achieved in a command-and-control environment. Full-on agility can’t. And so you miss out on all the benefits that come along with it: A whole new level of improved quality and increased productivity, creativity, accountability, leadership, energized work, motivated people and fun.

If you’re an executive manager serious about being agile and you’re in a command-and-control environment you should start changing things to achieve lasting success. Start with the culture and the organisation and then move onto the people.

Agility will not happen when scientific management prevails. The values and principles are diametrically opposed. Disband the command-and-control institutions and get rid of the traditional management mindsets. You need to be thinking of agile as a leadership mindset and an omnipresent culture that is built on trust, honesty and courage, and

  • allows teams self-organise
  • empowers people at the coal-face to make their own decisions
  • facilitates collaboration, open communication and information sharing
  • tolerates mistakes and encourages constant learning
  • drives a continuous flow of business value to the customer
  • energises people and creates a buzz
  • seeks to eliminate waste and bureaucracy
Create a place where people want to work.

That said, agility will not happen without the right people. Given long enough, I’m convinced a command-and-control will create theory-X people. You want theory-Y people who have the right mix of talent and integrity to get things done. Don’t have people tell other people what to do. Ask people to make commitments to one another about their work and what they will deliver. And ask them to hold one another accountable to those commitments because delivering against commitments builds trust.

Dissolve groups of people who are siloed according to their roles, e.g. QA, Architecture, Project Management, etc, and instead build cross-functional teams organised around single and coherent products or services. These teams should include all the necessary skills - programmers, testers, sysadmins, DBAs, etc - to make decisions, take immediate action and get things done. People in a team work together so colocate them. Give teams the space to succeed and trust them to get things done.

Don’t use managers. Find leaders who will facilitate teams, maintain focus on the big picture and common goals, and preserve the new culture.

Without the vocal support and encouragement of executive management coupled with visible demonstration of adherence to common values and principles, an organisation will not commit to change.

Creative Commons Licence

Recent Posts

  1. Debugging Grails Database Performance
  2. Grails for Hipsters
  3. Governance - Friend or Foe?
  4. The Energized Work lab is moving aboard ship
  5. Gus Power on the future of software development at The CW500 Club
  6. Agile On The Beach: Session: How Are We Doing?
  7. Presenting BuyaPowa at Hacker News London
  8. Knowledge nuggets from Kent Beck
  9. There's gold in them thar hills
  10. No Bull: An author's note

Archives

  1. 2013 (2)
  2. 2012 (27)
  3. 2011 (24)
  4. 2010 (31)
  5. 2009 (41)
  6. 2008 (69)
  7. 2007 (152)
  8. 2006 (128)
    1. December (16)
    2. November (26)
      1. XPDAY2006: Courage - How brave are you?
      2. XPDAY2006: Why is simple so difficult?
      3. XPDAY2006: Love in the Age of Software
      4. Another iteration retrospective
      5. Supporting change
      6. Courage, dear boy!
      7. Our bullpen has its own race track
      8. Making room for a big visible screen
      9. What's keeping me up
      10. She's a beaut!
      11. Constructive disruption and compromised agility
      12. Drawing burn-up charts on overlays
      13. ABC2006: Kent Beck - Agility is not enough
      14. ABC2006: Snippets of wisdom
      15. Diana Larsen's Retrospectives for Change
      16. Celebrate every success
      17. ABC2006: Exploring Agile Factors
      18. ABC2006: Attending the APLN Leadership Summit and Agile Business Conference
      19. ABC2006: Simon Voice of Connections Recruitment
      20. ABC2006: The Naked Leader Experience
      21. Retrospective: Attack of the oversized story cards
      22. Team on the planning board
      23. Settling into a new bullpen
      24. You're in my way
      25. Scrum talk at Google
      26. Behaviour-Driven Development
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
    12. January (24)
  9. 2005 (63)
  10. 2004 (2)

Tags

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