Skip to content
Try Scrumling for Employers
Glossary · metrics

Burnup chart

A chart tracking completed work against total scope over time, useful when scope changes during a Sprint or release.

What it means

A burnup chart plots two lines: total scope and completed work, both climbing over time until they meet. Unlike a burndown chart, it clearly shows when scope itself increases, rather than confusing scope changes with lack of progress.

It is not part of the Scrum Guide, but a common complement to Sprint or release tracking, particularly useful at the release or Product Goal level where scope evolves across multiple Sprints.

Common mistakes

Teams managing stakeholder expectations often prefer burnup charts because a rising scope line visibly explains schedule shifts, rather than looking like the team missed a deadline.

Example

A burnup chart shows the scope line jumped mid-release when a compliance requirement was added, explaining the later completion date.

The two lines on a burnup chart

The completed-work line starts at zero and rises as items reach Done. It never drops unless finished work is reopened. The total-scope line shows how much work is currently planned for the Sprint, release or goal being tracked. It rises when work is added and falls when work is removed.

The gap between the two lines is the work still to do. The team is finished when the completed line meets the scope line.

Worked example: scope changes, completed work stays the same

A release starts with 60 points of scope. After three Sprints the team has completed 30 points. Before Sprint four, stakeholders add a 15 point reporting feature, so scope rises to 75.

During week one of Sprint four the team is blocked by an environment problem and completes nothing new. The completed line stays flat at 30. The scope line has stepped up from 60 to 75. Remaining work grew from 30 to 45, and the chart shows exactly why: new scope, not lost progress.

What a burnup shows that a burndown can hide

A burndown chart shows a single remaining-work line, so it mixes two different movements. If the team finishes 10 points while 10 points are added, the burndown stays flat and looks like nothing happened.

A burnup chart separates those movements. It reveals steady delivery hidden by growing scope, scope that keeps rising faster than the team completes work, and scope removed to hit a date. This makes it useful for release forecasts and for conversations with stakeholders about trade-offs.