Burn-Up Charts

What a Burn-Up Shows

A burn-up chart has two lines plotted over time:

• Scope line: the total amount of work in the release/project, visible at the top. Moves up when scope grows; moves down when scope shrinks.
• Completion line: the cumulative work completed so far. Climbs from zero toward the scope line.

The chart shows progress (completion line trajectory) and scope change (scope line trajectory) simultaneously. The gap between them at any point is the work remaining.¹

Burn-Up vs. Burn-Down

The distinction is exactly the bottom line. A burn-down shows remaining work as a single line trending toward zero. A burn-up shows completion separately from scope.

The trade-off:

• Burn-down: simpler to read; hides scope changes.
• Burn-up: more honest about scope changes; slightly harder to read.

For sprint-level progress, burn-down is usually sufficient. For release-level forecasting, burn-up is dramatically more useful because release-level scope inevitably changes.

What Burn-Ups Reveal

Scope growth

The scope line climbs steadily over time. This is "scope creep" made visible. The team can still be making progress on completion, but the gap isn't closing because the target keeps moving.

Velocity changes

The completion line's slope shows the team's recent throughput. Flattening means slowing; steepening means accelerating. Compared against scope, the slope reveals whether the project is converging or diverging.

Projection

Extrapolating the completion line (at recent slope) until it intersects the scope line (at recent slope) gives a visual estimate of when the project will be done. The intersection is where to draw stakeholder attention.

Stalls and surges

Flat periods on the completion line (no progress) and jumps (batch completions) both signal something worth investigating.

Two Useful Variants

With confidence cone

Drawing two scope lines — optimistic (less) and pessimistic (more) — produces a band that visualizes scope uncertainty. The completion line projects against the band rather than a single value.

With probabilistic completion

Combining the burn-up with Monte Carlo forecasting (see Monte Carlo) produces a chart showing the completion line plus a 50%/85%/95% completion-date prediction. This is what modern release tracking should look like.²

How Burn-Ups Are Misused

• Static scope assumption. Some teams plot only the completion line and skip the scope line. This is a burn-up without its main feature — half-finished.
• Linear extrapolation. Projecting completion at the average historical slope ignores variability. Monte Carlo is more honest.
• Treating projection as commitment. "We'll be done by date X" based on extrapolation gets reported as a date. The honest answer is a probability distribution.
• Hiding scope decreases. Removing items from scope makes the chart look better. The removal should be visible.

When To Use Burn-Up vs. Other Charts

• Sprint progress: burn-down is fine. Scope is fixed during the sprint.
• Release tracking: burn-up is essential. Scope will change; the chart should show it.
• Long-running initiatives: burn-up plus Monte Carlo overlay.
• Operational team health: CFD beats both. Burn-charts are scope-bounded.

Coaching Tips

Always show the scope line.

A burn-up without scope is just a completion chart. The scope line is the chart's distinguishing feature.

Use burn-up for releases, burn-down for sprints.

Match the chart to the scope's volatility.

Don't extrapolate linearly.

Linear projection ignores variability. Use Monte Carlo for honest forecasts.

Show scope decreases too.

When scope is cut, the chart should show it. Hiding cuts makes the chart look better but corrupts the signal.

Use confidence bands when uncertainty is high.

An optimistic and pessimistic scope line bracket the range. Especially useful early in a project.

Annotate scope changes.

When the scope line moves, note why on the chart. The annotation makes future analysis tractable.

Summary

The burn-up chart is the burn-down's more honest sibling. By plotting scope explicitly, it prevents the silent distortion that scope changes cause in burn-down charts. Teams using burn-ups for release tracking see scope growth as it happens, can project completion against a moving target, and have a working conversation with stakeholders about which is more important — shipping by date or shipping with full scope. The chart is slightly harder to read; the honesty is worth the trade.

Back to Flow & Forecasting