Burn-Up Chart

A burn-up chart is a simple line chart that agile teams use to track progress toward a goal over time. The horizontal axis is time — usually days of a sprint or weeks of a project — and the vertical axis is a measure of work, such as story points or completed tasks. Two lines climb across it. One line shows the total scope, the full amount of work planned. The other shows the work completed so far, rising as the team finishes items. The gap between the two lines is the work remaining. When the completed line reaches the scope line, the goal is done. Because it draws completed work as an upward-climbing line, the chart 'burns up' toward the target, which is where the name comes from.

The defining feature of a burn-up chart is that it shows scope as its own line rather than baking it into the remaining work. That sounds like a small design choice, but it changes what you can see. If new requirements are added mid-project, the scope line steps upward, and the chart makes the change visible instead of hiding it. If work is cut, the scope line drops. A stakeholder glancing at the chart can tell at once whether the team is falling behind because they are working too slowly or because the target keeps moving. This clarity about scope is the burn-up chart's main advantage and the reason many teams prefer it for communicating progress to people outside the daily work.

The burn-up chart's closest relative is the burndown chart, and they are near-mirror images. A burndown chart plots a single line, the work remaining, starting at the top and falling toward zero as the team completes tasks. When the line hits zero, the work is done. It is compact and intuitive — down-and-to-the-right feels like progress — which is why burndown charts are common in sprint tools. But a burndown chart folds scope and progress into that one line. If the remaining line stalls or rises, you cannot tell from the chart alone whether the team slowed down or whether new work was added to the sprint. The information is there in the total, but the picture hides it.

The burn-up chart fixes exactly that blind spot by separating the two forces onto two lines. Progress is the completed line rising, while scope is the total line, which can rise or fall on its own. So on a burn-up chart, scope creep is unmistakable — the scope line visibly steps up — whereas on a burndown chart the same change just makes the remaining line refuse to fall, looking like slow progress. That is the core trade-off. Burndown is simpler and more familiar, while burn-up is more informative when scope changes, which on real projects it usually does. Teams that need to explain to stakeholders why a deadline moved often reach for the burn-up chart, because it distinguishes 'we are slow' from 'you added work.'

Use a burn-up chart when scope is likely to change and you need to show why — client projects, longer efforts, or any work where new requirements arrive mid-stream. Update both lines regularly so the picture stays current, and be consistent about your unit of work, whether story points, hours, or task counts, so the lines are comparable over time. Draw the scope line honestly, stepping it up or down exactly when work is added or removed, because its whole value is making those changes visible. You can add a target date or a projected completion line to show whether the completed line is on pace to meet the scope line by the deadline, turning the chart into a forecast as well as a record.

The failures come from undermining the chart's one advantage. If you quietly fold added work into a single line or stop updating scope, you lose the very transparency that makes a burn-up chart worth drawing, and it becomes a dressed-up burndown. Reading it without noticing the scope line rising is another trap, because you might blame the team for slow delivery when the target actually moved. And treating either line as precise when the underlying estimates are rough oversells the chart's accuracy, since it shows trend and direction, not a guarantee. Used honestly, though, a burn-up chart is one of the clearest ways to answer the question every stakeholder asks. Are we going to finish on time, and if not, is it because we are behind or because the job grew?

The 'burn-up' name mirrors the earlier 'burndown' chart from agile and Scrum practice, describing a completed-work line that climbs, or burns up, toward the total-scope line.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where burn-up chart is a core concern: