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.
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.
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:
- Agile and Lean
- Scrum and Kanban
- 10 Expert Agile Tips and Techniques
- 12 Agile Principles
- Sample Kanban Boards
Pingback: Differences between Waterfall and Agile Methodologies
Pingback: 5 Habits that Successful Leaders Have | Read to Lead
Pingback: The Power of Positive Thoughts
Pingback: 8 Most Popular Connected Home Devices | Emerging Technology Trends
Pingback: Frequently Asked Questions on Bitcoins
Pingback: 4 Habits that Impact Your Productivity at Work | Getting Things Done
Pingback: Sample Kanban Boards - Practical Examples | Lean Thinking
Pingback: What is Technical Debt? | Learn Agile Scrum Framework
Pingback: Enterprise Agility - Expectations Vs Reality | Aditi Agarwal
Pingback: Virtual PI Planning Virtual PI Planning Preparation | COVID-19 | Aditi Agawal