Epic: The Agile Placeholder for Big Ideas

THE MENTAL MODEL: An Epic is a large user story that is too broad or complex to be completed in a single sprint. Think of it as a high-level container or a chapter title for a big feature, like "User Authentication" or "Reporting Dashboard." It doesn't contain implementation details itself; it's a placeholder to be broken down later.

HOW IT WORKS: An Epic is placed on the product backlog to represent a significant piece of value. As it moves closer to implementation, the product owner and team break it down into smaller, more manageable user stories. Each of these smaller stories can be independently estimated, prioritized, and completed within a single sprint. The Epic is considered "done" only when all its child stories are completed.

WHEN TO USE IT: Use Epics to capture large-scale ideas and features early on without getting bogged down in details. They are perfect for organizing the backlog and communicating the product roadmap at a high level. Examples include "Build a new checkout process," "Integrate with a third-party payment provider," or "Overhaul user profile settings."

WHEN NOT TO USE IT: Avoid creating Epics for tasks that are small enough to be a single user story and can be completed in one sprint. For example, "Change the color of the login button" is a user story, not an Epic. Using Epics for small tasks adds unnecessary administrative overhead.

ONE CANONICAL EXAMPLE: A team wants to build a "User Profile" feature. This is too big for one sprint. They create an Epic called "User Profile Management." Over time, they break this Epic down into smaller user stories like: "As a user, I can upload a profile picture," "As a user, I can edit my email address," and "As a user, I can set my notification preferences." These smaller stories are then tackled in subsequent sprints.