Project Burndown Remaining Points Days

Burndown Chart: visualizing remaining work

A burndown chart puts remaining work on one axis and time on the other. The Y axis carries the effort that is still left (story points, hours, whatever unit you track) and the X axis runs across the days of the sprint. Its expected slope is ideal_burndown(t) = total_points × (1 - t / sprint_days), which draws a straight line from the full backlog on day 0 down to zero on the last day. Teams call this the “ideal line.” Treat it as a reference, never as a promise.

The actual line gets redrawn every day as the team closes stories. Sitting above the ideal line means you are behind. Sitting below means you are ahead. And when it jumps up, somebody added scope partway through the sprint, which is scope creep you can finally see. Because the gap shows up by the middle of the sprint, you still have room to renegotiate scope or clear a blocker before the review lands.

Applications

Sprint burndown tracks the current sprint backlog day by day and is the artifact most teams pull up during the daily sync. Release burndown works at the product-backlog level instead, following progress toward a milestone across many sprints. Jira, Azure DevOps, Linear and ClickUp build both for you out of completed-issue points. If your team is small, a spreadsheet or a Mermaid diagram does the job just as well.

FAQ

What’s the difference between burndown and burnup? Burndown counts remaining work as it falls toward zero. Burnup counts finished work as it climbs toward a total that can itself shift. Because that total is drawn on the chart, burnup tends to surface scope changes more plainly.

The actual line is a flat plateau — what does that mean? It means nothing crossed the finish line on those days. Usually the stories are too big, an external dependency is holding them up, or the definition of done is being waved through. Break the work into smaller pieces and clear whatever is blocking it.

Should I include in-progress work in the remaining points? Yes. A story stays in the remaining count until it is fully finished, and only then does it drop off. That binary “done or not done” rule is exactly what keeps velocity trustworthy.