How to Estimate Large Epics: Breaking Down 13+ Point Stories
When a story is estimated at 13, 21, or "too big to estimate," it's not ready for sprint planning. Epics require decomposition before accurate estimation. Here's how to break down massive features into estimable stories.
Signs a Story Is Too Large
- Votes cluster at 13+ or include "?" / "coffee cup" (too big)
- Team says "depends on..." more than 3 times
- Acceptance criteria list has 10+ bullet points
- Story spans multiple user personas
Epic Decomposition Techniques
1. Slice by User Journey Steps
Epic: "Build user onboarding flow"
Stories:
- Email verification
- Profile setup wizard
- Tutorial walkthrough
- First-time user dashboard
2. Slice by Technical Layers
Epic: "Add multi-currency support"
Stories:
- Database schema for currency codes
- Exchange rate API integration
- UI currency selector
- Historical transaction conversion
3. Spike First, Then Estimate
For truly unknown work, create a "spike" story:
- Timebox: 4-8 hours of research
- Output: Written findings + decomposed stories
- Then estimate the decomposed stories
Spikes convert unknown complexity into estimable work.