Sprint Health Metrics: What Should You Track?

What should you track?

The most useful sprint health metrics are the ones that reveal a real risk or a clear pattern.

• Planned vs completed work
• Scope added or removed
• Blockers
• Spillover
• Aging work
• Defects
• Capacity vs load
• Days remaining

Planned vs completed work

Comparing planned work with completed work is one of the fastest signals to review.

This does not automatically mean the sprint is unhealthy. The team should ask why the gap exists and whether the work is blocked, deprioritised or too large to complete.

• Why are six items incomplete?
• Were they deprioritized?
• Were they blocked?
• Was new work added?
• Were the original estimates unrealistic?

Blockers and spillover

If the team is repeatedly blocked or work keeps spilling over, that is a strong sprint health signal.

• Is spillover increasing?
• Is the same type of work repeatedly spilling over?
• Are dependencies causing it?
• Is work being started too late?
• Is the sprint consistently overloaded?

Spillover also matters because it shows the team is carrying work into the next sprint instead of finishing in the current one.

Aging work and defects

Aging work often points to unclear requirements, blockers or too much work in progress.

• Blockers
• Large stories
• Unclear requirements
• Technical complexity
• Excessive work in progress
• Dependency problems

Defects matter too. A sprint that creates more defects than it resolves can indicate quality risk even when the count of tasks looks healthy.

• New defects
• Open defects
• Critical defects
• Defects affecting sprint work
• Defects carried into future sprints

Capacity vs load

One useful signal is whether the team is planning more work than the team can realistically deliver.

• Days remaining
• Important work remaining
• Blocked work
• Dependencies
• Testing time
• Release constraints

If the team is consistently behind on critical work, it may need to reduce scope, improve planning or address blockers sooner.

A few practical signals to watch

A good metric set is compact and actionable. It should point the team to what needs attention rather than overwhelming it with data.

How to react to the signals

1. 1

   Identify the signal

   Three high-priority items have been blocked for two days.

2. 2

   Understand the cause

   Ask why they're blocked.

3. 3

   Determine the impact

   Could the blocker affect the Sprint Goal?

4. 4

   Take action

   Escalate the dependency, remove the blocker, adjust the plan, or take another appropriate action.

5. 5

   Review the outcome

   Check whether the intervention actually improved the situation.

Signs of a healthy sprint

• Progress toward the Sprint Goal
• Limited uncontrolled scope change
• Blockers being actively managed
• Work flowing through the process
• Critical issues receiving attention
• No significant accumulation of aging work
• Capacity broadly aligned with planned work

Sprint health metrics work best when they help the team make a practical adjustment instead of just creating a status report.