Chapter 2. Metrics for steering

 

This chapter covers

  • The purpose and mechanics of several metrics
  • Dependencies of each metric
  • Common anti-patterns or inappropriate uses metrics

In this chapter, I’ll describe the purpose and mechanics of a number of metrics that are useful for helping you steer your work. I’ll explain what sorts of questions each metric answers, as well as the implications of development approach, process model, and delivery mode on the meaning and usefulness of the metric. Finally, I’ll mention a few abuses, or anti-patterns, that often occur when people misapply the metric.

This chapter is longer than the rest, because there is a good deal of material to cover on the subject of metrics for steering. The chapter is designed to guide you to metrics that may be helpful in your context. It isn’t meant to be read straight through, like a novel.

First, assess your situation in light of the three factors introduced previously:

  • Development approach
    • Traditional
    • Adaptive
  • Process model
    • Linear
    • Iterative
    • Time-boxed
    • Continuous flow
  • Delivery mode
    • Discrete projects
    • Ongoing or continuous

2.1. Metric: Percentage of scope complete

2.2. Metric: Earned value

2.3. Metric: Budget burn

2.4. Metric: Buffer burn rate

2.5. Metric: Running tested features

2.6. Metric: Earned business value

2.7. Metric: Velocity

2.8. Metric: Cycle time

2.9. Metric: Burn chart

2.10. Metric: Throughput

2.11. Metric: Cumulative flow

2.12. Not advised

2.13. Summary

sitemap