What Are Story Points in Agile?
Understand story points, how they differ from hours, and why agile teams use them for estimation. Includes practical examples for Scrum and Kanban teams.
Fundamentals
Detailed Explanation
What Are Story Points?
Story points are a relative unit of measure used by agile teams to express the overall effort required to implement a product backlog item. Unlike hours or days, story points compare items to each other rather than predicting calendar time.
Key Characteristics
- Relative, not absolute -- A 5-point story is roughly twice as complex as a 3-point story, but nobody claims it takes exactly 10 hours.
- Include everything -- Effort, complexity, risk, and uncertainty are all baked into the number.
- Team-specific -- One team's "5" may be another team's "8." Cross-team comparison is meaningless.
How They Work
- The team picks a reference story that everyone understands (often a 3 or 5).
- Every new story is compared to that reference: "Is this bigger or smaller? By how much?"
- The estimate goes on the card, and the team moves to the next item.
Reference story: "Add email field to signup form" = 3 points
New story: "Add OAuth login with Google"
- More complex (new library, token handling)
- More risk (third-party dependency)
→ Estimate: 8 points
Why Not Just Use Hours?
| Hours | Story Points |
|---|---|
| Anchored to clock time | Anchored to relative complexity |
| Pressures individuals | Encourages team discussion |
| Invites micro-management | Focuses on throughput |
| Varies wildly by person | Stabilizes over sprints |
Story points decouple effort from individual speed, which makes sprint planning more predictable over time.
Use Case
Use this guide when onboarding new team members to agile estimation, or when explaining to stakeholders why the team uses points instead of hours.