artifactDelivery & agility

Epic

A large, coherent body of product work that is too broad for one delivery interval and is progressively split into smaller items.

Download Markdown (.md)

01What it means

An epic is a planning artifact used by many agile teams to group a substantial outcome, capability, or body of work that must be decomposed into smaller stories or items. It is a common convention rather than a required Scrum element, and its exact position in a work hierarchy varies by organization and tool.[1][2]

A broad body of work progressively split for delivery The epic provides coherence while smaller slices produce usable value and evidence
Product outcome
Why this body of work matters
Epic
Coherent scope too broad for one interval
Value slices
Journey sliceRule sliceSegment sliceCapability slice
Small backlog items
Independently discussable and testable work
Usable increments
Integrated evidence toward the outcome

An epic is not a universal hierarchy level or a promise to deliver every child item; teams should split by observable outcome rather than technical layer alone.

02Why it matters

Epics let teams discuss meaningful work above story level, expose dependencies, and coordinate incremental delivery. They can bridge strategic initiatives and executable items without forcing detailed long-range specifications.

03When to use it

Use an epic when work has a coherent purpose but cannot responsibly fit in one short delivery interval. Skip the extra hierarchy for small work, and close or reshape epics when evidence changes the intended outcome.

04How it works

  1. State the customer or business purpose and boundaries of the epic.
  2. Identify evidence, risks, dependencies, and a useful success measure.
  3. Split the epic into independently valuable or learnable items.
  4. Order and deliver those items incrementally instead of waiting for the entire epic.
  5. Review evidence and stop, adapt, or complete the epic when its purpose is met.

05A practical example

Example

A marketplace creates an epic to reduce seller payout failures. It splits work into bank-detail validation, clearer remediation, operational alerts, and a migration experiment, then delivers and measures each part rather than treating the epic as one large release.

06Where it breaks

There is no universal size or hierarchy for an epic. It can become a disguised project container, remain open indefinitely, or encourage teams to measure completion instead of outcomes. Tool-specific definitions do not transfer cleanly between organizations.

Common mistakes

  • Treating an epic as a single oversized user story.
  • Waiting for every child item before releasing any value.
  • Using tool hierarchy as if it were a product strategy.
  • Keeping an epic alive after evidence invalidates its purpose.

07Sources

  1. Agile Epics: Definition, Examples, and TemplatesAtlassian · Professional practice guideAgile Epics: Definition, Examples, and Templates
  2. Epics, Stories, and InitiativesAtlassian · Professional practice guideEpics, Stories, and Initiatives
View saved topics

Start typing to search titles, definitions, categories, and frameworks.