AGILE IN ACTION

Thursday, May 24, 2007

Left leg or whole body?

Posted by Simon Baker

There’s some discussion happening at the Agile Forums about refocusing the Agile Alliance . Brian Marick advocates a new focus on helping teams be ready to execute Agile:

If the teams could vault from novice to seasoned in a day, and if they were less affected by external political/organizational issues, they’d all do fine. The problem they have is getting to that point. That’s where they need the most help.
George Dinwiddie responded:
Sometimes those external organizational issues are a part of the reason it takes so long to move from novice to seasoned. I’ve talked with organizations that want the benefits of Agile, but they don’t want to give up the cubes and solo development work. They don’t trust the team to self-organize and create valuable software, so they stick with organizational frameworks that prevent the very things they fear won’t happen.
Michael Feathers added:
Elsewhere Brian mentions that perhaps we should leave larger organizational issues to others. We can, but if we do, we have to adjust expectations. Working with a single team in an organization is a bit like walking up to a person and saying "Let’s see what we can do to make your left leg as healthy as it can be." And, sure enough, there are things you can do. you can inject vitamins, chemicals to foster local growth.. develop an exercise regiment.

You can do a lot for that leg, you can make the muscles bulge, increase its endurance, increase blood flow; but at the end of the day, the health of that leg is going to be sensitively dependent on the surrounding organization.

I think that when we work on the leg, we have to think about the body. If we don’t, we have to be less surprised when, at times, the leg does well for a while and degrades or the leg doesn’t respond as well as we wish.

Most of us have had success with individual teams. Some of us have had success with whole organizations. But, that link is there. If we look at execution through the lens of single teams, I think we’re missing something.
The ‘others’ Brian refers to is the APLN , which was established specifically to engage with the industry to bring about change for agility.

Earlier, in another thread touching on the same issue, I said:
Agility is not sustainable unless the larger organisation is compatible and supportive. More often than not, the larger organisation needs to change, otherwise agility exists inside a very fragile bubble within a hostile business environment. In my experience, agility has always failed due to larger organisation issues. I think it would be remiss of the Agile Alliance to leave the concerns with the larger organisation to others.

The Agile Alliance needs to champion agility and the change required to support it within industries. Agility is never going to stick by supporting only bottom-up initiatives through teams. There needs to be a proactive strategy of engagement with industry, corporate business leaders and decision makers that challenges current thinking in organisations and aims to educate and dispel myths. Let’s start trying to gain executive support for agility and indirectly initiate top-down changes in organisations that nurture the adoption of agile methods.
Upon reflection we need to continue to invest in improving people, and their attitude and skills, at grassroots through bottom-up initiatives, and we must also help to effect cultural and organisational change from the top down. Nobody really disputes this. However, I believe that whatever we achieve at grassroots will not survive without holistic change in corporate thinking and structure and that can only be accomplished from the top. Only with a two-pronged strategy can we achieve sustainable and pervasive agility in industry.

If the Agile Alliance is to focus on one thing and the APLN on the other, I sincerely hope they can create a collaborative partnership to implement such a strategy so that things can get better for everyone.

2 Comments

I'm in agreement Simon, without a culture change within organisations any grassroots work will be lost. Supporting organisation to understand the benefits of agile whilst upskilling teams seems to me to be the only viable route.

Comment by Siobhan

We have to address root causes.

Comment by Simon Baker

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)
    1. December (11)
    2. November (7)
    3. October (17)
    4. September (8)
    5. August (7)
    6. July (13)
    7. June (15)
    8. May (24)
      1. Product Owner and business marksmanship
      2. Say something
      3. 7 faces of leadership
      4. Scrum Master pulls the trigger
      5. Left leg or whole body?
      6. Additional values
      7. Layman's Manifesto
      8. Brian Marick wants to stir things up
      9. Iterating user interfaces
      10. Lessons are learned ...
      11. Quality is ...
      12. How did it get to be so wrong?
      13. Does standardisation suppress innovation?
      14. Is there a better way?
      15. Wake up and smell the complacency
      16. It takes 1 woman 9 months to make a baby
      17. You, organisational hierarchies, avast there!
      18. Story test-driven development
      19. Agile estimation techniques
      20. Fixed-price contracts don't work
      21. Competing on the basis of speed
      22. Testing in agile projects
      23. Jeff Sutherland on tuning Scrum
      24. Talking about agility
    9. April (14)
    10. March (19)
    11. February (7)
    12. January (10)
  8. 2006 (128)
  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)