In 30 seconds
- One line for work done, one for total scope.
- Scope changes show up as the scope line moving.
- Ideal for release tracking and forecasting.
Try it
CompletedScopeForecast range
How to read it
The x-axis is time (days or sprints). The completed line rises as work finishes. The scope line shows total planned work. Where the lines meet is when the work is done.
Patterns
| Pattern | Means |
|---|---|
| Scope line rising | Work is being added |
| Completed line flat | Nothing is finishing |
| Lines converging steadily | On track |
Forecasting
Extend the completed line using best and worst recent velocity to show a range for where it meets scope. That gives an honest date range. See burndown vs burnup.
Myth vs reality
Myth · A burnup is just an upside-down burndown.
Reality · It adds the scope line, which changes the story.
Myth · Rising scope is always bad.
Reality · It may reflect learning; the chart just makes it visible.
Myth · Burnups are only for Scrum.
Reality · Kanban teams use them with item counts.
FAQ
What units should we use?
Story points or item counts.
Should scope ever go down?
Yes, when items are removed; show that too.
Who should see the chart?
The team and stakeholders.