What is Story Points?
Story points are a unit of relative estimation. Instead of estimating work in hours, teams assign points that capture a story's overall size — a blend of effort, complexity, and uncertainty — relative to other stories. Many teams use a Fibonacci-like scale (1, 2, 3, 5, 8, 13) to reflect that larger items carry more uncertainty.
The point of relative sizing is that humans are better at saying "this is about twice as hard as that" than at predicting exact durations. Over time, the team's points-per-sprint (velocity) translates into a dependable forecast without forcing false precision.
PMs don't usually assign points — engineers do, often via planning poker — but PMs rely on the output. Understanding that a 13-point story is risky and probably should be split is valuable for keeping the backlog shippable.
Examples
- A team sizes a small copy change as 1 point and a new integration as 8 points.
- During planning poker, a wide spread in estimates triggers a discussion that surfaces a hidden dependency.
Where PMs use this
Related terms
Velocity
A measure of how much work a team completes in a sprint, used to forecast future capacity.
User Story
A short, plain-language description of a feature told from the perspective of the user who wants it.
Sprint Planning
The meeting where a team selects and commits to the work it will complete in the upcoming sprint.