You organization decided to thoroughly implement the SAFe Principle "Assume variability; preserve options." What is the optimum path for success?

Question

Options

• AAssume variability of scope and preserve options for the release date.
• BPreserve flexibility in system functionality and design, but have fixed Solution intent.
• CAssume variability of scope, but have fixed Solution Context.
• DPreserve flexibility in both system functionality and design.

• A
  5% (1)
• B
  18% (4)
• C
  9% (2)
• D
  68% (15)

Explanation

Option D is correct because the SAFe principle "Assume variability; preserve options" calls for maintaining flexibility across both system functionality and design - this is the essence of set-based design, where multiple options are kept alive until sufficient real-world data justifies narrowing them down. Option A is wrong because it conflates scope variability with release-date flexibility, which is unrelated to this principle. Option B fails because a fixed Solution Intent locks in requirements too early, directly violating the "preserve options" mandate - Solution Intent should remain fluid until late-cycle learnings justify commitment. Option C is wrong because a fixed Solution Context constrains how the solution fits its operating environment, again closing off options prematurely.

Memory tip: Think of the principle as "stay flexible on what you build (functionality) and how you build it (design)" - any answer that fixes something early is a trap.

No community discussion yet for this question.