What is an epic?
An epic is a large body of work that spans multiple sprints. It's broken down into smaller user stories that can each be finished within a single sprint. Think of an epic as a chapter; user stories are paragraphs.
Examples of epics
- "Replace the legacy billing system" (could span 6+ sprints)
- "Build the mobile onboarding flow" (3-5 sprints)
- "Add SAML SSO support" (2-3 sprints)
Epic vs user story vs theme
- Theme — biggest. A strategic direction (e.g. "Self-serve")
- Epic — multi-sprint chunk under a theme
- User story — single-sprint, single-team-member-can-pull-it work
- Task — sub-piece of a user story; engineering breakdown
How to size an epic
Most teams don't story-point epics directly. Instead, they break the epic into stories during refinement, point the stories, and the epic's size emerges as the sum.
If you must size epics for high-level forecasting, use t-shirt sizes (S/M/L/XL) — false precision at the epic level is worse than no precision.
Common epic mistakes
- Never breaking down — an epic that lives in the backlog for months without sub-stories is a wishlist item, not work.
- Pointing the epic — defeats the point. Point the stories.
- Treating "epic" like a tag — it's a structural thing. Don't slap "epic" on any big-feeling ticket.