Sprint Burndown Calculator

Agile

Track sprint progress, visualize burndown patterns, and forecast completion with comprehensive analytics

Industry Standard
PMBOK Aligned
Real-time Results

Sprint Configuration

Daily Progress Tracking

DayDatePlannedActualCompleted
1
2
3
4
5
6
7
8
9
10
11
12
13
14

Understanding Sprint Burndown Charts

Key Components

  • •Ideal Burndown: Perfect linear progress from start to finish
  • •Actual Burndown: Real progress showing daily completed work
  • •Variance Analysis: Deviation from planned progress
  • •Forecasting: Projected completion based on current velocity

Best Practices

  • •Update burndown chart daily during stand-up meetings
  • •Investigate significant deviations immediately
  • •Use trends to predict completion and adjust scope
  • •Consider team capacity, holidays, and dependencies

What is a Sprint Burndown Chart?

A sprint burndown chart is one of the most powerful visual tools in the Scrum framework. It plots the amount of remaining work -- measured in story points, hours, or tasks -- against the number of days in a sprint. As a PMP who has facilitated hundreds of sprint retrospectives, I can tell you that the burndown chart is the single most effective communication tool for keeping stakeholders and team members aligned on sprint progress.

The chart features two primary lines: the ideal burndown line, which represents perfect linear progress from total committed work to zero, and the actual burndown line, which shows the real-world progress of work completed each day. The gap between these two lines tells a story. When the actual line is above the ideal line, the team is behind schedule. When it is below, the team is ahead. The PMBOK Guide 7th Edition and the Agile Practice Guide both reference burndown charts as essential tools for monitoring iteration progress and communicating status to stakeholders.

Burndown charts are updated daily, typically during the daily standup (also called the Daily Scrum). This cadence makes them an integral part of the Scrum inspect-and-adapt cycle. When the chart shows the team falling behind, the Scrum Master can facilitate a conversation about impediments, scope reduction, or reallocation of work. When the team is consistently ahead, the Product Owner may choose to pull additional items from the backlog.

How to Read a Sprint Burndown Chart

Remaining Work = Total Committed Work - Cumulative Work Completed

Understanding how to read a burndown chart is fundamental for any Agile practitioner. Here are the key components:

  • Ideal Burndown Line: A straight diagonal line from the total committed work (top-left) to zero (bottom-right). This assumes work is completed at a constant, linear rate throughout the sprint.
  • Actual Burndown Line: The real progress line updated daily. It rarely follows the ideal line perfectly. Teams commonly see a "staircase" pattern where work drops in chunks rather than smoothly, which is normal.
  • Projection Line: An extension of the actual burndown trend that forecasts where the team will finish by the end of the sprint. This is invaluable for early warning signals.
  • Variance: The vertical distance between the ideal and actual lines at any given day. A variance greater than 10-15% warrants a team conversation about root causes and corrective actions.

Step-by-Step Guide to Using Burndown Charts

1
Set the sprint baseline at sprint planning. During the sprint planning ceremony, determine the total committed story points and calculate the ideal daily burn rate. For a 10-working-day sprint with 50 story points committed, the ideal burn rate is 5 points per day.
2
Update the chart daily during the Daily Scrum. Each day, the team updates the remaining work. This should be a quick exercise -- estimate what remains for in-progress stories, not a full re-estimation. The Scrum Master typically updates the chart.
3
Analyze deviations during daily standup. If the actual line diverges significantly from the ideal, discuss why during the standup. Common causes include underestimated tasks, unplanned work, blockers, or team member unavailability.
4
Use projection for mid-sprint decisions. By day 4 or 5 of a two-week sprint, the projection line gives a reliable forecast. If it shows the sprint will not complete all committed work, the team and Product Owner can negotiate scope adjustments.
5
Review burndown patterns in the sprint retrospective. Look at the shape of the chart over multiple sprints. A flat line at the beginning followed by a steep drop at the end (the "hockey stick" pattern) suggests testing is being deferred, which is a quality risk.

Real-World Sprint Burndown Example

Scenario: E-Commerce Platform Redesign

Your team of 7 has committed to 42 story points for a 10-working-day sprint to redesign the checkout flow. Here is what the burndown might look like:

  • Day 1-2 (Mon-Tue): Flat at 42 points -- team is setting up, no stories closed yet
  • Day 3 (Wed): Drops to 36 -- 6 points completed (user login stories closed)
  • Day 5 (Fri): Drops to 28 -- 8 points completed (cart functionality delivered)
  • Day 7 (Tue): Drops to 18 -- 10 points completed (payment integration stories done)
  • Day 9 (Thu): Drops to 5 -- team surging to close remaining stories
  • Day 10 (Fri): Drops to 2 -- sprint ends with 40 of 42 points delivered

Completion Rate: 95% (40/42 points delivered)

Sprint Velocity: 40 story points (carried forward 2 points to next sprint)

The burndown shows a healthy pattern -- early acceleration with a slight plateau mid-sprint as the team tackles complex payment integration stories. The team completed 95% of committed work, which indicates good sprint planning discipline.

Common Mistakes to Avoid

  • The "hockey stick" pattern: When the actual burndown line stays flat for most of the sprint and then drops sharply in the last few days, it usually means testing and integration are being deferred. This creates quality risk and hides problems until it is too late to fix them.
  • Adding scope mid-sprint: The burndown chart should reflect the sprint backlog as committed during sprint planning. Adding stories mid-sprint distorts the chart and makes it impossible to compare across sprints. Use the sprint backlog as a fixed scope.
  • Confusing hours with story points: Some teams track hours remaining instead of story points. While this can work, it often leads to micromanagement. Story point burndowns give a higher-level view that is more useful for stakeholder communication.
  • Ignoring the chart until the sprint review: The burndown chart is most valuable when reviewed daily. If nobody looks at it until the sprint review, you have lost the opportunity to course-correct mid-sprint.
  • Panicking over single-day deviations: A one-day spike or plateau does not necessarily indicate a problem. Look at trends over 2-3 days before taking action. Natural variability is expected in knowledge work.

PMP Exam Tips

Sprint burndown charts are a core topic in the PMP exam, especially in questions related to Agile monitoring and controlling. Here is what to focus on:

PMBOK Guide 7th Edition: The "Delivery Performance" domain explicitly references burndown charts as a tool for monitoring iteration progress. Understand how burndown data feeds into the overall project performance measurement system. Know the difference between a sprint burndown and a release burndown chart.

Agile Practice Guide: The exam frequently tests your ability to interpret burndown chart patterns. You may be shown a chart and asked to identify what it reveals about team health. Know the common patterns: healthy steady decline, late surge (hockey stick), flat line (blocked team), and consistent overshoot (overcommitment).

Key exam concepts: The burndown chart is updated by the development team, not the Scrum Master or Product Owner. It is used during the Daily Scrum to facilitate the "three questions" conversation. On the exam, burndown charts are typically associated with the "monitor and control" aspect of Agile projects and the inspect-and-adapt principle of empirical process control.