How can a technical exploration Enabler be demonstrated?

Question

Options

• AShow the acceptance tests written for the exploration
• BShow the knowledge gained by the exploration
• CDemonstrate working systems in the production environment
• DExploration Enablers do not need to be demonstrated

• B
  89% (17)
• C
  5% (1)
• D
  5% (1)

Explanation

Option B is correct because a technical exploration Enabler's purpose is to generate knowledge - its "deliverable" is what the team learned (e.g., a spike result, a research finding, a feasibility conclusion). The output is intellectual, not functional, so demonstrating it means sharing that knowledge with stakeholders.

• A is wrong because acceptance tests define done for user-facing functionality; exploration Enablers produce learning outcomes, not testable acceptance criteria in the traditional sense.
• C is wrong because exploration Enablers are not meant to deliver production-ready working software - that confuses them with Architecture or Infrastructure Enablers that build out the technical runway.
• D is wrong because all work in SAFe must be demonstrable to provide transparency and validate value - "nothing needs to be shown" violates core SAFe principles of visibility and continuous inspection.

Memory tip: Think of exploration Enablers as "spike stories" - the team goes spelunking into the unknown and comes back with a map (knowledge), not a product. What did you learn? is the demo question.

No community discussion yet for this question.