Provide a summary of this practice.
A burn chart is a simple, widely used work tracking tool that makes it easy to predict the outcome of an iteration or release and take corrective or preventive action where it’s needed. It shows in a simple format the team’s ‘earned value’.
What is the overall goal or intention of this practice?
What are the schedule, cost, quality, frequency, performance or other expectations for completing this practice?
Status should be reported and the burn chart updated at least daily.
What must have happened or been delivered for this practice to be considered complete?
Burn charts continue to be used for as long as the iteration (or release) continues.
What pre-conditions must be met before this practice is used?
Burn charts cannot be useful until:
This view shows a simplified version of this process. For full details, explanation and advice, click on the ‘Detailed process’ tab. For background such as entry and exit conditions, click on the ‘Context’ tab.
|1||Prepare burn chart|
|2||Maintain burn chart|
|3||Analyse burn chart|
|1||Prepare burn chart||Iteration Lead.||Initial burn chart.|
|2||Maintain burn chart||Iteration Lead.|
|Updated burn chart.|
|3||Analyse burn chart||Iteration Lead.|
|Progress & status reports|
Issues & risks
What are the key concerns in making a success of this practice?
- For more about burn charts, click here.
- Burn charts can be used at both iteration & release level. Iteration-level charts can also be added together to project the probable outcome of a complete release.
- Burn charts are very powerful communications tools for the Product Owner, senior management and other stakeholders but only if they are accurate and up to date.
- Daily progress tracking requires discipline.
- But it provides the extra visibility of real progress, risk, obstacles and dependencies on which Agile relies.
- It is valuable to record the specific impediments and opportunities that will affect how delivery progresses.
- It makes it easier to identify recurring patterns & problems.
- Alternatively, consider using a highly visible Improvement Board.
- Problems fixed informally can be neglected. If they are recorded directly on the burn chart, this will:
- keep them in the team’s mind.
- encourage synergistic solutions across multiple problems/stories/iterations.
- provide usefully explicit input to your subsequent Retrospective.