Burndown chart-A visual display of work completion

Burndown chart-A visual display of work completion

Burndown Chart Burdown Chart is also called a Burn chart, which 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. This word is often used in agile development ( Agile Development refers to the evolution of the user's needs as the core, using an iterative, incremental approach to software development. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features.

function: describes the amount of work remaining over time and can be used to indicate development speed.

elements: X-axis: time; y-axis: Remaining work.

Example:

Some common scenarios for burndown graphs are:

　　1. First summon up and fall: The reason is that the plan will often miss some things, so after the start not only do not burn out, but also found a lot of new tasks.

2. First perfect combustion, then suddenly stop burning: Because the task is divided too thick, resulting in a wrong estimate of the workload, until the last discovery of the remaining time is difficult to complete.

3. Burn slowly, then go to the burning out of the time left a pile of unfinished tasks, be postponed to the next cycle: Some tasks are secondary "can not do", or is passively found that some stories are not completed.

......

Kane Mar divides the burndown chart into the following seven scenarios: 1, Fakey-fakey: The surface is perfect. Software projects are so complex that it is difficult to define visual targets.　　In most cases, this figure comes from an environment full of command and control, in which open communication becomes difficult. 2, Late-learner: The Burndown chart will have a peak.　　Often appear in teams that communicate efficiently and are learning scrum. 3, Middle-learner: more mature than Late-learner.　　The team explored most of the tasks and complexities in the middle of the sprint. 4, Early-learner: Start with a peak, then a flat recession.　　The team recognizes the importance of early exploration and then works efficiently to achieve its goals.　　5. Plateau: The team made great progress at the beginning, but lost direction in the latter part of the sprint. 6, Never-never: Burndown chart suddenly began to rise in the late sprint and will not fall again.　　These late changes need to be found as soon as possible and introspective. 7, the workload of scope-increase:sprint suddenly increased.                            This usually indicates that the team did not fully recognize the scope of the work at the Sprint planning meeting. ———— excerpt from: Burndown chart _ Baidu Encyclopedia

Burndown charts can be used to indicate the speed of development, which is true. But when analyzing burndown charts, you still have to recognize some of the things behind this picture.

The Burndown chart describes the amount of work remaining over time. 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. If the number of stories is too small, the resulting Burndown chart will have a pronounced polyline shape and will have an impact on the speed and risk judgments. Therefore, the curve does not necessarily represent the amount of work remaining.

In addition, the split granularity of story has a great influence on the Burndown chart. The smaller the split granularity of the story, the more it reflects the real situation. But it is not as small as possible, if the story is split into the amount of work that can be measured in person, then the team's workload estimation accuracy will be higher requirements, but also bring more role exchange costs.

Also, comparing the burndown graphs of multiple iterations is not necessarily indicative of the change between iterations. There are many factors that affect the results, such as whether the granularity of the story split is the same, whether the team members have changes, whether the time period is consistent, etc., so the comparison should be combined with various factors to draw conclusions.

Team members also affect the depiction of burndown charts. When they find out that the chart is still being used for performance appraisals, they tend to make the curve more beautiful and conceal the true completion result, or discount the "done" standard. In other words, although the Burndown chart curve reaches the x-axis, there is actually a lot of work to do, and this is a trap.

———— Excerpt: http://blog.csdn.net/caowenbin/article/details/8461148

Burndown chart-A visual display of work completion