Epic
An Epic is a large user story or body of work that is too big to complete in a single iteration and must be broken down into smaller, more manageable user stories.
Know it well enough for the exam? Questions on Epic are scenario-based, not definitional.
Practice it freeExplanation
Epics represent significant functionality or business objectives that span multiple sprints. They serve as containers for related user stories and provide a high-level view of the work needed to deliver a large feature or capability. As the team approaches an epic, it is progressively elaborated into smaller user stories that can fit within a single sprint.
Epics are useful for roadmap planning and communication with stakeholders. They provide enough detail to understand the scope and value of a feature without requiring the granularity needed for sprint-level planning. In many tools, epics sit at the top of a hierarchy: Epic, Feature, User Story, Task.
In SAFe, epics have a formal lifecycle with an epic hypothesis statement and a lean business case. They go through a Kanban system at the portfolio level and are approved based on WSJF prioritization before being broken down into features and stories for teams to implement.
Key Points
- •Large body of work that spans multiple iterations
- •Broken down into smaller user stories for sprint-level planning
- •Useful for roadmap planning and stakeholder communication
- •In SAFe, epics have a formal lifecycle with lean business cases
Exam Tip
An epic is too large for a single sprint. If a question describes a large requirement, the first step is to decompose it into smaller stories.
Frequently Asked Questions
Related Topics
User Stories
A user story is a short, simple description of a feature or requirement written from the perspective of the end user, following the format: "As a [role], I want [goal], so that [benefit]."
Feature (Agile)
A Feature in agile is a service or functionality that fulfills a stakeholder need, sized to be deliverable within a single iteration or Program Increment, and typically composed of multiple user stories.
Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Product Backlog
The product backlog is an ordered list of everything that is known to be needed in the product, serving as the single source of requirements and the primary artifact for managing scope in agile projects.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Part of
Agile & Hybrid
Practice Epic
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.