Q. What is a burndown chart?
Ans: A burndown chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. (Wikipedia)
If the end date is considerably earlier than the Sprint completion date, then more work is added from the Product Backlog. If the end date is considerably later than the Sprint completion date, then enough of the lowest priority tasks are removed from the Sprint backlog to meet the date. It is really important that the Sprint completion date does not change!
Where the blue line goes below the red line, the rate of progress is less than that what we planned for. Where it rises above the red line, the progress is greater than what we planned for.
If the line is flat, well, maybe the chart is not updated, or it means task deferred or postponed.
Burndown Chart
- Shows work of team during sprint.
- Where you are right now? Above or below the line.
- Adding another story -> Changes velocity.
Q. Why to create a burndown chart?
Ans: A Burndown chart is created to measure progress. The information on a burndown chart allows Scrum Master to know if the Scrum team is missing, meeting or exceeding the progress goals for that particular sprint.
Burndown Chart answers the following questions:
1. How fast is the team completing remaining work?
2. Is the team adding work during the iteration? Is there scope creep?
3. How much work can the team complete in the available time?
4. When can the team finish the work?
5. When can the team finish the current iteration? {Source}
Q. What types of burndown chart are there?
Ans: Usually (but not limited to) two types of burndown charts are created:
1. Sprint Burndown Chart
2. Release Burndown Chart
Q. What are the advantages of Burndown Chart?
Ans: Immediate understanding of the Sprint work (i.e. if we are on, behind or ahead of the planned schedule etc.)
Q. What are the disadvantages of Burndown Chart?
Ans: We cannot judge what are the risks at a particular point in time or what are the risks due to which we are behind the schedule or not able to progress etc.
Q. Give an example of a burndown chart.
Ans:
Q: How do you show scope changes in the burndown chart?
Ans:
One way can be:
Another way can be:
Also See:
Sprint Velocity & Focus Factor
References:
Scrumalliance
Scrumftw
Alistair
Agilekiwi
Scruminfo
Scrum_summary[pdf] from Helpserve