Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Know it well enough for the exam? Questions on Burn-Up Chart are scenario-based, not definitional.
Practice it freeExplanation
Burn-up charts are used at the release or product level, where scope is expected to change as the team learns. They are especially useful in conversations about dates: when a sponsor asks why a release moved, the chart shows whether the team slowed down or the scope grew. They also work for fixed-date releases, by showing how much of the backlog will realistically fit by that date.
Building one takes two numbers per sprint: the cumulative points completed and the current total scope. Many teams add projection lines from the completed line at their slowest and fastest recent velocity, which turns the chart into a forecast range instead of a single promised date.
Reading it is straightforward. A completed line that flattens means velocity has dropped. A scope line that rises means work was added; one that falls means items were removed. The vertical gap between the lines is the work remaining, and dividing it by velocity gives the number of sprints left.
What a burn-up chart shows
A burn-up chart draws two lines on the same axes. One is total scope: how much work is in the release right now. The other is work completed, which climbs as items are finished. The distance between them is the work remaining; the work is done when the two lines meet.
That separation is the whole point. On a burndown, finishing 20 points and adding 20 points look the same as doing nothing: the line stays flat. On a burn-up, you see the team's progress and the scope growth as two different movements, which makes for a much more honest conversation with stakeholders about dates. It is spelled burn-up, burnup or burn up chart; all mean the same thing.
Worked example: an 8-sprint release with growing scope
A team plans a release of 120 story points and averages about 19 points per sprint. After sprint 4 the sponsor adds a 20-point reporting feature; after sprint 6 the product owner adds 10 more points from user feedback.
| Sprint | Velocity | Completed | Scope | Remaining |
|---|---|---|---|---|
| 0 | — | 0 | 120 | 120 |
| 1 | 18 | 18 | 120 | 102 |
| 2 | 20 | 38 | 120 | 82 |
| 3 | 17 | 55 | 120 | 65 |
| 4 | 21 | 76 | 140 | 64 |
| 5 | 19 | 95 | 140 | 45 |
| 6 | 19 | 114 | 150 | 36 |
| 7 | 18 | 132 | 150 | 18 |
| 8 | 18 | 150 | 150 | 0 |
Forecasting from the chart
After sprint 5 the team has completed 95 of 140 points, so 45 remain. At an average of 19 points a sprint that is about 2.4 more sprints, so the release lands in sprint 8. When 10 more points arrive after sprint 6, 36 remain; at 19 a sprint that is still sprint 8. Without the two additions, the original 120 points would have been finished in sprint 7.
The message for the sponsor is clear and fair: the team did not slow down (velocity stayed between 17 and 21), the date moved because scope grew by 30 points. A good burn-up often shows a forecast range rather than one date, by projecting the completed line at the team's slowest and fastest recent velocity.
The same data as a burndown
Between sprints 3 and 4 the remaining work drops by one point. A stakeholder reading only this chart would assume the team had a bad sprint. The burn-up shows what actually happened: 21 points done, 20 points added.
Common exam traps
Picking a burndown when the question is about changing scope.
If the stem says stakeholders keep adding or removing features, or asks which chart shows scope changes, the answer is the burn-up chart.
Reading the gap between the lines as a schedule variance.
The vertical gap is remaining work in points, not time. Convert it to time with velocity, and say it as a range.
Thinking a rising scope line is automatically bad.
In adaptive work, scope is expected to evolve as the team learns. The chart makes the trade-off visible so the product owner and stakeholders can decide: accept a later date, or remove lower-value items to hold it.
Assuming the team decides to add scope.
The product owner owns the product backlog and its ordering. Stakeholders request; the product owner decides what goes into the release, and the burn-up records the consequence.
Treating velocity as a target to raise.
Velocity on the chart is used for forecasting. Pressuring the team to increase it tends to inflate estimates rather than output.
Where it fits
Burn-up vs burndown: which one to use
| Situation | Better choice | Why |
|---|---|---|
| Single sprint, fixed sprint backlog | Burndown | Simple, one line, daily signal |
| Release with scope that moves | Burn-up | Separates progress from scope change |
| Explaining a date change to a sponsor | Burn-up | Shows the team kept pace while scope grew |
| Fixed-scope contract milestone | Either | With no scope change both show the same thing |
| Spotting bottlenecks in a Kanban flow | Neither | Use a cumulative flow diagram |
The burndown chart page walks through a day-by-day sprint example. A longer side-by-side discussion is in Burndown chart vs burn-up chart on the blog.
Practice and related pages
Free practice questions on this concept (full explanations, no signup):
- What does a burn-up show that a burndown does not?
- What a cumulative flow diagram adds to burn charts
- Using burn charts in iteration planning
- All free adaptive project-controls questions
Study next:
Key Points
- •Two lines: total scope and cumulative completed work
- •Scope changes are visible separately from progress
- •The work is done when the completed line meets the scope line
- •Project the completed line at a range of velocities to forecast a date range
- •Preferred over a burndown for release tracking when scope changes
Exam Tip
If a question involves changing scope or asks which chart shows scope changes, the answer is the burn-up chart. The gap between the lines is remaining work in points; convert it to time with velocity.
Frequently Asked Questions
Related Topics
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Velocity
Velocity is the amount of work a Scrum team completes in a Sprint, typically measured in story points, used to forecast how much work the team can handle in future sprints.
Information Radiators
Information radiators are highly visible, physical or digital displays placed in prominent locations that provide project status information to stakeholders at a glance without requiring them to seek it out.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Part of
Agile & Hybrid
Practice Burn-Up Chart
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.