Key Takeaways
- A release burndown chart plots work remaining against time and answers “are we going to make it?” by revealing both your burn rate and whether scope is sneaking up.
- The vertical axis is work remaining in points or item count and the horizontal axis is time in sprints; a line trending to zero by the target date means you are on track, and the slope is your real burn rate.
- When the line rises between sprints, scope was added; a burndown that flattens or climbs despite steady output is the clearest early warning of scope creep.
- Splitting the baseline (original scope) from added scope on the chart makes the scope-versus-date trade-off visible for stakeholder conversations.
- Act on the chart: re-forecast or cut scope when the burn rate is too slow, make the trade-off explicit when scope rises, and confirm on-track status with confidence backed by the slope.
A release burndown chart is the simplest honest answer to “are we going to make it?” It plots the work remaining in a release against time, and its real power is showing not just whether you’re burning down, but whether scope is sneaking up. It’s a key tracking tool in release planning.
What it shows
The vertical axis is work remaining (in points or item count) and the horizontal axis is time, usually measured in sprints. A line trending down toward zero by your target date means you’re on track. The slope tells you your real burn rate; project it forward and you have a rough completion date.
The signal most people miss
When the line goes up between sprints, scope was added. A release burndown that flattens or rises despite steady team output is the clearest early warning of scope creep you’ll get, long before the deadline makes it obvious. Some charts split the baseline (original scope) from added scope so the two are visible separately, which is even better for the conversation with stakeholders.
Act on it
- Burn rate too slow? Re-forecast the date or cut scope, don’t hope.
- Scope rising? Make the trade-off explicit; see managing release scope creep.
- On track? Say so with confidence, backed by the slope.
Release Management, Roadmaps, Portfolio PPM & Timeline pairs the burndown with a live, throughput-based forecast, so you see both where you are and where you’ll land. For the forecasting side, see release date forecasting.
Where the burndown fits: tracking is one step of a full workflow to plan a release in Jira: from Fix Versions and dependencies to a defensible target date.
