Story Points Explained: The No-Drama Guide to Agile Estimation

Few topics in agile generate more debate than story points.

Let's cut through the noise with practical guidance.

What Story Points Measure

Story points are a relative measure of effort combining:

1. Complexity: How hard is this?
2. Uncertainty: How much do we know?
3. Effort: How much work is involved?

What They Are NOT

• Not hours or days
• Not a commitment
• Not comparable across teams
• Not a performance metric

The Fibonacci Scale

| Points | Meaning | |--------|---------| | 1 | Trivial—done this before | | 2 | Small—straightforward | | 3 | Medium—typical story | | 5 | Large—significant work | | 8 | Very large—consider splitting | | 13+ | Too big—must split |

Planning Poker

1. Product owner presents story
2. Clarifying questions (5 min max)
3. Silent estimation
4. Simultaneous reveal
5. Discuss extremes
6. Re-estimate if needed

Reference Stories

Maintain 3-5 completed stories as benchmarks:

| Size | Reference | |------|-----------| | 2 | "Add field to form" | | 5 | "Password reset flow" | | 8 | "CSV export with filtering" |

Common Mistakes

1. Equating points to time - They measure relative effort
2. Comparing teams - Each team's points are unique
3. Individual performance - Points aren't productivity
4. Re-estimating after completion - Don't change history

When to Skip Points

No Estimates: Break stories to similar sizes, track throughput. T-Shirt Sizing: Use S/M/L/XL. Bucket Sizing: Quickly sort into buckets.

The Bottom Line

Story points help teams have conversations about complexity, plan sprints, identify stories to split, and track capacity trends.

---

Want easier estimation? Scrummy includes built-in planning poker and automatic velocity tracking.