Thuật ngữ Burn Down Chart trong Agile là gì? Luyện thi PMI-ACP
Burn Down Chart is a graphical representation of “work remaining” vs “time remaining”
Make project events (e.g. fluctuating team velocity, new stories added, etc.) visible for expectation management
A major way to report Agile metrics
A burn-down chart shows:
- How much work has been done?
- How much work remains?
- The team’s velocity (the slope of the chart)
Risk Burn Down Charts / Graphs
- To show the risk exposure of the project
- Created by plotting the sum of the agreed risk exposure values (impact x probability) against iterations
- To be updated regularly (per iteration) to reflect the change in risk exposure
- General recommendation: top 10 risks are included
- The risk burn down chart should have the total risks heading down while the project progresses
SCRUM BURN DOWN CHART
The Scrum Burndown Chart is a visual measurement tool that shows the completed work per day against the projected rate of completion for the current project release. Its purpose is to enable that the project is on the track to deliver the expected solution within the desired schedule.
Simple burn down chart
The rate of progress of a Scrum Team is called “velocity”. It expresses the amount of e.g. story points completed per iteration. An import rule for calculating the velocity is that only stories that are completed at the end of the iteration are counted. Counting partially finished work (e.g. coding only – test missing) is strictly forbidden.
After a few Sprints the velocity of a Scrum Team will most likely be predictable and would allow quite accurate estimation about the time needed until all entries in the Scrum Product Backlog will be completed. If the velocity of a Scrum Team is e.g. 30 story points and the total amount of remaining work is 155, we can predict that we need about 6 Sprint to complete all stories in the Backlog.
However in reality the entries in the Scrum Product Backlog will change over the duration of the project. New stories are added and other stories are changed or even deleted. In the simple Burndown Chart the velocity of the Scrum Team and the change in the scope cannot be distinguished. To reflect this, another form of diagram can be used.
Separating Scope and Velocity changes
Here a bar chart instead of a line diagram is used. The size of each bar represents the total amount of work remaining at the start of each sprint. The velocity of the team is subtracted from the top while changes in the Scope change the bottom of the bar.
To get even more accurate we can also take the rate of changes in total work into account. However we have to be careful when using this model since the rate of change will be high in the beginning of the project but will drop at the end.
Extended burn down chart with prediction
SPRINT BURN DOWN REPORTS / CHARTS
The Sprint Burndown Report shows the progress within the Sprint toward reaching the Sprint Goal. It provides transparency about the current performance (burndown rate) and allows easy estimation if the Sprint Goal can be reached in time or if the team has to find additional measures to speed-up completion of the remaining activities.
Example Sprint Burn Down Report/Chart
The initial Sprint Backlog defines the start-point for the remaining efforts. The remaining effort of all activities are collected on a daily base and added to the graph. In the beginning the performance is often not as good as predicted by the ideal burndown rate due to wrong estimations or impediments that have to be removed in order to get on full speed.
Nếu có bất cứ chia sẻ về luyện thi PMP, PMI-RMP, PMI-ACP hay góp ý bạn vui lòng chia sẻ ở dưới phần bình luận. Tôi rất vui lòng về điều đó. Cảm ơn.