Burndown Chart Example
I can describe a simple example of a burndown chart to help you understand how it typically looks and what information it conveys. In this example, we’ll consider a Scrum project with a two-week sprint.
Let’s assume the team has estimated work in story points, and they have a total of 40 story points planned for the sprint. The burndown chart might look like this:
- Day 0 (Start of Sprint):
- Total Story Points: 40
- Completed Story Points: 0
- Remaining Story Points: 40
- Ideal Burndown Line: A diagonal line from the top left (40) to the bottom right (0) over the 10 days.
- Day 3:
- Completed Story Points: 10
- Remaining Story Points: 30
- Day 5:
- Completed Story Points: 20
- Remaining Story Points: 20
- Day 8:
- Completed Story Points: 30
- Remaining Story Points: 10
- Day 10 (End of Sprint):
- Completed Story Points: 40
- Remaining Story Points: 0
- Ideal Burndown Line: Reached the bottom right corner
The burndown chart visually represents the progress of the team over the sprint. The x-axis typically represents time (in this case, the days of the sprint), and the y-axis represents the amount of work (in this case, story points). The actual burndown line shows the actual work completed each day, and the ideal burndown line represents the ideal progress if all work was completed evenly throughout the sprint.
In a healthy sprint, the actual burndown line should be close to or following the ideal burndown line, indicating that the team is on track. Deviations might suggest challenges that need attention, such as scope changes, impediments, or underestimated work. Burndown charts are powerful tools for teams to visualize their progress and make informed decisions during the sprint.

