Agile Measurement

Agile is not a traditional SDLC model so this would suggest traditional measurement techniques would be out of step with this model also. I have collated some thoughts on an article I found interesting (see end of article for link). Points of Interest

• Follows trends, not numbers. This avoids measuring sub-optimsied data
• Use a small set of metrics and diagnostics, They (see the authors of the original document) advocate that a 'just enough' approach is sufficient. Too much information can become unwiedly and ultimately obscure important trends
• Provide fuel for meaningful conversation. Face-to-face conversation is a very useful tool for process improvement. A measurement isolated from its context loses its meaning
• Encourage the "good-enough" quality. This context should come from the customer and their business needs and not the developers. Doesn't matter if the developers think it is "good-enough" if the client won't accept it.

One interesting point made was the distinction between the measurement purpose and respective process. Suggesting that there is confusion between two exercises; measuring to deliver value (the object of Agile work) and data-gathering to document or justify the Agile approach in the wider world of methodologies. This makes a lot of sense. When measuring, measure wisely: Apply heuristics. A good agile metric re-affirms and reinforces Lean and Agile principles Measures outcome, not output The theme of the paper focuses heavily on "Customer Value". Unlike old practices where cost was the primary driver for the product agile focuses on "Value". More specifically, value for the customer. Hence... Measure what you deliver: value as the customer metric. There are many benefits to value-driven work which delivers high-value features to the client. It is suggested that this business-value be determined by the stakeholders and developers together. The paper further goes on to talk about diagnositics and metric evaluation checklist techniques whilst looking at the key metric; business value delivered. You can read the full publication here.