Measuring Agility, Craftsmanship, and Success

by Chris Sims on May 25, 2009 |

While Scott Ambler, Ross Pettit and others continue to pursue the creation of a maturity model for agile, David Starr has looked at how and why an organization might want to measure things like: agility, craftsmanship, and organizational success. He found craftsmanship relatively easy to measure, while agility was the most difficult to measure in a useful way.

David examined three areas that an organization might want to measure: agility, craftsmanship, and organizational success. He finds it relatively easy to find way to measure organizational success. The most common measure is profitability, or ROI. While this is an easy measurement to make, it is more difficult to understand all the potential causes for a given change in ROI. For this reason, ROI does not easily lend itself to being a measure of the effectiveness of organizational growth or improvement efforts. The article notes, but doesn't deeply explore, the many areas of measurement provided by Lean, which seem better suited to measuring organizational effectiveness and improvement.

The next area of measurement examined was agility. Unlike ROI, the term agility is not clearly defined. In order to answer the question 'How agile are we?' an organization has to first define measurable attributes of agility. David considers measuring the degree to which an organization's values align with those in the Agile Manifesto, but finds this not very useful. David didn't examine using the 12 principles behind the Agile Manifesto as a basis for measurement, which might be easier and more useful to measure.

The final area the David examines is craftsmanship. Andrew Hunt and David Thomas used a craftsmanship model in their book The Pragmatic Programmer. Bob Martin made a push for this model in his keynote at the Agile 2008 conference, and went on to create the Manifesto for Software Craftsmanship.

Guilds have been creating rating systems for craftsmen for ages. David shows how such a system could be created for developers, or any skills-based activity. He then shares a basic model for using the rating system to facilitate improvement:

Pick a skill

Assess your proficiency

Make a decision to modify your behavior in a deliberate way

Perform this new way

Evaluate your skill level

Repeat

Ultimately, David recommends using what he calls 'guild-specific instruments' to measure individual and team improvement in skills and capabilities, while making use of the instruments of Lean as tools for organizational improvement.

Related Editorial

How do you Develop a Shared Understanding on an Agile project?

Application Performance Management Buyer's Guide

Continuous Delivery: A Maturity Assessment Model

How do you estimate on an Agile project?

Agile Executive Primer: Partnering Across the Organization

Related Sponsor

Agile Project Management That Adapts With You. Provide your global development team a shared space that adapts to the way they work.

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Community comments

Point of Accuracy by Micah Martin Posted

Point of Accuracy by Micah Martin

While Bob Martin was one of the contributors of the Manifesto for Software Craftsmanship, he was not the sole creator. Most of major contributors of the manifesto are among the first signatures on the document. It is ultimately Doug Bradbury that deserves credit for coordinating and compiling the the manifesto.