What is Story Points?
Story points are a relative unit teams use to estimate the effort required to complete a piece of work, rather than measuring it in hours or days. Items are sized by comparison with one another, often on a modified Fibonacci scale, capturing effort, complexity and uncertainty together.
Reviewed by Gensudo Team · 23 July 2026
In more depth
Story points express how big one item is relative to others, not how long it will take in absolute time. Teams commonly use a scale such as 1, 2, 3, 5, 8, 13, estimate collaboratively through techniques like Planning Poker, and derive velocity, the points completed per sprint, to forecast. Mike Cohn stresses that points reflect effort, not complexity alone, and that their value lies in the relative comparison.
Why it matters
Time-based estimates invite false precision and pressure, and they differ by who happens to do the work. Relative sizing sidesteps this by focusing on comparison, which people do more reliably than absolute prediction, and it enables forecasting through velocity without pretending an estimate is a commitment. Points also spark the useful conversations that surface hidden complexity before work starts.
A product example
A team sizes a login form at 3 points and a new billing integration at 13, agreeing the integration is far larger and riskier without arguing over exact hours. Over several sprints they average 30 points, which they use to forecast the release date.
Related terms
User Story · Product Backlog · Epic · Acceptance Criteria