In 30 seconds
- An epic is a big story, often spanning several sprints.
- It's broken into user stories before work starts.
- Epics group related work and track progress at a higher level.
Where epics fit
| Level | Example |
|---|---|
| Epic | Online checkout |
| User story | As a shopper, I want to pay by card |
| Task | Add card form validation |
In SAFe, epics are very large initiatives, and features sit between epics and stories.
Splitting an epic
- By workflow step: browse, add to cart, pay
- By user type: guest, registered
- By rule: domestic first, international later
- Happy path first, edge cases next
A story map makes splitting visual.
Common pitfalls
- Epics that never close because scope keeps growing
- Splitting by technical layer instead of user value
- Treating the epic as a fixed contract
Myth vs reality
Myth · Epics are a Scrum term.
Reality · Scrum doesn't define them; they're a common practice.
Myth · An epic must be finished before release.
Reality · Valuable slices can be released as they're done.
Myth · Epics need detailed specs.
Reality · Detail comes as stories are refined.
FAQ
How big is an epic?
Anything too big to finish in one sprint.
Who owns epics?
Usually the Product Owner or product manager.
When is an epic done?
When its goal is met, which may be before every story is built.