"Using Working SW As The Measure Of Progress Is Narcissistic...." How Do You Measure The Value Of Agile Instead?

Hi all,

My colleague and friend Mike Gualtieri wrote a really interesting blog the other day titled "Agile Software Is A Cop-Out; Here's What's Next." While I am not going to discuss the great conclusions and "next practices" of software (SW) development Mike suggests in that blog, I do want to focus on the assumption he makes about using working SW as a measurement of Agile.

I am currently researching that area and investigating how organizations actually measure the value of Agile SW development (business and IT value). And I am finding that, while organizations aim to deliver working SW, they also define value metrics to measure progress and much more:

  • Cycle time (e.g., from concept to production);
  • Business value (from number of times a feature is used by clients to impact on sales revenue, etc.);
  • Productivity metrics (such as burndown velocity, number of features deployed versus estimated); and last but not least
  • Quality metrics (such as defects per sprint/release, etc.).
Read more