Epic

Why

An epic[1] is a means to describe a larger user goal or business goal, that will be further developed in multiple user stories. Linking the user stories to the epic, gives insight in the context and progress of the epic. Epics are used to make a high level planning.

Prepare for success

  • Any epic on the Product Backlog should be in line with the product vision, and contribute to the goal of the project.
  • Postpone the co-preparation for an epic to the latest acceptable moment, but not later. Until that moment, put the epic on the backlog without too much detail.

How

An epic is similar to a user story[2], but too large to build in one go. An epic is big in scope and may have assumptions and dependencies. As long as its position on the product backlog[3] is low, and you don’t need a detailed estimate for it, it’s perfectly fine to just leave it on the backlog without too much detail. Once it becomes more important, the Product Owner[4] should organize a co-preparation[5] session for breaking down the epic into User Stories with the key stakeholders and the development team. The result will be a number of prioritized user stories and a release planning. On the product backlog, the relationship between an epic and its user stories is visible, which makes it possible to track its progress. A release can consist of multiple epics.

Definition of Done[6]

The epic is done when all related user stories are done.

Real Life Example

For the development of an app to book a shipment for parcels and packages, the idea came up to improve the usability for the end-user by storing previously used names and addresses, suggesting these while typing, and providing other ways to easily import and select contact information. This entire set of ideas and wishes was identified as an epic, called the “online address book”. Eventually 11 different user stories were defined and developed that together formed this epic.

Notes

  1. Epic - An epic is a means to describe a larger user goal or business goal, that will be further developed in multiple user stories. Linking the user stories to the epic, gives insight in the context and progress of the epic. Epics are used to make a high level planning.
  2. User Story - A user story describes a functional goal from the perspective of an end-user. Who wants to do what with the product, and why?
  3. Product Backlog - An ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.
  4. Product Owner - The Product Owner plays a crucial role in the development of a great software product. He or she is responsilble for maintaining the Product Backlog.
  5. Co-preparation - The Product Owner (PO) meets the Team with their technical skills to define the best solution for the business case challenges. Best ideas arise in offsite meeting(s) in a relaxed and inspiring atmosphere. Various techniques are used to explore possibilities and to discover business values and ways to mitigate risks.
  6. Definition of Done - A shared understanding of expectations that the Increment must live up to in order to be releasable into production. Managed by the Development Team.