In 30 seconds
- Burndown: one line of remaining work falling to zero.
- Burnup: two lines, completed work rising toward total scope.
- Burnup makes scope changes visible; burndown hides them.
Pick a burndown when…
- Tracking a single sprint with stable scope
- The team wants a simple daily check
Pick a burnup when…
- Tracking a release over many sprints
- Scope changes and you need stakeholders to see it
- Forecasting a finish date from progress
Side by side
| Burndown | Burnup | |
|---|---|---|
| Lines | Remaining work | Completed work and total scope |
| Scope added | Looks like no progress | Scope line rises visibly |
| Best horizon | One sprint | Release or project |
| Ease of reading | Very simple | Slightly more to explain |
Myth vs reality
Myth · Burnup charts are just upside-down burndowns.
Reality · Burnups show scope as a separate line.
Myth · You must pick one.
Reality · Many teams use burndown for sprints and burnup for releases.
Myth · Charts measure productivity.
Reality · They show progress against a plan.
FAQ
What units do these charts use?
Story points, item count or task hours.
Do tools draw both?
Most agile tools offer both.
Which do executives prefer?
Usually burnup, because scope changes are visible.