Skip to content
BENIBIX Learn

Velocity

Business📋 Agile DeliveryPlanning

Also known as Team Velocity, Sprint Velocity

How much work a team finishes per sprint, often in story points. Used to plan ahead.

Think of it like

It is like counting how many pages you read each night. After a week, you know how long a book will take.

Example

Over five sprints, Jack's team finishes 18, 22, 20, 24 and 21 points. The average is 21, so they plan about 21 points for the next sprint.

Why it matters

It turns past sprints into a fair forecast. Release dates come from it.

Formula

Velocity = story points of done work in one sprint

Definition

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.
Five sprints, one average. The next sprint is planned near that line, not near the best bar.

Common mistake

Pushing a team to raise its velocity. The team just sizes stories bigger, and the number stops meaning a thing.

Key takeaways

  1. 1
    Done work only. Half-finished stories count for nothing.
  2. 2
    Use the average. A few sprints smooth out the bumps.
  3. 3
    Not a target. A goal for velocity breaks the number.

Compare

Learn it properly