Epics and Capabilities
Turn portfolio goals into sized, fundable Epics and Capabilities before a single Feature hits the backlog.
Epics→
Capabilities→
Features
01 / Summary
What Is the Epics and Capabilities Workshop?
This workshop is the bridge between portfolio strategy and program delivery. It takes a portfolio’s approved Goals and works them down into Epics, then into Capabilities, so the Feature Breakdown Workshop has clean, sized, and funded starting points instead of vague strategic language.
In the Scaled Agile Framework, an Epic is defined as a significant solution development initiative that requires a Lean business case and Portfolio Leadership approval before funding. A Capability sits between an Epic and a Feature: it represents large solution functionality whose implementation often spans multiple Agile Release Trains and is sized to be delivered within a Program Increment. Features are sized to be delivered by a single Agile Release Train within a PI.
Run this workshop any time the connection between what leadership wants and what teams are building has gone fuzzy, or before it’s allowed to.
02 / Application
When to Use the Epics and Capabilities Workshop?
Run this workshop any time the connection between what leadership wants (Goals) and what teams are building (Features) has gone fuzzy, or before it’s allowed to.
New ART or Value Stream
Launching a new Agile Release Train or Value Stream and you need a real starting backlog, not a wish list.
Goals Shifted
Portfolio Goals shifted after a strategy or budget review and existing Epics need to be re-scoped or retired.
Large Solution, No Capabilities
A Large Solution spans multiple ARTs and Capabilities haven’t been defined, so work is being requested directly as Features.
Feature Breakdown Keeps Stalling
The Feature Breakdown Workshop keeps stalling because the Epics or Capabilities feeding it are too vague to split.
Prerequisites
Approved Goals
Strategic Themes or portfolio Goals, ideally stated as OKRs, that Portfolio Leadership has already signed off on.
Draft Epic Hypotheses
At least a draft hypothesis for each candidate initiative, with a named Epic Owner accountable for it.
Roles and Responsibilities
Keep the room limited to people who can actually approve, size, or own the work in front of them. This session moves slowly with observers in it.
Scheduling and Timing
- Plan a half-day for a single Agile Release Train; a full day for a multi-ART Solution Train with several Capabilities to work through.
- Best scheduled after Strategic Theme or OKR approval and before Feature Breakdown or PI Planning prep begins.
- Revisit quarterly, or immediately whenever Goals change materially.
- Build in one to two weeks of pre-work so Epic Owners can arrive with a real hypothesis, not a blank page.
03 / Preparation
Preparing for the Workshop
Preparation is where this workshop is won or lost. If Epic Owners show up without a drafted hypothesis, the session turns into a brainstorm instead of a decomposition exercise, and nothing gets sized.
- Confirm and distribute the current Strategic Themes or portfolio Goals and OKRs to every invitee.
- Identify Epic Owners for each candidate initiative and confirm each has a draft hypothesis statement (problem, proposed MVP, expected outcome).
- Reserve and set up the Portfolio Kanban board (physical or Miro), with Funnel, Review, and Analysis columns visible.
- Download and prepare the Canvas Template and the Facilitator’s Presentation for the session.
-
Send scheduling communication with agenda and pre-read materials
Email Template
Subject: [Portfolio/Value Stream Name] — Epics and Capabilities Workshop — Prep and Pre-ReadHi team,
We’re holding an Epics and Capabilities Workshop on [date] to connect our approved [quarter/year] Goals to a sized set of Epics and Capabilities.
Please review the attached Strategic Themes/OKRs before the session. If you’re an Epic Owner, bring a one-page hypothesis (problem, proposed MVP, and expected business outcome) for your initiative.
We’ll spend the session decomposing approved Epics into Capabilities and placing them on the Portfolio Kanban.
Location/Miro link: [link]
Duration: [half day / full day]Calendar Invite Copy
Subject: Epics and Capabilities WorkshopAgenda: Goals review, Epic hypotheses, Capability decomposition, WSJF/business-case check, Portfolio Kanban placement, hand-off to Feature Breakdown.
Room/Miro: [link]
Please bring your draft Epic hypothesis if you’re an Epic Owner.
04 / Facilitation
Facilitating the Session
Facilitation moves in one direction: from the Goals the portfolio has already funded, down to Capabilities a Program team can actually plan around. Resist the urge to let the room re-debate strategy; that conversation should already be settled by the time this workshop starts.
Facilitation Agenda
-
Open with the Goals
- Review the Strategic Themes and OKRs the portfolio is funding this cycle, so everyone in the room is working from the same strategic intent.
-
Walk the Hierarchy
- Goals to Epics to Capabilities to Features, using one real, already-familiar example so the abstraction lands before asking the room to do it themselves.
-
Surface and Hypothesize Epics
- Each Epic Owner presents their one-page hypothesis: the problem, the proposed MVP, and the expected business outcome.
-
Decompose Epics into Capabilities
- Group by ART or Solution Train and size roughly using T-shirt sizing or relative estimation.
-
Stress-Test Against LPM Criteria
- Confirm each Epic has a Lean business case, an MVP, and a rough WSJF score before it moves forward.
-
Sequence on the Portfolio Kanban
- Move approved items from Funnel into Review/Analysis, and park anything not ready back in Funnel.
-
Confirm Hand-Off to Feature Breakdown
- Agree on what “ready for feature splitting” looks like for each approved Capability.
Common Anti-Patterns to Avoid
- Writing Epics that are really just oversized Features in disguise — if it fits in one ART’s PI, it’s not an Epic.
- Skipping the business case and MVP definition because “everyone already agrees this is important.”
- Letting Capabilities balloon instead of splitting them to fit within a Program Increment.
- Approving an Epic without a named, accountable Epic Owner in the room.
05 / Follow-Up
After the Workshop
What happens in the two weeks after this workshop determines whether the Epics and Capabilities you just approved actually turn into scheduled work, or quietly stall. Follow-up should be fast, specific, and land in the hands of the people now accountable for each item.
Expected Outputs
Share these outputs within 48 hours, distributed to every Epic Owner, Product/Solution Management, and Portfolio Leadership, not just archived in a shared folder no one opens.
Follow-Up Communication Template
Thanks for a productive session.
Attached are the approved Epic hypotheses, the Capability list by ART, and the updated Portfolio Kanban board.
Epic Owners: please finalize your Lean business case within [1-2 weeks].
Product/Solution Management: please schedule Feature Breakdown Workshops for each approved Capability.
Questions or changes to scope should come to [name] before [date].
Ongoing Next Steps
- Epic Owners finalize Lean business cases within one to two weeks.
- Product/Solution Management schedules Feature Breakdown Workshops for each approved Capability.
- RTE/STE updates the Portfolio Kanban status weekly until PI Planning.
- Revisit any unapproved or parked Epics at the next portfolio sync.
- Archive session artifacts (hypotheses, Kanban snapshot, business cases) in the shared workspace.
06 / References and Resources
References and Resources
- Scaled Agile Framework (SAFe): Epic
- Scaled Agile Framework (SAFe): Features and Capabilities
- Scaled Agile Framework (SAFe): Strategic Themes
Complimentary Workshops
Story Pointing Workshop
Give the team a shared, repeatable way to size backlog items before they commit to a sprint.
Ready to facilitate?
Download templates and tools to run your own Epics and Capabilities session.