What description best represents Capabilities as defined in SAFe?

Question

Options

• ACapabilities are simply a level of abstraction above Epics, exhibiting largely the same
• BCapability is a different name for Features, one that is preferred by some organizations.
• CCapabilities are simply a different kind of Epic, exhibiting largely the same characteristics and
• DCapabilities are simply a level or abstraction above Features, exhibiting largely the same

• A
  3% (1)
• B
  3% (1)
• C
  8% (3)
• D
  87% (34)

Explanation

Option D is correct because in SAFe, Capabilities occupy the layer directly above Features in the solution backlog hierarchy. They describe larger cross-ART (Agile Release Train) solution behaviors that are too large to be delivered by a single ART, and - like Features - they are sized to be delivered within a Program Increment. They share the same structural characteristics as Features (written with a benefit hypothesis, using WSJF for prioritization, etc.), just at a higher level of abstraction.

Why the distractors are wrong:

• A is wrong because Capabilities are above Features, not above Epics. Epics are actually above Capabilities in the hierarchy.
• B is wrong because Capabilities and Features are distinct constructs at different levels - Capabilities are not simply an alias for Features.
• C is wrong because Capabilities are not a kind of Epic. Epics sit at the Portfolio level and are decomposed into Capabilities (or Features), making them the parent, not a sibling.

Memory tip: Think of the SAFe hierarchy as Epic → Capability → Feature → Story. Capabilities are the "middle child" between Epics and Features - they look and behave just like Features, only one rung higher on the ladder. If you remember "Capability is a Feature-shaped thing that lives above Features," you'll nail this question.

No community discussion yet for this question.