A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.
Story points are a relative estimation method in Agile that helps teams assess effort, complexity, and risk for backlog items. Unlike time-based estimates (hours or days), story points represent relative complexity, effort, and risk.
What Are Story Points?
Story points consider:
Complexity: How technically challenging is the work?
Risk: What unknowns or dependencies exist?
Amount of work: How much needs to be done?
Story points do NOT equal hours. A 5-point story isn't "5 hours of work."
Why Use Story Points Instead of Hours?
Benefits of Story Points:
Team Collaboration: Encourages team discussion and consensus
Reduced Bias: Less emotional attachment than hourly estimates
Better Forecasting: Improves accuracy over time
Accounts for Uncertainty: Better for complex, uncertain work
Focuses on Value: Emphasizes what's being delivered, not just time spent
Researchers have found that this improves estimate accuracy, especially on items with a lot of uncertainty as we find on most software projects.
The Fibonacci Sequence
Story points typically use a modified Fibonacci sequence:
1, 2, 3, 5, 8, 13, 20, 40, 100
Why Fibonacci?
Reflects uncertainty in larger estimates
Larger gaps for larger items acknowledges less precision
Forces meaningful distinctions
Prevents false precision (no "4.5" story points)
Scale Interpretation:
1-2: Very small, simple tasks
3-5: Small to medium complexity
8-13: Medium to large complexity
20+: Very large, should probably be broken down
100: Epic/too large to estimate accurately
Planning Poker
Planning Poker® is a consensus-based technique for agile estimating.
How It Works:
Present Item: Team discusses a user story from the backlog
