(Select 3) Enablers can be used for any activities that are necessary to support upcoming business features, but generally they fall in one of 3 categories:

Question

Options

• AArchitecture
• BTeam tasks
• CExploration
• DVertical slice of a feature
• EInfrastructure

• A
  91% (43)
• B
  6% (3)
• D
  2% (1)

Explanation

In SAFe (Scaled Agile Framework), Enablers support the Architectural Runway - the technical foundation needed before user-facing features can be built. The three official Enabler categories are Architecture (defining system structure and design decisions), Infrastructure (build/test/deployment pipelines and environments), and Exploration (spikes, research, and prototyping to reduce uncertainty).

B (Team tasks) is wrong because routine team activities are not a formal Enabler category - they belong in iteration planning as standard backlog items. D (Vertical slice of a feature) is wrong because vertical slices are a story-writing technique for delivering user-facing functionality end-to-end; they represent business value, which is the opposite of what Enablers do (they are not user-facing).

Memory tip: Use the acronym AIE - Architecture, Infrastructure, Exploration - and think of Enablers as the "invisible scaffolding" that lets business features stand up. If the work touches a user, it's a Feature/Story; if it touches the foundation beneath it, it's an Enabler in one of these three buckets.

No community discussion yet for this question.