Epic
An epic is a large body of work, often written as a big user story, that is too large to complete in a single sprint and must be split into smaller stories before a team builds it. Epics group related stories under one shared outcome, which helps teams organize the backlog, plan work across several sprints and track progress toward a larger goal.
How Epics Work
Mike Cohn traces the term to the Extreme Programming teams that invented user stories, where an epic was simply a large user story. There is no exact size threshold. An item becomes an epic when it is too big for one team to finish in one iteration.
Epics play two roles. First, they act as placeholders. Early on, a team can write "customers can manage their subscription" as one epic and deliberately leave the detail for later. Second, they act as containers. As the epic approaches the top of the backlog, the team splits it into smaller user stories that can each be built, tested and delivered. In tools such as Jira, the epic remains as a parent item so progress across its child stories is visible.
Many teams use a layered hierarchy: initiatives or themes at the top, epics beneath them, then stories, then tasks. The exact names vary between companies and tools, so teams should agree on what each level means.
Good splitting keeps value intact. Instead of cutting an epic by technical layer, such as "build the database" and then "build the interface", teams usually slice it into thin pieces of end-to-end functionality. User story mapping is a common way to see an epic's stories along the user's journey and decide which slice to build first.
Why Epics Matter
Epics let a backlog hold large ideas without detailing them too early. That keeps planning lightweight: the team spends effort only on the epics it is about to start, and the rest stay as short descriptions until priorities settle.
They also connect strategy to delivery. A roadmap item such as "self-serve billing" becomes an epic, and the epic's stories become sprint work. Stakeholders can follow progress at the epic level without reading every story. For a deeper look at breaking epics down without losing scope or dependencies, see epic decomposition into dependency-aware tasks.
Epic Example
A team building a project management tool writes an epic: "As a team admin, I can manage billing myself so I don't need to contact support." Before starting, they split it into stories: view the current plan and next invoice, update the payment card, download past invoices, and change the plan with a prorated charge. They build the first two in one sprint because they cover the most frequent support requests, and leave plan changes for a later sprint.
Epic vs. Feature and Theme
Cohn notes that "feature" was not part of the original user story vocabulary and is used inconsistently. The most common meaning is a capability large enough for users to notice, which overlaps with epic in many teams. A theme is a collection of related stories grouped for convenience, like a label, rather than a single large piece of work to be split.