Epic
Definition
An epic is a large body of work in agile product development that represents a significant feature or capability — too large to complete in a single sprint — which is broken down into multiple user stories that are planned and delivered incrementally.
Epics sit one level above user stories in the agile hierarchy. If a user story is a single conversation, an epic is a chapter. If a user story is a sprint of work, an epic is a quarter of work.
The term "epic" comes from Jira's hierarchy but is now used broadly across agile teams regardless of tooling. The Scrum Guide doesn't define epics — they're a practical addition most teams adopt to manage work at different levels of granularity.
When something becomes an epic: A feature is an epic when it's too large to be planned or estimated as a single story, or when it represents a meaningful product capability rather than a discrete user interaction. "User authentication" might be an epic. "Password reset via email" is a user story within that epic.
How epics get worked: The Product Owner keeps epics at the higher levels of the product backlog or in a roadmap view. As an epic approaches the next one to two sprints, the team breaks it down in refinement sessions — decomposing it into sprint-sized user stories that can be estimated, planned, and delivered.
Epic vs. theme vs. initiative: Different organizations use these terms with different hierarchies. A common stack: Initiative (business objective) > Theme (area of focus) > Epic (large feature) > User story (sprint-sized work). This varies widely — what one company calls an epic, another calls a theme.
Epic acceptance criteria: Like user stories, epics benefit from clear criteria that define when the epic is "done" — typically expressed as: all child stories are complete and the business outcome is achieved.
Examples
- Epic: 'User onboarding flow' breaks into seven user stories covering registration, email verification, profile setup, and first action
- Epic: 'Multi-workspace support' spans three sprints and 22 story points
- Product roadmap organizes twelve epics across four quarters, each containing ten to thirty user stories
- Epic flagged as a dependency — can't start 'Reporting dashboard' epic until 'Data pipeline' epic ships
- PO adds an epic titled 'Mobile offline mode' to the backlog; team breaks it down in two refinement sessions before it enters a sprint
Snap a epic. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.