Story Points Guide
Relative effort estimation in agile teams.
PURPOSE
Time-based estimates in hours or days are notoriously inaccurate in software development and lead to unrealistic expectations. Story Points measure relative complexity instead and enable more reliable predictions over multiple sprints. They decouple estimation from individual speed and promote team-based thinking.
HOW TO USE
The team agrees on a reference story as a baseline and estimates all further stories relative to it. The scale typically uses Fibonacci numbers (1, 2, 3, 5, 8, 13) to reflect the increasing uncertainty with larger stories. Over multiple sprints, a velocity emerges that can be used for capacity planning.
WHAT IT IS
Story Points are a unit of measure for relative estimation of effort, complexity, and uncertainty in agile teams. They don't represent an absolute measure but rather the relationship between different tasks. The Story Points Guide by Atlassian explains the methodology, scaling, and best practices for introducing relative estimation in a team.
EXAMPLE
Example: Your new team member asks why you estimate in 'points' instead of hours. With the Story Points Guide, you explain the concept of relative estimation: a story with 5 points is roughly twice as complex as one with 3, but whether it takes 2 or 4 days depends on many factors. The Fibonacci sequence makes estimation uncertainty visible for larger stories.