About "Burndown Chart"

Burndown chart (burn down chart) is a visual representation of the work that needs to be done before the project is completed. The Burndown chart has a y-axis (work) and x-axis (time). Ideally, the chart is a downward curve, with the remaining work completed, "Burnt" to 0. Burndown charts provide a public view of the work progress of project team members and business owners.

In layman's terms, the Burndown chart describes the amount of work remaining over time, as well as an intuitive representation of the speed of a project and can be compared with the expected progress curve.

The two main elements of Burndown chart are workload and time point.

Workload refers to the amount of work remaining, measured in story. There are many stories to be developed for each iteration, and in agile development, the workload is evaluated in story, and the number of an iteration story affects the y-axis of the Burndown chart.

Time is the work time, with the remaining work to reflect the progress of a project, as shown in the actual progress of the project is not as good as the ideal plan effect.

　　　　

At the same time, I also have a little doubt about the Burndown chart, as a project, if the teacher said that the customer can change the demand at any time, then the significance of this picture, for each modification, should be redrawn, or correction curve?

About "Burndown Chart"