Scrum Master Metrics and Reporting: What Should You Track?

Metrics can help Scrum Teams understand how work is flowing, where problems exist and whether improvements are helping.

The goal is not to collect as many numbers as possible. The goal is to use useful information to support inspection and improvement.

Why Use Scrum Metrics?

Useful metrics can help a team understand:

  • How work is progressing.
  • Where delays occur.
  • Whether quality is improving.
  • Whether improvements are helping.

1. Sprint Progress

Sprint progress can help the team understand how much planned work remains and whether the Sprint Goal is at risk.

The Sprint Goal should remain more important than simply completing a certain number of items.

2. Burndown

A Sprint Burndown shows remaining work over time.

Useful for:

Seeing whether remaining work is changing during the Sprint.

A burndown is a signal, not a performance score.

3. Velocity

Velocity represents the amount of work a team has completed in previous Sprints, usually using the team's own estimation approach.

It can support forecasting when used carefully.

Do not:

Set a higher velocity target or compare different teams based on velocity.

4. Cycle Time

Cycle time measures how long work takes to move through a defined workflow.

It can help identify delays and opportunities to improve flow.

5. Lead Time

Lead time measures the elapsed time from when work is requested or identified until it is delivered, depending on how the organization defines it.

Tracking lead time can help reveal delays across the delivery process.

6. Work in Progress

Work in Progress, or WIP, shows how much work is currently being worked on.

Too much WIP can make it harder to finish work and may increase delays.

7. Defects and Quality

Quality information helps the team understand whether problems are being created during development.

Defects Identify recurring quality problems.
Rework Understand how much effort is spent correcting work.
Escaped Defects Identify problems discovered after delivery.
Automation Where relevant, understand the effectiveness of automated testing.

8. Sprint Goal Success

One useful question is whether the team is regularly achieving meaningful Sprint Goals.

However, simply counting successful and unsuccessful Sprints does not explain why results occurred.

9. Retrospective Improvements

A Scrum Master can help the team inspect whether improvement actions are actually making a difference.

The focus should be on learning and outcomes rather than the number of actions created.

Metrics at a Glance

Burndown Remaining work during a Sprint.
Velocity Historical amount of work completed by a team.
Cycle Time Time taken for work to move through a workflow.
Lead Time Time from request to delivery based on the chosen definition.
WIP Work currently in progress.
Quality Defects and other useful quality indicators.

How Should a Scrum Master Use Metrics?

1. Observe Look at the available information.
2. Understand Discuss what the numbers may be telling the team.
3. Experiment Try a practical improvement.
4. Inspect Check whether the change helped.

Metrics Are Not Targets

Turning a metric into a target can encourage people to optimize the number rather than improve the actual outcome.

Example:

If a team is told to increase velocity every Sprint, Developers may change estimation rather than actually improving delivery.

Don't Compare Teams

Different teams may use different products, technologies, estimation approaches and workflows.

Comparing their velocity or other team-specific measures can therefore produce misleading conclusions.

Reporting to Stakeholders

Reports should provide useful information rather than overwhelming stakeholders with numbers.

Focus on:

  • Progress toward goals.
  • Important risks and impediments.
  • Quality concerns.
  • Meaningful trends.
  • Actions being taken.

Common Metrics Mistakes

Too Many Metrics Collecting information that nobody uses.
Using Metrics to Blame Treating numbers as evidence against individuals.
Velocity Target Turning historical velocity into a performance target.
Ignoring Context Looking at numbers without understanding what caused them.

Useful Questions

  • What is this metric helping us understand?
  • What trend do we see?
  • What might be causing the change?
  • What should we investigate?
  • What improvement could we try?
  • Did the improvement actually help?
Key Principle:

Use metrics to improve the system and support learning, not to rank or punish people.

Key Takeaway

Good Scrum metrics provide useful information about progress, flow, quality and improvement.

The Scrum Master's job is not to chase numbers. It is to help the team use meaningful information to inspect, learn and adapt.