Story Points

Updated September 30, 20262 min read

In short

Story points are a unit Agile teams use to estimate the relative size of work items, combining complexity, amount of work, and uncertainty rather than hours.

What are story points?

Story points are an abstract unit for estimating how big a piece of work is compared with other pieces of work. Instead of guessing hours, the team asks whether a story is bigger or smaller than a reference story it already understands. A story's points reflect the amount of work, its complexity, and the uncertainty or risk involved.

Teams usually estimate with a limited scale, often based on the Fibonacci sequence, such as 1, 2, 3, 5, 8, 13, and 21, because the growing gaps reflect that big items are harder to estimate precisely. A popular technique is planning poker: each person picks a card privately, everyone reveals at once, and the people with the highest and lowest estimates explain their reasoning before the team votes again. The total number of points a team completes per sprint is called its velocity, which helps forecast how much work fits in future sprints.

Estimating with story points is like comparing moving boxes instead of weighing them. You may not know the exact weight of each box, but you can quickly agree that the box of books is heavier than the box of pillows, and relative judgments like that tend to be more reliable than absolute ones.

Story points are often confused with time estimates, but a 5-point story does not mean five hours or five days, and the same story may take different amounts of time for different people. Velocity is specific to one team, so comparing points across teams or using them to measure individual productivity is misleading. Story points are not required by Scrum, and some teams prefer simpler methods such as t-shirt sizes or just counting finished items.

Key takeaways

Story points measure relative size, not hours or days.
They combine the amount of work, complexity, and uncertainty.
Fibonacci-like scales such as 1, 2, 3, 5, 8, 13 are common.
Velocity is the number of points a team completes in a sprint.
Points and velocity should not be compared across teams.

Example

Estimating a backlog and tracking velocityyaml

# Reference story: "Add a logout button" = 1 point
scale: [1, 2, 3, 5, 8, 13, 21]
backlog:
  - story: Show order history
    points: 3
  - story: Reset password by email
    points: 5
  - story: Pay with saved cards
    points: 13   # large and uncertain: consider splitting
velocity:        # points completed in recent sprints
  sprint_12: 21
  sprint_13: 18
  sprint_14: 24
forecast: about 21 points per sprint

Readers ask

How many hours is one story point?

There is no fixed conversion. Story points are deliberately relative, and converting them to hours turns them back into time estimates, which defeats their purpose.

Why do story points use the Fibonacci sequence?

The widening gaps between numbers, such as 8 and 13, reflect that larger work carries more uncertainty. They also stop teams from arguing over small differences, such as 7 versus 8, that nobody can estimate precisely.

What is velocity in Agile?

Velocity is the amount of work, often measured in story points, that a team completes in a sprint. It is used to forecast future sprints, not to compare teams or rate individuals.