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.

Comments

Popular posts from this blog

How Do You Vote Someone Off of Your Agile Team?

One of the conundrums of agile conversion is that although you are ordered by management to "self-organize," you don't get to pick your own team.  You may not have pictured it this way, but your agile team members are going to be the same people you worked with before, when you were all doing waterfall!   I know I wasn't picturing it that way for my first agile team, so I thought I should warn you.  (I thought I was going to get between six and eight original Agile Manifesto signers.  That didn't happen.). Why "warn" you (as opposed to "reassure" you, say)?  Because the agile process is going to reveal every wart, mole, quirk, goiter, and flatulence issue on the team within a few hours.  In the old days, you could all be eccentric or even unpleasant in your own cube, communicating only by document, wiki, email, and, in extreme situations, by phone.  Now you are suddenly forced to interact in real time, perhaps in person, with written messag

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. From http://www.yogawithjohn.com/tag/yoga-class/ 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 a

Your Agile Transformation Needs to Start with a Quiet Phase

From a really great blog post on agile adoption:  http://smoovejazz.wordpress.com/2011/02/16/an-agile-approach-for-adopting-agile-practices/ I've observed some different agile transformation patterns, and maybe you have too: Just Do Standups   (Shoot, then Aim):   some people feel that since you're "agile," you should just start doing stuff, like daily standups, and then build more of the the plan as you go.  Find a team and start doing some agile with them!  Start a revolution one practice at a time, one team at a time. Pros:   you're very busy from the start. Cons:   what exactly are you doing and why? KPI-Driven Change (Aim, then Shoot) : some people who have worked in large corporations for a while will tell you that to get the respect of the people, you need to start with a plan, support the plan with awesome printed and online collateral.  Then you "kick off," tell teams what to do, and measure them using "Key Productivity Indica