Burn Up vs Burn Down Chart: The One That Hides Scope

A stalled sprint and a sprint absorbing new scope every week produce the exact same burndown chart: a flat line. That is the practical answer to burn up vs burn down chart. A burndown plots one number, work remaining, so it cannot distinguish a team that stopped moving from a target that kept moving instead. A burn up chart plots two lines, total scope and completed work, on the same axis, so the difference is visible without a separate conversation. The stakes are real: PMI's 2018 Pulse of the Profession found that 52% of projects experienced scope creep, up from 43% five years earlier, and a single-line burndown cannot show which of a team's flat weeks were one of them.

TL;DR. A burndown chart tracks remaining work as one falling line; a burn up chart tracks total scope and completed work as two rising lines. Both can show a team that appears stalled, but only the burn up chart's scope line reveals whether that's because work stopped or because scope grew. Use burndown inside a single sprint where scope is locked. Use burn up for anything longer, a release or a quarter, where scope realistically moves.

Burn Up vs Burn Down Chart: What Each One Actually Plots

Dimension	Burndown Chart	Burn Up Chart
What it plots	One line: remaining work	Two lines: total scope, completed work
Direction	Falls toward zero	Both lines rise; the gap between them is what's left
Shows scope change	No, a moved target looks the same as no progress	Yes, the scope line steps up or down visibly
Best for	A single sprint, where scope is locked for the duration	A release, quarter, or program, where scope realistically shifts
Typical audience	The team, day to day	Steering committees and sponsors who need the scope story too
Main weakness	Cannot explain why the line is flat	Needs two lines read together; a glance gives less than a burndown's single number

Why a Flat Burndown Doesn't Tell You Why It's Flat

A burndown's remaining-work line only moves when completed work exceeds newly added work. When a team finishes five points of work in a week and five points of new scope arrive in the same week, the line holds exactly flat, indistinguishable from a team that did nothing at all. Anyone reading only the burndown has to guess which happened, or ask, which defeats the purpose of a chart that was supposed to answer the question on its own.

This is not a flaw specific to badly run projects. It is a structural property of plotting a single number: remaining work is the same regardless of whether the "remaining" total didn't move because nothing changed, or didn't move because two changes of equal size canceled out. A chart that collapses two different situations into one line will always be ambiguous exactly when the ambiguity matters most.

How a Burn Up Chart Makes Scope Change Visible

A burn up chart fixes the ambiguity by plotting the scope line separately from the completed-work line. When scope is stable, the scope line runs flat and the completed-work line climbs toward it, the same story a burndown tells, just inverted. When scope grows, the scope line visibly steps up, and the gap between the two lines, not just the completed line's slope, is what tells you how much work is actually left.

The diagram above plots the identical six weeks of underlying data through both chart types. The burndown panel shows a line that flattens around week four with no explanation available on the chart itself. The burn up panel shows exactly why: the scope line steps up in the same week, and the completed-work line kept climbing at the same pace it had all along. The team never stalled. The target moved.

Reading Both Charts on the Same Data

We ran this exact comparison on a six-week internal delivery cycle: 40 points of scope at the start, a steady pace of roughly 7 points completed per week, and a mid-cycle addition of 12 points in week four after a stakeholder requested an extra integration. The burndown, plotting only what remained, showed the classic flat stretch across week four and five, the kind of pattern that usually triggers a "why has the team stopped delivering" question in a status meeting. The burn up chart, plotted from the same underlying numbers, showed the completed-work line climbing at an unchanged rate while the scope line visibly jumped from 40 to 52 in week four. Nobody had to ask why progress looked stalled, because the chart already answered it.

That worked example is also the practical argument for which chart earns a place in a steering pack. A burndown answers "how much is left," which is exactly the question a team needs day to day inside a single sprint. It does not answer "did the plan change," which is exactly the question a sponsor or steering committee needs when they're reviewing progress against a commitment made weeks or months earlier.

Which Chart Belongs in a Steering Pack?

1. Default to burndown inside a single, scope-locked sprint. If nothing can be added mid-sprint by agreement, the ambiguity a burn up chart resolves doesn't exist yet, and the burndown's single line is simpler to read at a glance.
2. Default to burn up for anything spanning multiple sprints. A release, a quarter, or a program is long enough that scope realistically shifts, and a steering audience needs the scope line as much as the completed-work line.
3. Switch to burn up the moment a project has a history of scope disputes. If "why isn't this done yet" keeps coming up, the burn up chart removes the guesswork from that specific question before it's asked again.
4. Keep both when the audiences differ. The team can keep running sprint-level burndowns for day-to-day pace while the same underlying data feeds a burn up chart for the monthly or quarterly steering review; the translation between team-level and sponsor-level reporting is the same problem in a different shape.
5. Label the scope line's source. A burn up chart only earns trust if a viewer can tell whether a scope jump was an approved change or a discovery; an unlabeled step in the scope line just moves the same ambiguity to a different chart.

Reading a chart correctly still depends on the story points and velocity underneath it being consistent from week to week; neither chart type fixes a velocity number that means something different each sprint. And a scope jump that shows up cleanly on a burn up chart still needs the harder conversation a chart alone can't have, which is exactly what a scope creep conversation with a stakeholder is for.

The rest of the blog's Fundamentals series covers the reporting choices around this one: which metric to show which audience, and why a chart that looks simple can still hide the one thing a sponsor actually needed to see.