SAFE-SPC practice question 4 of 25

What description best represents Capabilities as defined in SAFe?

Answer options

A: Capabilities are simply a level of abstraction above Epics, exhibiting largely the same characteristics and practices.

B: Capability is a different name for Features, one that is preferred by some organizations.

C: Capabilities are simply a different kind of Epic, exhibiting largely the same characteristics and practices.

D: Capabilities are simply a level of abstraction above Features, exhibiting largely the same characteristics and practices. Correct answer

Correct Answer:

D. Capabilities are simply a level of abstraction above Features, exhibiting largely the same characteristics and practices.

Explanation

In SAFe 6.0, Capabilities are defined as "higher-level solution behaviors that typically span multiple ARTs." They are maintained in the Solution Train Backlog and are sized and split into Features for implementation by individual ARTs. The SAFe 6.0 guidance specifically states: “Capabilities are larger solution behaviors that often span multiple Agile Release Trains. They are typically sized to be delivered in a Planning Interval (PI) and are broken down into Features to facilitate implementation.” This distinguishes Capabilities from Epics and Features. Unlike Epics, which require Lean Business Cases and approval through Portfolio Kanban, Capabilities follow a breakdown path to Features for execution. Therefore, they are a level above Features, not a synonym for Epics or Features.
Reference: SAFe 6.0 Website: Capabilities SAFe Practice Consultant SPC (6.0) Training Guide — "Building Solutions with Agile Product Delivery" Module Terminology Update: "Solution Backlog" → "Solution Train Backlog" confirms the hierarchical location of Capabilities

Keep practicing

Take the free SAFE-SPC practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test