Burndown chart

A burndown chart is a graphical representation of work remaining versus time. It shows how much work is left to complete and helps teams visualize progress toward a sprint or project goal. The chart "burns down" from the total work to zero as tasks are completed, providing an at-a-glance view of whether the team is on track.

Why it matters

Burndown charts make progress visible. Instead of asking "how's the sprint going?" and getting vague answers, anyone can look at the chart and see exactly where things stand. This visibility enables early course correction-if the chart shows you're behind on day three, you can adjust before it's too late.

The chart also facilitates conversations. When the actual line diverges from the ideal line, it prompts questions: What's blocking progress? Did we underestimate? Was scope added? These discussions are more productive when grounded in visual data.

Reading a burndown chart

The horizontal axis shows time, typically days in a sprint. The vertical axis shows work remaining, measured in story points, hours, or task count.

Two lines tell the story:

The ideal line runs straight from total work (top left) to zero (bottom right). It represents steady, even progress-what would happen if work completed at a constant rate.

The actual line shows real remaining work each day. It tracks above, below, or on the ideal line depending on actual progress.

When the actual line is above the ideal, you're behind schedule. Below means ahead. Tracking closely to ideal means on track.

What the patterns mean

Flat sections indicate no progress. Work isn't getting done-perhaps due to blockers, unexpected complexity, or team members being pulled away.

Steep drops show rapid completion. This might indicate a burst of productivity or that several items were completed simultaneously.

Upward movement means work was added. Scope increased after the sprint started, or items were re-estimated to be larger than originally thought.

Cliff at the end suggests work wasn't tracked granularly. Everything appeared incomplete until suddenly it was all done. This limits the chart's predictive value.

Creating useful burndown charts

Update daily, at a consistent time. The chart reflects progress only if it's current.

Measure remaining work accurately. Items should be marked done only when they're actually done-meeting the definition of done, not just "mostly finished."

Choose the right unit. Story points work well for sprints; task count works for simpler tracking. Whatever you choose, be consistent.

Make the chart visible. A dashboard everyone sees daily is more valuable than a report someone generates weekly.

Sprint vs. release burndowns

Sprint burndowns track progress within a single sprint. They typically span 1-4 weeks and measure completion of the sprint backlog. These are the most common type.

Release burndowns track progress across multiple sprints toward a release goal. They span months and show how the overall release is progressing. These are more useful for longer-term planning and stakeholder communication.

Common issues

Scope changes without visualization confuse the picture. If 20 points were added mid-sprint, the team isn't really behind-the target moved. Some teams explicitly show scope changes on the chart.

Gaming the chart happens when teams optimize for the metric rather than actual progress. Completing small items to make the line look good while hard problems linger defeats the purpose.

Partial credit inflates progress. An item 80% done still has 100% of its points remaining. Counting partial completion makes the chart unreliable.

Large items create step functions rather than smooth lines. If one 13-point story takes all sprint, the chart shows no progress until day 10, then a cliff. Smaller items burn more smoothly.

Burndown vs. burnup

Burndown charts show work remaining (going down). Burnup charts show work completed (going up) alongside total scope.

Burnup charts make scope changes visible-when scope increases, the target line rises. This is useful when scope changes frequently and you want to show stakeholders that the team is making progress even as requirements expand.

Many teams find burndown simpler for sprint tracking and burnup more informative for release tracking.

Beyond the chart

Burndown charts are tools for visibility and conversation, not guarantees. A chart showing you're on track doesn't mean you'll finish-unexpected issues can still arise. A chart showing you're behind doesn't mean you'll fail-teams often accelerate toward the end.

The value is in what the chart reveals and the conversations it enables. Teams that use burndowns effectively pay attention to what the chart says, discuss divergences openly, and adjust based on what they learn.

Most agile project management tools generate burndown charts automatically. The data comes from how you track work-mark items done, and the chart updates. The key is building the habit of looking at it and using what you see.