What is Story Points?
Story points are a unit of estimation used in agile development to measure the relative effort, complexity, and uncertainty of a user story.
Story points are a unit of estimation used in agile development to measure the relative effort, complexity, and uncertainty of a user story. They use a modified Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) where higher numbers represent more effort and uncertainty.
Story points are relative, not absolute. A 5-point story is roughly 2.5x the effort of a 2-point story. The absolute time varies by team — one team's 5 might take 2 days while another team's 5 takes 4 days. This is fine because points measure relative effort within a team.
Story point criticisms: they're often misused as productivity metrics (comparing team velocities), they don't measure value (a 13-point story might deliver zero customer value), and they can be gamed (teams inflate points to look more productive).
Modern alternatives: cycle time (actual time from start to done), no estimation (just break stories into similarly-sized chunks), and outcome-based tracking (did we achieve the sprint goal?).
Why It Matters
Story points are the most widely used estimation method in agile development, but they're frequently misused. Using them to compare teams or as a performance metric destroys trust and accuracy.
Frequently Asked Questions
What are story points?
A relative estimation unit for measuring effort, complexity, and uncertainty of user stories. They use Fibonacci numbers (1, 2, 3, 5, 8, 13, 21).
Should you compare story points between teams?
Absolutely not. Story points are team-specific. One team 5 is not equivalent to another team 5. Comparing velocities between teams is meaningless and destructive.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →