Skip to main content

Slaying the Agile Scaling Lycanthrope with A Barrage of Silver Bullets, er Maturity Models

Scott Ambler became my new hero in an instant today when I reached the conclusion of his dazzling Scaling Agile: An Executive Guide, published on his Agility@Scale blog site in February, 2010, where he refers to corporate productivity challenges as "lycanthropes." [p. 19, if you want to skip right to it.]

I had been hoping to write about scaling agile to large organizations today and will doubtlessly do so immediately, heavily referencing Ambler, whose blog you really must visit early and often.  But I hadn't heard the word lycanthrope before, and I just had to pause and marvel at the aptitude of the metaphor, in a way I haven't done since I encountered Dan North and Martin Fowler describing the relationship between business and technical people in a software endeavor as the "Yawning Crevasse of Doom." 

If agile enthusiasts gain any traction at all in this world, and apparently we are (Ambler quotes a survey showing that 76% of American corporations were at least experimenting with agile techniques in 2009), I would like to think it's because we are so frequently able to reap a fiscally significant corporate harvest from the hours of effort we've invested in the colorful worlds of J.R.R. Tolkien, StarCraft II (Wings of Liberty) and DragonQuest IX (Sentinels of the Starry Skies).

Back to the point, however, as agilists, we seem to have moved on since Martin Fowler's 2003 keynote on "Why Scaling Agile is the Last Thing You Want to Do."  Although his advice to "scale down projects" before "scaling up agile" is still true, by 2009, would-be organizational transformers had produced so many models to describe agile at scale that InfoQ had to publish a roundup.  The models annotated are either prescriptive, like CMMI or PMI, or purposefully heuristic and descriptive, as proposed by Ross Pettit

Now that the dust has settled a little and Ambler has produced his own model, I thought it might be time for a look at what he and two other practitioners offer, and how their models can help:
  • Ambler's Agility Scaling Model (ASM), referenced above.  Ambler's bottom line advice is going to be to retain IBM's Global Services and Rational teams to embed experts into your organization and help with the specifics of applying the model to your situation.  The framework itself is awesome in its own right, however, suggesting an evolution from:
    • "Core Agile Development" (a team iterating) to 
    • "Disciplined Agile Delivery" (an IT organization delivering a business solution from ideation to money-making production), and finally to 
    • "Agile at Scale" which describes a whole IT organization operating in an agile manner for all projects across all necessary continents.
A blurry approximation of Ambler's original.
  •  An earlier and also highly regarded framework has been developed by Ahmed Sidky and Greg Smith, and is included in their excellent book, Becoming Agile in an imperfect world.  The model, called the Sidky Agile Measurement Index (SAMI), is one which Sidky would ideally like you to engage his company, X2A Consulting (recently acquired by ubroadcast, inc), to help apply to your organization, but Sidky and Smith provide detailed information about how to do this for yourself in Appendix A of their book, "Readiness assessment tables by practice."  The book as a whole provides a helpful reference narrative describing steps you might go through in your own organizational transformation.  Like the ASM, the SAMI does not lend itself to intra-blog rendering at readable scale, but here is roughly what it looks like:
From Becoming Agile in an imperfect world--read the original!
  •  Michael Spayd has an interesting perspective on corporate agile conversions, and has developed methods for implementing XP within the framework of the CMMI, for companies who need to do so.  More recently, however, he has developed an agile-specific Seven-Layer Framework which usefully lays out the different layers of the organization which need to be addressed in order to successfully transform it.  Spayd, like Ambler and Sidky, can offer guidance on use of the framework through his company, CollectiveEdge Coaching.  Spayd's framework is useful in the way it helps you devise appropriate strategies for transformations of different demographics within a corporate environment:
    • Individual
    • Team
    • Management
    • Program
    • Strategy
    • Leadership
    • Organization
From Spayd's Agile 2009 Presentation -- read it in full!

The available published 2010 maturity models have in common that they do not provide a point-by-point guideline as to how to change your organization.  As my brief descriptions above suggest, the owners of these models want you to hire them, and there are other companies out there who have their own proprietary models as well.  And that is a good thing. 

Returning, as is my wont, to the Agile Manifesto, I suggest that organizational transformation, like so much in life, is going to be about a relationship between an owner of a corporate productivity problem of some size and one or more people who are going to help that person solve it.  We in the agile community, both suppliers and demanders of advice, are going to want to educate ourselves on different ways to think about the problem, and apply different lenses to evaluating how things are going.  In the end, maturity models won't increase corporate productivity, just as surely as silver bullets don't kill werewolves.  You need people to slay both figurative and literary lycanthropes.

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
Dialogue:
WBABA:   ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…