Scrum

What is Story Points?

Q: What is Story Points?

Story Points are a relative unit of effort estimation used by agile teams. They do not measure hours: they measure the size of a work item compared to others already known, taking into account complexity, uncertainty and amount of work. Estimating in points decouples the estimate from individual speed and from exact-date pressure.

Story Points are a relative unit of effort estimation used by agile teams. They do not measure hours: they measure the size of a work item compared to others already known, taking into account complexity, uncertainty and amount of work. Estimating in points decouples the estimate from individual speed and from exact-date pressure.

In practice

Teams use Story Points in Planning Poker or item-comparison sessions, with scales like Fibonacci (1, 2, 3, 5, 8, 13). The team picks a reference story (say, a 3) and calibrates the rest against it. Combined with historical Velocity (how many points the team delivers per Sprint), points become a basis for forecasting. The best results come from combining points with real flow metrics — lead time and throughput — for more reliable forecasts without the trap of promising fake dates. K21's A-CSPO course covers this in depth.

What happens when it is missing

Teams that estimate in person-hours or person-days fall into the trap of treating estimates as deadline commitments. When an item takes longer (which is normal in complex environments), the team is held accountable for the "promise" and starts inflating estimates to protect itself. The whole process becomes defensive theater, real predictability drops, and nobody learns the team's true capacity.