The Sprint Burndown or the Iteration Burndown chart is a powerful tool to communicate daily progress to the stakeholders. It tracks the completion of work for a given sprint or an iteration. The horizontal axis represents the days within a Sprint. The vertical axis represents the hours remaining to complete the committed work. The purpose of a sprint burndown chart is to show the total amount of work remaining.

Let's take an example. The below table shows the actual number of hours remaining at the end of each day within a Sprint to create a sample Sprint burndown chart. The table also captures data for ideal remaining hours. The ideal remaining effort is calculated by assuming a uniform rate of task completion each day. In the below example, you can see that the ideal and actual remaining hours were same at the beginning of the sprint, however, as the sprint progresses, the actual remaining hours vary from the ideal remaining hours. 

Sprint Burndown Chart Table

Next, we will plot a sample Sprint Burndown chart using the above table data. The below diagram depicts the sample chart with ‘Date’ represented on the horizontal axis and ‘Remaining Effort (Hours)’ represented on the vertical axis. 

Sample Sprint Burndown Chart

From the above chart, you can conclude that:

  • There were no spillover stories since the actual remaining hours at the end of the sprint were zero.
  • The team started a bit slow in the first week of the sprint, but then caught-up during the second week.

Other articles that you may be interested in:

Learn all about Agile Scrum with my book, The Basics Of SCRUM. Other Books:

Posted in Agile Scrum and tagged , , , , , , .


  1. Pingback: Differences between Waterfall and Agile Methodologies

  2. Pingback: 5 Habits that Successful Leaders Have | Read to Lead

  3. Pingback: The Power of Positive Thoughts

  4. Pingback: 8 Most Popular Connected Home Devices | Emerging Technology Trends

  5. Pingback: Frequently Asked Questions on Bitcoins

  6. Pingback: 4 Habits that Impact Your Productivity at Work | Getting Things Done

  7. Pingback: Sample Kanban Boards - Practical Examples | Lean Thinking

  8. Pingback: What is Technical Debt? | Learn Agile Scrum Framework

  9. Pingback: Enterprise Agility - Expectations Vs Reality | Aditi Agarwal

  10. Pingback: Virtual PI Planning Virtual PI Planning Preparation | COVID-19 | Aditi Agawal

  11. Pingback: Agile Anti-Patterns For Remote Teams | COVID-19 | Aditi Agawal

Leave a Reply

Your email address will not be published. Required fields are marked *