Velocity vs Throughput
People think velocity and throughput are the same number. Velocity adds up the story points a team finishes in a sprint. Throughput counts the items it finishes in a week, with no sizes. Both help a team forecast, but only velocity needs the work sized first.
Velocity
How much work a team finishes per sprint, often in story points. Used to plan ahead.
Velocity is how much work a team finishes in one sprint, often counted in story points. Only work that is fully done counts. Teams take the average of the last few sprints to plan the next one. The Scrum Guide does not define it, but many Scrum teams use it. It is a planning tool for one team, not a score to compare teams.
Velocity = story points of done work in one sprintThroughput
How many items a team finishes in a set time. For example, five items a week.
Throughput is how many pieces of work a team finishes in a set time, like a week. It counts finished items, not started ones. Teams use it to forecast how much they can deliver. It is tied to work in progress and cycle time by a rule called Little's Law. On average, work in progress equals throughput times cycle time.
Average work in progress = average throughput x average cycle time (Little's Law)In one line
- Velocity
- How much work a team finishes per sprint, often in story points. Used to plan ahead.
- Throughput
- How many items a team finishes in a set time. For example, five items a week.