Agile Metrics and Continuous Improvement
What to Know
Metrics should inform improvement, not judge individuals. Know velocity (forecasting), burn-down (work remaining vs. time), burn-up (scope + completed, shows scope creep), cycle/lead time, cumulative flow diagrams (reveal bottlenecks and WIP growth), throughput, and escaped defects.
Continuous improvement is driven by the Retrospective: inspect, identify one or two actionable improvements, and follow up. Improvement is empirical - plan, do, check, adjust. Root-cause tools (5 Whys, fishbone) help move past symptoms.
Anti-patterns: using velocity to compare teams, gaming metrics, measuring output (lines of code) instead of outcomes (value delivered), and ignoring retrospective actions.
Traps
- Velocity comparison across teams. Meaningless - points are team-specific.
- Burn-down vs. burn-up. Burn-down shows remaining work; burn-up shows scope growth and completed work; scope creep is clearer on a burn-up.
- Cumulative flow diagram misread. Widening bands = WIP building = bottleneck.
- Retrospective without follow-through. Improvement requires tracked actions.
- Vanity metrics that look good but don't drive decisions.
- Blaming individuals with metrics - destroys trust and transparency.
Rule of Thumb
Choose the metric that answers the question: Will we finish? → burn-down/burn-up/velocity. Where's the bottleneck? → cumulative flow. How fast do we deliver? → cycle/lead time. Are we improving? → retrospective actions + outcome measures.
Worked Example
A team's burn-up shows flat completion while scope rises - classic scope creep. The Retrospective identifies unrefined backlog items entering Sprints; the team adds refinement and tracks the action next Sprint.