Agile guide · Agile practices
Agile Metrics and KPIs: What to Measure and Why
Agile teams measure to learn and improve, not to rank people. The right handful of metrics shows whether the team is delivering value predictably, at good quality, in a sustainable way.
Key takeaways
- Measure delivery, flow, quality, outcomes and team health.
- Use a small set of metrics and watch trends.
- Metrics are for learning, not for ranking teams.
Delivery and predictability
| Metric | What it shows |
|---|---|
| Velocity | Story points completed per sprint; used for forecasting |
| Sprint burndown | Work remaining in the current sprint |
| Release burnup | Progress towards a release, including scope changes |
| Sprint goal success rate | Share of sprints in which the Sprint Goal was met |
| Planned vs completed | How reliably the team delivers what it plans |
Flow
| Metric | What it shows |
|---|---|
| Cycle time | Time from starting an item to finishing it |
| Lead time | Time from the request to delivery |
| Throughput | Items finished per week |
| Work in progress | Items started but not finished |
| Cumulative flow diagram | Where work piles up in the workflow |
Quality
- Escaped defects: problems found after release.
- Defect resolution time.
- Change failure rate and deployment frequency, two of the DORA metrics widely used by software teams.
- Technical debt trends.
Outcomes and value
- Customer satisfaction or Net Promoter Score.
- Adoption and usage of new features.
- Business results linked to the release goal, such as conversion or time saved.
- Time to first value for new initiatives.
Team health
- Regular team happiness or engagement surveys.
- Overtime and unplanned work.
- Retrospective actions completed.
Using metrics well
- Pick a small set: one or two from each group.
- Look at trends, not single data points.
- Discuss metrics in retrospectives, with the team.
- Never compare velocity between teams or use it to rate individuals.
- Pair every speed metric with a quality metric, so one is not improved at the expense of the other.
Free templates for this topic
Frequently asked questions
What is the most important Agile metric?
There isn't one. Combine a flow or delivery metric with a quality metric and an outcome metric.
What is the difference between the lead time and cycle time Agile metrics?
Lead time starts when the request is made; cycle time starts when work actually begins. Both end when the item is delivered.
What are the most common Agile metrics?
Velocity, sprint burndown, release burnup, cycle time, lead time, throughput, escaped defects and team health surveys.
What is a sprint burndown chart as an Agile metric?
A chart showing the work remaining in the current sprint, day by day. It helps the team see whether it is on track for the Sprint Goal.
What is throughput as an Agile metric?
The number of items finished per period, such as per week. It is a simple, reliable flow metric that does not depend on estimates.
What are the DORA metrics, and are they Agile metrics?
Four software delivery metrics: deployment frequency, lead time for changes, change failure rate and time to restore service.
What is a cumulative flow diagram among Agile metrics?
A stacked area chart showing how many items are in each workflow stage over time. Widening bands show where work is piling up.
How many Agile metrics should a team track?
A small set, one or two each from delivery, quality, outcome and team health, is usually enough.
Should Agile metrics be used for performance reviews?
No. Using them to rate individuals or compare teams encourages gaming the numbers. Use them to ask questions and improve.
What is the sprint goal success rate Agile metric?
The share of sprints in which the team met its Sprint Goal. It shows predictability without relying on story points.
Which Agile metrics measure value?
Through outcome metrics such as customer satisfaction, feature adoption, revenue, cost saved or time to first value.