Burn Up Chart

What is a Burn Up Chart?

A burn-up chart is a progress chart for a sprint, release or project that plots total scope and completed work as separate lines. Since scope has its own line, added or removed work is visible, unlike in a burndown chart.

Updated November 2026 · 3 min read


A burn-up chart is a graph that shows two lines over time: the total amount of work in scope and the amount of work completed. The completed line rises as the team finishes work, and the gap between the two lines is the work remaining. When the lines meet, the scope is done. Because scope gets its own line, a burn-up chart makes changes in scope visible, which is its main advantage over a burndown chart.

Burn-up charts are used for releases, projects and sprints. Work is usually measured in story points or number of items on the vertical axis, with sprints or days on the horizontal axis.

Components of a burn-up chart

  • Horizontal axis. Time, usually sprints for a release chart or days for a sprint chart.
  • Vertical axis. Units of work, such as story points, items or estimated hours.
  • Scope line. The total work planned. It steps up when work is added and down when work is removed.
  • Completed line. Cumulative work done. It never goes down, and flat segments show periods with nothing finished.
  • Projection (optional). An extension of the completed line based on average pace, often shown as a range using the best and worst recent velocity.

Burn-up vs. burndown chart

AspectBurn-up chartBurndown chart
What it plotsTotal scope and completed workRemaining work
Scope changesVisible as a separate lineHidden inside the remaining work line
Best forReleases and projects where scope changesShort sprints with stable scope
Main question it answersAre we progressing, and is the target moving?Will we finish what is left on time?

With a burndown chart, if the line flattens, it is unclear whether the team slowed down or new work was added. A burn-up chart separates the two.

How to create a burn-up chart

  1. Choose the unit. Story points or item count. Item count works well when items are similar in size.
  2. Record total scope at the start. Plot it as the first point on the scope line.
  3. Update at a fixed interval. At the end of each sprint or day, record total scope and cumulative completed work.
  4. Count only finished work. Items meet the definition of done or they do not count.
  5. Add a projection. Extend the completed line using average velocity to estimate when it will meet the scope line.

Burn-up chart example

Consider a hypothetical team planning a release with 200 story points of scope and a velocity of about 25 points per sprint, suggesting eight sprints. The burn-up data after five sprints looks like this:

End of sprintTotal scopeCompleted (cumulative)Remaining
120024176
220050150
323075155
423099131
5250125125

The team has averaged 25 points per sprint (125 / 5), exactly as planned. But scope grew by 50 points in sprints 3 and 5. At 25 points per sprint, the remaining 125 points need five more sprints, so the release finishes after sprint 10, not sprint 8. A burndown chart would show remaining work rising in sprint 3 and barely moving in sprint 5 and might suggest the team slowed down. The burn-up chart shows the team kept pace while scope grew, which points the conversation at scope decisions: either cut about 50 points or move the date.

Common pitfalls

  • Not updating the scope line. If added work is not recorded, the chart loses its main advantage.
  • Counting partly done work. Partial credit makes the release look further along than it really is.
  • Treating the projection as a promise. It is a forecast based on past pace, and its range matters more than its single date.
  • Re-estimating finished work. Changing points after completion distorts both lines.

Burn-up charts sit alongside sprint velocity, cumulative flow diagrams and other agile metrics, and help explain scope creep to stakeholders.

Frequently asked questions

What is the difference between a burn-up chart and a burndown chart?

A burn-up chart plots total scope and completed work as two separate lines, so added or removed work is visible. A burndown chart plots only remaining work, so when its line flattens it is unclear whether the team slowed down or scope grew. Burn-up charts suit releases with changing scope, while burndown charts suit short sprints with stable scope.

How do you forecast a completion date with a burn-up chart?

Extend the completed-work line using the team's average velocity and see where it meets the scope line. For example, with 125 points remaining and an average of 25 points per sprint, the work needs about five more sprints. Show the forecast as a range using the best and worst recent velocity, and treat it as an estimate, not a promise.

What units should a burn-up chart use?

A burn-up chart usually measures work in story points or item count on the vertical axis, with sprints or days on the horizontal axis. Item count works well when items are similar in size. Whatever the unit, count only work that meets the definition of done, and avoid re-estimating finished items, since both mistakes distort the chart's lines.