What description best represents Capabilities as defined in SAFe?

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