Epic(s)
Loosely specified, high-level placeholders for functionality. They are big, not-yet-refined user stories kept in the prioritized product backlog and will be split into smaller, detailed stories later.
Key Points
- Captured early in the project when details are still evolving.
- Represent large chunks of value that are too big for a single iteration.
- Stored and ordered in the prioritized product backlog, then refined and split over time.
- Useful for roadmap planning and coarse estimates until acceptance criteria are elaborated.
Example
In a mobile app project, the team adds an epic called "User account and authentication." Early on, it is a broad placeholder. During backlog refinement, it is broken down into stories like "User registration," "Email verification," "Login with password," and "Reset password," each with clear acceptance criteria for upcoming sprints.
PMP Example Question
During initial backlog creation, the product owner records a large, loosely defined item summarizing end-to-end checkout that will later be divided into multiple user stories. What is this item called?
- Epic
- Task
- Increment
- Definition of Done
Correct Answer: A — Epic
Explanation: An epic is a large, unrefined user story kept in the prioritized product backlog that is intended to be split into smaller stories as details emerge.
