What is true about Epic implementation?

Question

Options

• AOnce pulled into implementation, the Epic needs to be finished.
• BA budget reserve is established that can be used to fund Epics.
• CAgile Release Trains are empowered to decide whether or not they proceed with a Portfolio Epic.
• DRe-prioritization happens at every PI boundary, and the rest of the Epic can be postponed or

• A
  3% (1)
• B
  18% (6)
• C
  9% (3)
• D
  71% (24)

Explanation

Option D reflects a core SAFe principle: Epics are not treated as all-or-nothing commitments. At each Program Increment (PI) boundary, leadership re-evaluates the portfolio backlog, and any in-flight Epic can be reprioritized, postponed, or cancelled based on new information, changing business conditions, or shifting priorities - this is intentional, not a failure.

Why the distractors are wrong:

• A is incorrect because committing to finish an Epic regardless of circumstances contradicts agile principles; stopping work when value is no longer justified is a feature, not a flaw.
• B is incorrect in its framing - SAFe uses Lean-Agile Budgeting allocated to Value Streams/ARTs, not a dedicated "budget reserve" earmarked specifically for Epics.
• C is incorrect because Portfolio Epics require approval from Lean Portfolio Management (LPM), not the ART alone; ARTs have autonomy over local Features, not Portfolio-level investments.

Memory tip: Think of PI boundaries as "off-ramps" - every time a PI ends, the organization gets an off-ramp to exit the Epic highway if the destination no longer makes sense. Epics are investments re-evaluated at each checkpoint, not contracts enforced to completion.

No community discussion yet for this question.