Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 41 ยท Agile and Scrum

Sprint Planning, Velocity and Burndown

Plan sprints with story points, capacity and velocity, forecast release dates and read burndown charts, with runnable Python for velocity, forecasts and burndown data.

Agile teams still need to answer "how much can we do?" and "when will it be ready?". They do it with relative estimates, measured velocity and visible progress charts, not with promises made months ago. This lesson covers the practical numbers behind Scrum: story points, capacity, velocity, forecasting and the burndown chart.

Estimating with story points

A story point is a unit of relative size. It combines effort, complexity and uncertainty, and it is not hours. The team picks a reference story ("Email confirmation = 2 points") and sizes everything else against it: is this twice as big? half? Most teams use a Fibonacci-like scale (1, 2, 3, 5, 8, 13) because the gaps widen as uncertainty grows, so nobody argues whether something is 6 or 7.

Planning poker is the usual technique: each person privately picks a card, everyone reveals at once, and the highest and lowest voters explain their reasoning. The goal is the conversation; the team re-votes until the numbers converge. Anything above 8 or 13 is a signal to split the story.

Relative sizing works because people judge "bigger than" better than "exactly 17.5 hours", and because the errors average out across many stories.

Velocity

Velocity is the number of points the team completes (to the Definition of Done) per sprint. Count only fully done items; partial credit hides unfinished work. After a few sprints, the average gives a reliable planning range.

Python Average velocity and a planning range

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Velocity belongs to one team. Comparing teams' velocities, or setting velocity as a target, makes the numbers inflate and destroys their value. Velocity is a planning aid, not a performance measure.

Capacity and the sprint backlog

During Sprint Planning the Developers combine velocity with this sprint's capacity: holidays, training, support rotations, and part-time members all reduce it. Then they choose backlog items from the top until the forecast is full, and write a Sprint Goal.

Python Capacity-adjusted sprint forecast

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Velocity already includes the team's usual overhead (meetings, support), so only subtract the unusual absences; do not apply an overhead factor twice.

Tasks and hours inside the sprint

After choosing stories, the team breaks them into tasks (a day or less each) and may estimate remaining hours to track progress. The sprint backlog is the team's plan; it is expected to change as they learn, as long as the Sprint Goal stays intact.

The burndown chart

A sprint burndown chart plots remaining work (points or hours) against sprint days. An ideal line goes straight from the total to zero. The actual line shows reality: flat stretches mean no work finished, a rise means scope was added or estimates grew.

Python Sprint burndown data and status

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

How to read it:

  • Above the ideal line: behind. Talk about it in the Daily Scrum; do not wait for the Review.
  • Flat for several days: work is blocked, or stories are too big and not yet finished (a sign to split stories smaller).
  • Burns all at the end: items finish in a rush on the last day; the team is probably working on too many things in parallel.
  • Goes up: scope was added, or estimates were wrong.

A release burndown (or burnup) does the same at product level, sprint by sprint. A burnup chart plots work done upward and the total scope as a separate line, so scope changes are visible instead of hiding in a falling line.

Forecasting a release

If the backlog for a release is 130 points and velocity is 20 per sprint, that is 6.5, so about 7 sprints. But a single number is a promise you cannot keep. Use the range of your recent velocities to give a best, likely and worst case, or run a simulation by sampling past sprints.

Python Forecast release date with a Monte Carlo of velocities

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

This is the same idea as Monte Carlo schedule risk, using real past data instead of guesses.

Healthy habits

  • Finish stories, not start them. Limit work in progress (see Kanban).
  • Protect the Sprint Goal; negotiate scope, not quality.
  • Keep estimates cheap. If you spend a day estimating, you lost more than the estimates are worth.
  • Re-baseline with data. New team or new technology: expect velocity to drop, then settle.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a story point?

    Story points are relative; they are not converted to hours.
  2. 2. A team completed 20, 22 and 18 points in the last three sprints. How should the next sprint be planned?

    Use recent average velocity, adjusted for planned absences and other capacity changes.
  3. 3. On a burndown chart, a line that stays flat for four days suggests:

    No remaining work is burning, so nothing is being finished: investigate blockers or story size.
  4. 4. Why is velocity a poor performance target?

    Goodhart's law: when a measure becomes a target, it stops being a good measure.

Summary

  • Story points are relative sizes; planning poker generates discussion.
  • Velocity is the average of fully done points per sprint; use it with capacity to forecast.
  • A burndown shows remaining work against an ideal line; flat or rising lines are conversation starters.
  • Forecast releases with ranges or simulation from past velocities.
  • Do not turn velocity into a target.

Next: Kanban and Flow Metrics