# Burnup Chart

A burnup chart plots completed work against total scope over time, making progress and scope change visible as separate lines.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/burnup-chart/>)

## What it means

A burnup chart displays cumulative completed work over time together with a separate line for total scope. The completion line rises as items finish; the scope line rises or falls when work is added or removed. The gap between them represents remaining work under the selected counting or estimation convention.

## Why it matters

Separating completion from scope makes an important distinction visible: a target can move even while delivery continues. Teams and stakeholders can discuss whether a forecast changed because completion slowed, scope grew, or both. The chart also keeps completed progress visible instead of reducing the view to what remains.

## When to use it

Use burnup for a release, epic, initiative, or other body of work whose scope may change. It is useful in reviews and forecasting conversations where people need transparency about both delivery and target movement. Select a unit—item count, points, or another measure—and keep its interpretation consistent.

## How it works

1. Define the scope boundary, completion rule, time horizon, and vertical-axis unit.
2. Record total scope and cumulative completed work at regular intervals using the same unit.
3. Plot both series, annotating meaningful additions, removals, or re-estimation events.
4. Inspect the remaining gap and completion trend, but express forecasts as ranges rather than guarantees.
5. Discuss value, quality, dependencies, and flow data alongside the chart before changing plans.

## A practical example

A team plans a 40-item account-migration release. After research, regulatory needs add six items, so the scope line rises while the completion line continues steadily. The chart prevents the added gap from looking like lost productivity. Leaders choose to defer two lower-value items and update the release forecast with the change visible.

## Where it breaks

A burnup depends on the quality and stability of its units. Point totals can change through re-estimation, while item counts can hide large differences in size. Completed work may not equal usable value, and an upward trend can conceal defects or incomplete integration. Extrapolated dates remain assumptions, especially with little history.

## Common mistakes

- Flattening the scope line after work changes, which removes the chart's main transparency advantage.
- Treating the completion trend as a deterministic promise rather than evidence for a forecast.
- Using completed points or items as a measure of individual or team value.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/burnup-chart/#visualization-burnup-chart>)

## Sources

1. [Configure Burndown and Burnup Widgets](<https://learn.microsoft.com/en-us/azure/devops/report/dashboards/configure-burndown-burnup-widgets?view=azure-devops>) — Microsoft Learn · Technical documentation
2. [Agile Burndown Chart Tutorial](<https://www.atlassian.com/agile/tutorials/burndown-charts>) — Atlassian · Professional guide

## Related topics

- [Burndown Chart](<https://wiki.soroush.uk/topic/burndown-chart/>)
- [Team Velocity](<https://wiki.soroush.uk/topic/team-velocity/>)
- [Monte Carlo Forecasting](<https://wiki.soroush.uk/topic/monte-carlo-forecasting/>)
