liveBook · Manning

Epic

As explained in BDD in Action, Second Edition

An epic is a high-level software or business deliverable representing a broad capability needed to address a business problem or achieve a goal.

An epic is a high-level deliverable that represents a capability needed to address a business problem or achieve a measurable goal. Teams build an Epic Landscape by connecting business problems, goals, impacts, and deliverables, creating a breadth-first view of the capabilities worth pursuing. section 4.4.4

Use epics to keep delivery conversations focused on business value rather than terminology:

  • Start with pain points and convert them into tangible, measurable goals. section 4.4.4
  • Trace goals through actors, impacts, and deliverables; treat the resulting high-level deliverables as candidate epics. section 4.4.4
  • Keep only the most valuable deliverables when many possible capabilities compete for attention. section 4.4.4
  • Organize higher-level requirements into manageable sizes so stakeholders can understand them, validate assumptions, and provide feedback. section 5.2

From an acquisition problem to an epic landscape

A team notices that too few business travelers visit its site. It turns the pain point into a measurable goal: increase visits from business travelers by 300 percent. The team then explores the actions and deliverables that could support that goal, retaining the most valuable candidates as high-level epics rather than keeping every possible idea. section 4.4.4

Figure 4.18 A completed Pirate Canvas shows an Epic Landscape, high-level deliverables in the context of the bottlenecks they aim to eliminate.

Use the completed Pirate Canvas to see how an Epic Landscape places high-level deliverables in the context of the bottlenecks they aim to eliminate. section 4.4.4

How BDD in Action, Second Edition covers it

How deep it goes
Traces epics from pain points through goals, impacts, and deliverables, then stops at high-level prioritization rather than implementation detail.
Examples
Uses business-traveler acquisition, a 300-percent visit-increase goal, and a completed Pirate Canvas.
What it assumes
Assumes a business problem and goal, while teaching how to connect them to actors, impacts, deliverables, and manageable requirements.
What you can do after
Apply it to prioritize valuable deliverables and organize requirements for stakeholder validation and regular feedback.
How it connects
Connects epics with business goals, Pirate Canvas, Impact Mapping, capabilities, features, and User Stories.

Also explained in

Compare how 2 books explain epic →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of BDD in Action, Second Edition. The section links point to the parts of the book it draws on.