Burndown chart is nothing but a graphical representation of amount of work left to be completed versus the time. It can also be called as RUN chart displaying the data in time sequence. It is a picturesque depicting what hundred words put together might not be able to communicate so effectively.
The amount of work remaining is shown on the vertical axis (Y axis) and the time passed since the project has begun is shown on the horizontal axis (X axis).
Burndown chart find their origin since Scrum is designed. It has been observed Burndown charts were never part of managing any software project or other effort. It was formally described by none other than Ken Schwaber in the year 2000 while working at Fidelity Investments to create simple tool kit for scrum team.
In the year 2002, its popularity got increased in the Scrum community and so was its implementation along with Burn Up chart which merely inverts the vertical direction and used for better understanding of releases in the sprint.
Burndown chart are broadly classified in two, Sprint burndown chart for remaining work items in the sprint. Product Burndown chart for work remaining in the project at large.
Sprint Burndown chart- The Sprint burndown chart depicts the working to be completed in the sprint. Just like the generic burndown chart, the Y-axis denotes the efforts remaining in terms of Story points and X-axis measures time (e.g.- if duration of sprint in 4 weeks it will display duration of 4 weeks) in the sprint. It gives a visibility to the management about how much work is left in the sprint backlog to be completed and predict when can the development team is likely to complete their sprint goal.
Release/Iteration Burndown chart- Release/Iteration burndown chart is used for tracking team’s progress over period of Release/Iteration. The Y-axis of the release burndown chart is hours or story points, whereas the x-axis of the chart is time (spanning over the duration of a release/iteration).
Agile burndown chart demonstrates several key points. On the X-axis, the project or iteration timeline is defined. On the Y-axis, the amount of work that needs to get accomplished in the project is defined. The story point estimates for the work that remains is represented by this axis. Each day amount of work remaining will be calculated by subtracting from the total effort. Burndown chart gives an overall idea if the project is heading in the right direction as perceived by the ideal line which is drawn by calculating the number of hours ideally team would require completing the task they are working on through the sprint.
Benefits of Burndown chart are mentioned below:
1) Team members can save time by tracking the progress of the sprint visually instead of sorting through email, tasks and documents for status update.
2) Project managers can get better view of the sprint and plan more effectively.
3) Burndown chart can help team members to constantly evaluate team performance daily and prioritize work based on the status thereby alerting teams about bottleneck situation and issues at hand.
4) It acts as an information radiator that gives instant status of the sprint.
5) Act as a motivator to the team
Limitations of the Sprint burndown chart are listed below:
1) It focusses on the task completed but not on what task is in progress
2) It does not show impact of scope changes
Purpose of sprint burndown chart is utmost when the team needs to know about the amount of work remaining.
It can be used to gain insight into how team is working. For example:
• In case the team finishes the work early the burndown chart can be a sign they aren’t committing to enough work during planning.
• In case the team is unable to finish the work, burndown chart can be a sign they are committing too much work.
• In case there is a sharp drop in the burndown chart, it can be an indicator that work has not been estimated accurately or split properly.
Burndown charts can be created in excel or tools such as JIRA (Jira burndown chart)
Below mentioned are steps on how to create burndown chart in excel:
1) Create Estimate Effort
2) Tracking Daily Process
3) Computation of the Actual Effort
4) Derive the final dataset
5) Plot the Chart using the final dataset
1) Go to Project
2) Choose a Specific project.
3) Click on the Report icon on the left side of the menu.
4) Go to Agile and click on Burndown chart.
As the team is self-organising, the onus to create and update Burndown chart lies with the development team. It can be argued that the scrum master can create and update the Burndown chart but as the team works closely on task themselves, it can motivate team to see the success closely in terms of tasks completed and if the chart doesn’t show positive graph they can take necessary steps to avoid further debacle.
In a way, Burn down chart is very important for any project in agile to get a picture of how much work is pending and how much has been completed by team during each Sprint. Since agile doesn’t come with much documentation, burn down chart can be definitely be one great matrix.
To understand more about Sprint burndown and release burndown charts attend StarAgile. certified scrum master certification or call us at +91 – 95133 93880
>4.5 ratings in Google