Burnup chart
A burnup chart shows work completed over time alongside the total scope of work. Unlike a burndown chart that only shows remaining work, a burnup displays two lines: one for cumulative completed work and one for total scope. This makes scope changes visible-when the target moves, you can see it.
Why it matters
When scope changes frequently, burndown charts can be misleading. If the team completes 50 points but 60 points were added, a burndown shows you're further from done than when you started. This doesn't reflect poorly on the team-it reflects changing requirements-but the chart doesn't distinguish between slow progress and moving targets.
Burnup charts separate these concerns. The completed work line always rises (or stays flat). The scope line rises when work is added and falls when work is removed. Stakeholders can see both: yes, we've made progress; also, requirements have grown.
Reading a burnup chart
The horizontal axis shows time. The vertical axis shows work in your chosen unit-story points, tasks, or features.
The completed work line starts at zero and rises as work is finished. It only goes up, making progress visible regardless of scope changes.
The scope line shows total work in the project or release. When scope is stable, it's flat. When work is added, it rises. When work is removed, it falls.
The gap between the lines represents remaining work. When the lines meet, you're done.
What the patterns show
Parallel lines with shrinking gap: Healthy progress. The team is completing work faster than scope is growing. You're approaching completion.
Diverging lines: The scope is growing faster than work completes. At this rate, you'll never finish. Something needs to change-either scope control or increased capacity.
Completed line flat: No progress. Blockers, distractions, or misreported data.
Scope line dropping: Deliberate descoping. The team or stakeholders decided to reduce what's included, which can be a healthy response to reality.
When to use burnup vs. burndown
Use burnup when:
Use burndown when:
Many teams use burndown for sprints (where scope should be stable) and burnup for releases (where scope often evolves).
Forecasting with burnup
Burnup charts enable useful projections. If you draw a line extending the completed work trend, you can see when it might intersect the scope line-giving an estimated completion date.
This works best with stable velocity. If recent progress has been consistent, projections are more reliable. If velocity varies wildly, projections are guesses.
You can also show range forecasts. Using the best and worst recent velocities, draw two projection lines. The range between their intersection with the scope line shows the uncertainty in your completion estimate.
Making burnups useful
Track scope changes explicitly. When the scope line jumps, note why. This creates a record of how requirements evolved and enables better conversations about scope management.
Update regularly. Like any tracking tool, burnups are only useful if current. Stale data leads to bad decisions.
Use consistent units. Whether story points, features, or tasks, pick one and stick with it. Mixing units makes the chart meaningless.
Show it to stakeholders. The burnup's power is in making scope changes visible. If stakeholders never see the chart, they miss the point.
Addressing scope creep
A burnup chart that consistently shows scope growing faster than completion is surfacing an important truth: you're committing to more than you can deliver. The chart doesn't solve this problem, but it makes it undeniable.
This visibility enables better conversations. Instead of "why aren't you done yet?" the discussion becomes "should we add more people, reduce scope, or accept a later date?" These are the real trade-offs, and the burnup makes them clear.
The relationship to roadmaps
Burnup charts typically track defined work. Roadmaps communicate planned work at a higher level. They complement each other-the roadmap shows intent, the burnup shows execution reality.
When a burnup shows scope consistently growing while progress lags, it may signal that the roadmap is too ambitious. The roadmap should reflect what can actually be delivered, and burnup data informs that reality check.
Tools and implementation
Most agile project management tools generate burnup charts automatically from how you track work. Mark items done, and completed work rises. Add items to the scope, and total scope rises.
The key is consistent tracking habits. The chart is only as good as the data feeding it. If work is tracked sporadically or inconsistently, the chart becomes unreliable.
Burnup charts are particularly valuable for communicating with stakeholders who need to understand that progress is real even when requirements keep expanding. The visual makes the abstract concrete.
