Story Points Explained

Story points are a unit agile teams use to estimate the size of backlog items. They combine effort, complexity, and risk into a single relative number. Crucially, story points are not hours — a 5-point story is not "five hours." It means "about this much work compared to other stories we have pointed."

What story points capture

• Effort — How much work across design, build, test, and release?
• Complexity — How hard is the problem or how many unknowns exist?
• Risk — Dependencies, new technology, or compliance constraints that might slow delivery?

Two stories might take similar calendar time for one developer but earn different points because one touches a fragile legacy module. Points encode that team-level judgment.

Why not estimate in hours?

Hours imply precision the team does not have early in refinement. Different people finish the same task at different speeds; story points use the team's collective view. Hours also encourage managers outside the team to convert points to deadlines without context. Velocity — points completed per sprint — is a planning tool for the team, not a performance metric for individuals.

Relative estimation in practice

Teams pick a baseline story everyone remembers, assign it a middle value (often 5 on Fibonacci), and compare new work to that anchor. "This feels twice as big as the login story" → higher points. Over sprints, velocity stabilizes enough to forecast how many points fit in the next iteration.

Story points and velocity

Velocity is the sum of completed story points in a sprint. It fluctuates early on; after three to five sprints, teams use average velocity for capacity planning. Velocity is meaningful only if pointing stays consistent — changing scales or inflating points to "look productive" destroys the signal.

Common mistakes

• Converting points to hours for external reporting without team agreement
• Comparing velocity across teams — each team calibrates differently
• Re-pointing completed work because actual time differed from expectation
• Using points as individual performance scores

How planning poker assigns story points

Planning poker is the most common way teams agree on point values. Private votes and discussion turn individual guesses into a team number. Learn the full ceremony in What Is Planning Poker? and practice with PlanITPoker's Fibonacci deck.