Velocity and Burndown Charts
Level 4 Β· Stories, sizing and tracking
How velocity uses past sprints to plan the next one. How a burndown and a burnup chart show work left and work done, and which one hides added scope.
Course contentsLesson 16 of 19
Level 1 Β· What agile is
Level 2 Β· Scrum
Level 3 Β· Kanban
Level 4 Β· Stories, sizing and tracking
Level 5 Β· Other methods and scale
After this lesson you can
- Work out a team's velocity
- Read a burndown chart
- Choose a burnup when scope changes
12 mincovers 3 glossary entries
Worth reading first: Story Points and Estimation
How teams track progress in a sprint and a release
Velocity is how much work a team finishes in one sprint, often in story points. Only fully done work counts. Teams average the last few sprints to plan the next. A team that finished 18, 22, 20, 24 and 21 points has an average of 21, so it plans about 21 for the next sprint.
Velocity is a planning tool for one team. It is not in the Scrum Guide, and it is not a score. Comparing two teams' velocity means nothing, because their points mean different things. Pushing a team to raise it only teaches them to give bigger numbers.
A burndown chart shows how much work is left over time. Work left runs up the side, and days run along the bottom. A straight ideal line runs from the start total down to zero on the last day. The real line shows what is truly left each day.
If the real line sits above the ideal line, the team is behind. On a 10-day sprint that starts at 40 points, the ideal pace is 4 a day. With 24 points left on day 6, the team is 8 points behind, since the ideal is 16 left.
A burnup chart shows the same work the other way. One line climbs as work is done. A second line shows the total scope. When they meet, the work is finished.
The burnup's second line is the reason to use it. When work is added, the scope line jumps up, and everyone can see it. On a burndown, added work just makes the line flatter, so it looks as if the team slowed down.
The common mistake is reading a flat burndown as a lazy team. Check first whether work was added. The other mistake is counting half-done items as progress, which makes the line drop on paper and climb back later.
Worked example
Lucy's burnup shows the real story
Lucy's burndown for a release looks flat for 3 sprints, and her manager thinks the team has slowed. She switches to a burnup.
The work done line climbed by about 20 points every sprint. The scope line jumped from 60 to 80 points, because 20 points of new work were added. The team was fine. The plan had grown.
The words for this lesson3
Check yourself
Scope keeps being added to a release. Which chart shows that clearly?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.