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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
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 that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice Epic
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.