Burndown Chart in Scrum Methodology
Projects are inclined towards uncontrolled growth in a project’s scope, at any point after their commencement. According to Scrum Theory, Scrum employs an iterative, incremental approach to optimize predictability and control risk; therefore, Burndown Chart is one of the methods implemented in the Scrum Theory to provide these benefits.
Burndown chart provides to monitor what is being accomplished by tracking the scrum projects with the information story point and time period (it can be sprint or the whole project). Hereby, unexpected timing problem can be handled and project goals can be achieved on time.
If there is a comprehensive analyse document and enough time to groom all of the items; ideal project burndown chart can be created. However, in real life, projects are not proceeded as they are planned (otherwise we do not need Agile methodologies). Scrum is capable of responding changes in the implementation period. Recent or revised requirements completely change the time estimation of development. Precisely in these cases, Burndown Chart will be helpful to monitor and balance the added/removed issues in the period. With all that, it helps to convince customer to stop requesting changes in the proceeding period and allow the sprint to be completed.
In addition to what is mentioned above, Burndown Charts provide various reports with data regarding modified issues/requests. With the help of these reports, it is possible making an inference about how quickly team has completed tasks, and predict when your team will achieve the goal or goals of the sprint. For example, Microsoft’s Visual Studio, goes further and includes ‘In Progress’ and ‘To Do’ status items on its Burndown Chart Graph. It is helpful to monitor how many hours remain for tasks that are marked as ‘In Progress’ and ‘To Do’ in a sprint on the same chart.
Let’s look at its infrastructure, it is very simple and basic. It is an ordinary x-y coordinated graph. The horizontal axis of the burndown chart shows the specified time period; the vertical axis shows the amount of work. Work remaining can be shown in whatever unit the team prefers — story points, ideal days, team days and so on. The Ideal Trend line indicates an ideal situation in which the team burns down all of the effort that remains at a constant rate by the end of the sprint.
Burndown chart provide to monitor below cases effects to the time line on the graph;
o Effects of estimation changes
o Effects of requirement changes
o Effects of new requests
In conclusion, seeing how progress is being made during each sprint is an essential necessity for project management. Therefore, effectiveness and simplicity of Burndown Chart makes it preferable to track remaining effort and story points.