Chapter 3. Metrics for improvement

 

This chapter covers

  • Using metrics to guide process improvement
  • Metric dependencies on development, process, and delivery
  • Common anti-patterns or inappropriate uses of metrics

Several of the metrics we’ll cover in this chapter were described in chapter 2 in the context of steering work in progress. In this chapter, we’re concerned with using the same metrics to inform process-improvement efforts. You’re looking for different information from the metrics, and you’ll take different actions in response to the information than in chapter 2.

3.1. Process-agnostic metrics

Delivery-performance metrics that have no dependencies on software development methods are useful for monitoring the effectiveness of process-improvement efforts because they have the same meaning regardless of how the work is carried out. On the other hand, metrics that depend on development approach, process model, or delivery mode will break if you change any of those factors as part of your improvement program. This means metrics derived from the Lean school of thought are equally useful for steering and for process improvement.

3.2. Technical metrics

3.3. Human metrics

3.4. General anti-patterns

3.5. Metric: Velocity

3.6. Metric: Cycle time

3.7. Metric: Burn chart

3.8. Metric: Cumulative flow

3.9. Metric: Process cycle efficiency

3.10. Metric: Version control history

3.11. Metric: Static code-analysis metrics

3.12. Metric: Niko Niko calendar

3.13. Metric: Emotional seismogram

3.14. Metric: Happiness index

3.15. Metric: Balls in bowls

3.16. Metric: Health and happiness

3.17. Metric: Personality type profiles

3.18. Summary

sitemap