Agile failure is a sensitive topic but one that we as a community need to talk about in order to build a brighter future together. In this post, I will share some observations that came out of an informal session that took place over an extended coffee-break session at Play4Agile conference.
I ran a quick fist of five survey with first eight coaches and then with twelve as people. The question was:
“How many (percent) of your Agile transitions have been successful? Zero for none. Five for all.”
The results confirmed what I have suspected and experienced: a single one, lot’s of twos and threes, and one four. No zeros or fives.
It was noted that one problem with the survey is that Agile (Lean?) is a direction (dream of perfection) and not a destination.
Good news, Bad news
Consider the visual note below (start in the top left).
Agile in the small is fine
When probing about what was working and what wasn’t it became clear that agile in the small was working well. With single teams and smaller companies, people were pretty happy with the results. Even isolated teams at large companies seemed to find success when the teams wanted to go Agile. The principle that applies here is: Go where the energy is.
Agile in the large needs attention
Now that Agile has crossed the chasm and many more transitions are initiated by the early majority we are seeing more of “me too” Agile adoption. Some of the support found in earlier transitions are now missing:
- Strong management support
- Sense of urgency (Critical for Kotter model)
- Notion that: failure is not an option
Case studies MIA
One key need of early majority is case studies. We as a community do not do a good job sharing success stories and an even worse job sharing failures. This makes it hard to learn and improve.
Agile in the Large
Craig Larman and Bas Vodde have written a great book – Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum – on how to make Agile work in the large. This is a good start and paints a clear vision for alternatives for making Agile work.
We also have Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns and Linda Rising. This is nice, but not nearly enough to get to a playbook for Agile adoption.
I believe that we as a community need focus more attention on models, patterns and guides for Agile transition and adoption. Lot’s of open territory here.
It’s about people. Duh.
One of the challenges with Agile in the large is that many people really don’t care about Agile and don’t want to change. Yeah, this happens with small teams too, but I find it is manageable there. When dealing with hundreds and thousands of people the problem gets amplified.
I thank Christine Neidhardt for reminding me that organizational change is about people. The way to change an organization is one person at a time.
Subsequent to publishing this, I found this great post that I strongly recommend: Agile’s Second Chasm (and how we fell in)
Michael K Sahota guides and teaches leaders how to create high-performance organizations. He is the creator of a proven system for leading change through a practical playbook. His model for Consciously Approaching Agile guides the creation of a cultural and leadership context where Agile creates lasting organizational results. Michael has taught over 1000 leaders worldwide through his highly acclaimed “Agile” Culture & Leadership Training.
Adoption , Coaching , Creativity , Failure , Identity , Management , Observing , Organizational Change , Play4Agile , Red Pill , Transition