What is Epic?
An epic is a large, coarse-grained unit of work that captures a significant feature, initiative, or outcome. It is too big to complete in one sprint and too broad to estimate precisely, so teams decompose epics into smaller user stories that can each be delivered incrementally.
Epics sit in the middle of the Agile work hierarchy: above them are themes or initiatives (strategic goals), and below them are user stories and tasks (executable work). This structure lets PMs talk about strategy and delivery at the right altitude — pitching an epic to leadership while the team works through its constituent stories.
For product managers, epics are useful for grouping related work, tracking progress toward a meaningful outcome, and communicating roadmaps without drowning stakeholders in story-level detail.
Examples
- An epic titled "Self-serve onboarding" contains stories for sign-up, email verification, a setup wizard, and a welcome tour.
- A roadmap shows three epics planned for the quarter, each expanding into 8–15 stories.
Where PMs use this
Related terms
User Story
A short, plain-language description of a feature told from the perspective of the user who wants it.
Product Backlog
A prioritized, continuously updated list of everything that might be built for a product.
Product Roadmap
A high-level, communicative plan of what a product team intends to work on and why, over time.
Prioritization
The discipline of deciding what to work on next by weighing value, effort, and strategic fit.