Enabler Features can contribute to the Architectural Runway and realize system Nonfunctional Requirements at the same time.

Question

Options

• ATrue
• BFalse

• A
  87% (34)
• B
  13% (5)

Explanation

Option A is correct because Enabler Features in SAFe are specifically designed to extend the Architectural Runway - building the technical foundation needed for future work - while simultaneously satisfying Nonfunctional Requirements (NFRs) like performance, security, or scalability. These two goals are not mutually exclusive; a single Enabler Feature can do both at once, for example, implementing a distributed caching layer that both extends system infrastructure (Architectural Runway) and meets a response-time NFR.

Option B is wrong because it incorrectly assumes these two purposes conflict or cannot coexist - SAFe explicitly recognizes that Enablers serve multiple technical objectives simultaneously.

Memory tip: Think of Enabler Features as "dual-purpose technical investments" - they build the runway (infrastructure for the future) while also meeting quality targets (NFRs). If a feature is technical and foundational, it can tick both boxes at once.

No community discussion yet for this question.