Agile metrics and key performance indicators (KPIs) provide quantifiable insights into team performance, delivery predictability, quality, and continuous improvement within iterative development frameworks. Unlike traditional project metrics that emphasize comprehensive upfront planning and scope completion, Agile metrics focus on empirical data—throughput, cycle time, flow efficiency, and value delivery—to enable adaptive planning and data-driven retrospectives. When used correctly, these metrics reveal bottlenecks, predict delivery outcomes, and guide teams toward sustainable velocity without gaming the system; when misused, they become vanity metrics that incentivize the wrong behaviors (e.g., inflating story points to boost velocity). This cheat sheet covers velocity and its correct application, burndown and burnup chart interpretation, Kanban flow metrics (cycle time, lead time, WIP limits, throughput), cumulative flow diagrams, DORA metrics for DevOps performance, team health and predictability indicators, quality and technical debt tracking, and common anti-patterns that undermine Agile measurement. Mastering these metrics helps teams build trust with stakeholders, improve delivery forecasting, identify process improvements, and maintain a healthy balance between speed and sustainability.
What This Cheat Sheet Covers
This topic spans 11 focused tables and 45 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Core Scrum Metrics
Scrum's inspect-and-adapt cycle relies on a few foundational metrics that guide sprint planning, track progress toward the sprint goal, and enable data-driven retrospectives. Velocity measures historical throughput to inform capacity planning; burndown and burnup charts visualize daily progress and scope changes; and sprint goal success rate reveals how consistently teams deliver on commitments. These metrics are most effective when viewed together—velocity sets the baseline, burndown tracks daily execution, and goal achievement validates that the team is delivering meaningful outcomes rather than just completing story points.
| Metric | Example | Description |
|---|---|---|
Sprint 1: 32 ptsSprint 2: 29 ptsSprint 3: 35 ptsAvg: 32 pts | • Sum of story points completed per sprint, averaged over 3–5 sprints; used for capacity planning only, not performance comparison between teams • Each team's points are relative to their own context • Never compare velocity across teams or use it as a performance target | |
12 goals met / 15 sprints= 80% success | • Percentage of sprints where the sprint goal was achieved; measures predictability and commitment reliability rather than raw throughput • High velocity with low goal success indicates scope creep or over-commitment • Track completion rate above 80% | |
Y-axis: Remaining work X-axis: Sprint days Ideal slope vs actual | • Visualizes remaining work over time within a sprint; tracks progress toward zero • Steeper slope = faster completion • Flat sections indicate blockers • Best for fixed-scope sprints with clear sprint goals |