The Rosetta Stone
Please note: I have massively expanded on this post in an article appearing in InfoQ:
Go there for my deeper, more considered treatment.
* * *
Here's my attempt to line up a range of models, most not explicitly or exclusively agile:
| Model | Stage 1 | Stage 2 | Stage 3 | Stage 4 |
| Folk classification | Cowboy | Waterfall | Agile (or Lean) | - |
| Shu Ha Ri | - | Shu (learn) Doing Agile | Ha (internalise) Being Agile | Ri (transcend) |
| 4 stages of competence | Unconscious incompetence | Conscious incompetence | Conscious competence | Unconscious competence |
| Marshall model | Ad hoc | Analytic | Synergistic | Chaordic |
| Agile Fluency | Non-fluent | One star (focus on value) | Two / Three star (deliver / optimize value) | Four star (Optimize for systems) |
| Hofstede culture clusters | Contest | Pyramid | Network | - |
| Spiral dynamics | Orange | Blue, Orange | Green, Yellow | Turquoise |
Disclaimers
- In some Agile quarters "maturity model" is a bit of a dirty expression, in-so-far as it can be taken to imply a strict linear development, oblivious to context, so hopefully there will be some good debate!
- I don't claim that the models line up perfectly. Each has its strengths, so I'm using it to point towards useful parallels and prompt further discussion.
- Shu Ha Ri and Four stages of competence are usually taken to apply at a personal level, while the others apply at larger scales: to teams, organisations, and/or societies. I include both because I see the personal and cultural shifts as intertwined.
Commentary
It's early days in the paradigm-shift sweeping knowledge work and its coordination. Leading up to and following the signing of the Agile Manifesto in 2001 the early adoption of the Agile was all bottom-up, and came from software development groups.Today we are seeing lots of top-down action, as well as the dissemination of Agile [and Lean] concepts and techniques well beyond software [and manufacturing] into most areas of knowledge-work. Executives are sponsoring Agile (and Lean) "implementations" in an attempt to cope with the challenges of an era of accelerating change and unrelenting competition.
But the shifts in mindset and culture needed to thrive in the "new normal" are vast. This applies to do-ers, to middle-managers, and to executives. [Those who think they can require change in their subordinates without going on the journey too, may well find themselves obsolete.] In my experience many welcome the change to a more humane and effective way of working, some adapt with a bit of effort, others misconstrue, bastardise and partly "get it", and a significant number are unwilling or unable to make the shift, at least on the first attempt.
When I first came across Agile methodologies in 2004 they were regarded as the province of elite, small-scale software development teams. I thought that there was no way large organizations would buy into the implicit challenge to command-and-control, and I had yet to realise that Agile ideas have so much to offer all areas of knowledge-work, not just programming, start-ups, and IT. By 2010, I saw that the shift was well under-way: the need for change now outweighed the blockers, but paradigm-shifts don't happen easily ... or overnight!
Today, as an Agile Coach, I find myself in the business of culture change, and I've gone hunting for models to quickly assess organisational culture in order to make clear, achievable recommendations for Agile intervention, implementation, transformation, or rescue. The aim is to make Agile coaching interventions faster and more effective.
After chatting with Matthew Hodgson of Zen Ex Machina about his brilliant application of Hofstede's culture clusters to diagnose organisational culture I wondered whether I could better target my own coaching efforts.
When I discussed applying the Hofstede/dgson with my then colleagues, a counter-proposal arose: what about Bob Marshall's model? This carried the day, and yielded helpful insights.
Some applications
The different mindsets that underly the different stages can give rise to interesting (and somewhat amusing) perceptual differences.
1. While recruiting in a fairly established corporate Agile environment (in which teams were operating reliably in late stage 2, early stage 3) I would typically get one of two responses from job candidates who lacked previous Agile:
- People from Stage 1 (ad hoc) backgrounds such as digital agencies would take one look and comment on the "incredible bureaucracy" of our practices. How did we ever get anything done!?
- Those accustomed to stage 2 (waterfall variant) such as long-time bank employees would, by contrast, perceive our operation as a risky cowboy shop operating at break-neck pace!
In both cases it was necessary to gauge whether the individual would likely be able to make the transition. Generally, if they were attracted to our approach, for example if they felt that it addressed shortcomings in their previous work environments that they had found frustrating, there was potential.
2. As a coach, it's a very different proposition to work with an "ad hoc" group, typically confronted with organisational growing pains, compared to a more established organisation trying to transition out of command-and-control / traditional project management, e.g. in order to become more responsive and/or creative.
In the first instance one needs to lead the client on a journey into discipline -- shu / doing agile -- before ha / becoming truly agile.
In the latter case, there is the tricky task of helping people unlearn the false lessons of command-and-control ("unplugging them from the Borg" in the evocative phrasing of the wonderful Stephanie BySouth) before nurturing the new mindset.
In the first instance one needs to lead the client on a journey into discipline -- shu / doing agile -- before ha / becoming truly agile.
In the latter case, there is the tricky task of helping people unlearn the false lessons of command-and-control ("unplugging them from the Borg" in the evocative phrasing of the wonderful Stephanie BySouth) before nurturing the new mindset.
Which model is best?
Just as I love both my children equally, and I don't want to choose between different Agile methodologies -- but I *will* recommend one over the others in a given context -- I'm not picking winners here. I wouldn't have included a model if I didn't think that it added substantively to the mix. However, I will put in a vote for Bob Marshall's model as a good default starting place.
What do you think?
