Epic
What is an Epic?
An epic is a large piece of work that spans several sprints and is split into user stories or tasks that together deliver one outcome. It sits between initiatives or themes and individual stories in most agile work hierarchies.
Updated November 2026 · 3 min read
An epic is a large body of work that is too big to finish in a single sprint and is therefore broken down into smaller user stories or tasks. It describes a meaningful outcome, such as "self-serve billing for team accounts," and groups the stories that together deliver it. Epics give teams and stakeholders a way to plan and track work at a level above individual tickets, without losing the link to the detailed backlog.
The term comes from agile practice, where an epic was originally described as a user story too large to estimate or complete in one iteration. Work-tracking tools such as Jira and Azure Boards later made epics a standard level in their work hierarchies, which is why most product teams now use the word.
Epic vs. user story vs. theme or initiative
Teams use these terms at different levels of a hierarchy. Exact names vary by tool and framework, but a common structure looks like this:
| Level | Size | Example |
|---|---|---|
| Theme or initiative | Quarters; spans several epics or teams | Expand into the mid-market |
| Epic | Several sprints; one team or a few | Self-serve billing for team accounts |
| User story | A few days; fits in one sprint | As an admin, I can update the company card on file |
| Task or subtask | Hours to a day | Add card validation to the billing API |
In the Scaled Agile Framework, "epic" means something bigger: a significant portfolio-level initiative that usually requires a lean business case and spans multiple release trains. Clarify which meaning is in use when working across organizations.
What a good epic contains
- A clear outcome. The user or business problem the epic solves, not a list of features.
- Success measures. How the team will know the epic worked, such as an adoption rate or a reduction in support tickets.
- Scope boundaries. What is in and, just as important, what is out.
- Acceptance criteria. High-level conditions the finished epic must meet.
- Dependencies and risks. Other teams, systems or decisions the epic relies on.
- Child stories. The stories that deliver it, created and refined over time rather than all at once.
How to break down an epic
- Start with the outcome. Write the epic as a problem and a goal before listing any work.
- Map the user journey. Use user story mapping to lay out the steps a user takes and find the thinnest end-to-end slice.
- Split by value, not by layer. Prefer stories that each deliver something usable ("pay by card") over technical slices ("build database tables"). See story splitting for patterns.
- Estimate the first stories. Size the near-term stories in detail and leave later ones rough.
- Refine continuously. Add, split or drop stories as the team learns.
Epic example
Consider a hypothetical project-management SaaS company whose support team handles about 300 billing tickets a month from team accounts. The product team creates the epic "Self-serve billing for team accounts," with the goal of cutting those tickets by half. It splits the epic into seven stories, estimated at 5, 8, 3, 5, 8, 2 and 3 story points, a total of 34 points. With an average velocity of 20 points per sprint and other work to fit in, the team forecasts the epic over about two sprints (34 ÷ 20 = 1.7). After the first three stories ship, billing tickets fall to around 200 a month, and the team learns that invoice downloads, not card updates, drive most of the remaining requests. It adds a new story and drops a low-value one.
Common pitfalls
- Epics that never close. An epic used as a permanent bucket ("Improvements") cannot be tracked or finished. Give every epic an end state.
- Breaking down everything up front. Writing all stories at the start locks in assumptions the team has not tested.
- Splitting by component. Stories like "front end" and "back end" deliver nothing on their own and hide integration risk.
- No success measure. Without one, finishing the stories is mistaken for achieving the outcome.
Epics live in the product backlog and connect day-to-day work to higher-level agile themes. Estimating them usually relies on story points and the team's sprint velocity.
Frequently asked questions
What is the difference between an epic and a user story?
An epic spans several sprints and describes a larger outcome, such as self-serve billing for team accounts. A user story fits in one sprint, usually taking a few days, and delivers one piece of that outcome, such as letting an admin update the company card on file. An epic groups the stories that together deliver it.
How do you split an epic into user stories?
Write the epic as a problem and a goal first, then use user story mapping to lay out the user's steps and find the thinnest end-to-end slice. Split by value rather than by technical layer, so each story delivers something usable, such as paying by card. Estimate near-term stories in detail and leave later ones rough until they are closer.
What does epic mean in SAFe?
In the Scaled Agile Framework, an epic is bigger than in most teams' usage: a significant portfolio-level initiative that usually needs a lean business case and spans multiple release trains. In tools such as Jira and Azure Boards, an epic typically covers several sprints for one team or a few. Clarify which meaning is in use when working across organizations.
Related terms
User Story
A plain-language statement of what a user wants to do and why.
Scaled Agile Framework (SAFe)
A framework for running agile across many teams, programs and portfolios.
Agile Themes
Goal-based focus areas that sit above epics and stories.
Story Points
A relative measure of the size of work, used instead of hours.