Agile Metrics: Velocity, Burndown Charts and Burnup Charts

Agile teams need a clear way to understand their progress, plan upcoming work, and identify problems before they affect delivery. Agile metrics help teams make sense of project information and decide where improvements are needed. Among the most commonly used metrics are velocity, burndown charts, and burnup charts.

Each provides a different view of work. When used together, they help Scrum teams understand their progress without relying on assumptions or unnecessary status meetings.

What Are Agile Metrics?

Agile metrics are measurements that help teams evaluate their workflow, progress, and ability to deliver value. They can highlight patterns such as unfinished work, changing scope, and delays during a Sprint.

However, metrics should support conversations rather than become targets that teams must meet at any cost. A single number rarely explains why a team is facing difficulties. Scrum Masters should consider the context behind the data and involve the team when deciding what to improve.

1. Scrum Velocity: Understanding Team Capacity

Scrum velocity measures the amount of work a team completes during a Sprint, commonly expressed in story points when the team uses story-point estimation.

For example, suppose a team completes 24 story points in one Sprint, 28 in the next, and 26 in the third. Its average velocity across these three Sprints is 26 story points.

This information can help the team forecast how much work it might complete in a future Sprint. During Sprint Planning, Developers can consider previous results alongside current capacity, upcoming leave, technical dependencies, and the complexity of the work.

Why velocity matters:

• Helps inform Sprint planning and forecasting.

• Provides insight into the team's delivery patterns.

• Supports discussions about changes in capacity or work complexity.

Velocity is not a measure of individual productivity or overall product quality. Comparing story points between teams can also be misleading because estimation practices differ. Scrum Masters should encourage teams to use velocity for their own planning rather than pressure them to increase the number every Sprint.

2. Sprint Burndown Chart: Tracking Remaining Work

A sprint burndown chart shows how much work remains during a Sprint as time progresses. The chart typically compares the remaining work against the days or other time intervals in the Sprint.

For example, a team begins a two-week Sprint with 40 hours of estimated work remaining. As tasks are completed, the remaining work decreases. If the chart stays flat for several days, the team may need to investigate whether tasks are blocked or larger than expected.

A sprint burndown chart can help teams:

• See whether remaining work is changing over time.

• Identify periods when progress slows.

• Discuss blockers and adjust their approach.

• Understand whether the Sprint Goal remains achievable.

A burndown chart does not explain the reason behind a trend by itself. The Scrum Team still needs to discuss what is happening and decide whether action is required. It should not be used to blame team members when the line does not follow the expected path.

3. Burnup Chart: Tracking Completed Work and Scope

A burnup chart shows the amount of completed work over time, usually alongside a line representing the total scope. Unlike a burndown chart, which focuses on remaining work, a burnup chart makes changes in scope easier to see.

Imagine a team starts a Sprint with 30 story points of planned work. During the Sprint, the team completes 15 points, but additional work increases the total scope to 40 points.

A burnup chart displays the rise in completed work separately from the increase in total scope. This helps stakeholders understand why the team may not have reached the original target, even though progress has been made.

Burnup charts are useful for:

• Showing completed work clearly.

• Making scope changes visible.

• Supporting conversations about delivery expectations.

• Helping stakeholders understand the difference between progress and added work.

This visibility is particularly helpful when requirements change frequently. Rather than treating every change as a failure, teams can use the chart to discuss the impact of new work on delivery plans.

Velocity vs Burndown vs Burnup Charts

Although these Agile metrics are related, each answers a different question.

Teams do not need to use every metric available. They should select measures that help them understand their work and make better decisions.

How Scrum Masters Should Use These Metrics

Scrum Masters can help teams interpret metrics without turning them into performance targets. If velocity falls, for example, the team can explore possible causes such as unexpected defects, changing requirements, or reduced capacity.

Similarly, a burndown chart with little movement may indicate a blocker, while a rising scope line on a burnup chart may show that new requirements have been added.

The purpose is not to make every chart look ideal. It is to identify useful information, encourage honest discussions, and support continuous improvement.

Conclusion

Velocity, burndown charts, and burnup charts offer different ways to understand Agile delivery. Velocity supports forecasting, burndown charts show remaining work, and burnup charts reveal completed work alongside changes in scope.

When Scrum teams interpret these metrics in context, they can improve planning, discuss risks earlier, and make informed decisions. The best metric is the one that helps a team learn and improve, not the one that simply produces the most impressive numbers.