Burndown chart--Agile programming

I. function

Burndown chart. The English name of the Burndown chart is called Burn down chart. is a publicly displayed chart that shows the number of unfinished tasks in the current sprint, or the number of unfinished order items on the punch order. Typically used for agile programming, here is a Burndown chart that represents meaning.

• The horizontal axis of this graph is the date and the vertical is the number of hours.
• The number of hours is the sum of the remaining work for all tasks in the project, calculated every day, forming coordinates, and then connecting the lines together to form this burndown chart.

Two. Elements

the elements of the Burndown chart are time and remaining work. Expressed in the form of an image.  

Three. Example

Spring_1

Analysis:

1.

Team members start the first sprint, the decomposition of the task is not proficient in the work of their own production efficiency is unclear. The result is a further refinement of the July 13 work task, resulting in a higher actual curve than the planned curve.

2.

Although, July 12 July 18, the actual curve is higher than the planned curve, but the trend of the actual curve coincides with the plan curve, indicating that the production rate of the team members is constant.

3.

On July 19, the actual curve fell back, and the development group submitted the iteration version to the test as a result of iterative system testing.

4.

The last work is still present, and there are problems in characterizing the member's work estimate.

5.

At this sprint review meeting, the team members agreed that "development and testing are closely integrated and release and testing can be released in a timely manner."

Spring_2

Analysis:

1.

July 25 July 29, the trend is basically normal.

2.

July 30, the actual curve rose, the analysis found that there is still insufficient granularity of task decomposition, the member found that the task of the more work needed to do more. The deep-seated reason is that when the task is decomposed at the beginning, due to the demand, design and other reasons, the task time estimate and the actual existence of large deviations.

3.

At this sprint review meeting, team members thought that "team work time is more accurate", but "the granularity of the task needs to be appropriate, the objectives to be clear, there is no cross-iteration." Task decomposition needs to be improved "

The above is about the analysis of the Agile record Burndown chart.

Burndown chart--Agile programming