SAFe-Agilist Practice Question: Building a Foundation with Mindset, Values and Principles
A Product Manager insists on finalizing all requirements before development begins to avoid rework. Which SAFe Lean-Agile Principle does this behavior violate?
⚠ Common exam trap
Candidates frequently justify upfront requirements as a way to 'prevent rework,' missing the fact that in complex systems, this approach actually increases the risk of building the wrong thing.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Principle 3: Assume variability; preserve options
This behavior violates Principle 3, 'Assume variability; preserve options.' By attempting to define all requirements upfront, the manager ignores the inherent uncertainty in complex systems. Instead, SAFe advocates for a set-based design approach that maintains multiple options for as long as possible. This principle is vital because it enables teams to make better-informed decisions based on empirical evidence rather than potentially flawed initial assumptions, ultimately reducing the risk of costly late-stage corrections.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Principle 1: Take an economic view
Why it's wrong here
This principle focuses on sequencing jobs for maximum benefit and understanding the cost of delay. While poor planning affects economics, the specific act of locking down requirements early primarily conflicts with the need to handle variability, which is the foundational focus of Principle 3 in the Scaled Agile Framework.
- ✗
Principle 2: Apply systems thinking
Why it's wrong here
Systems thinking encourages optimizing the whole rather than individual silos. While requirements management is part of the system, the specific practice of freezing specifications contradicts the flexibility required to adapt to change. Principle 3 is the more precise match for the avoidance of early commitment to specific product designs.
- ✓
Principle 3: Assume variability; preserve options
Why this is correct
Freezing requirements early reduces the ability to pivot when new information emerges. This principle dictates that teams should maintain a range of possibilities to account for uncertainty. By forcing a single path too early, the manager eliminates the flexibility necessary to adjust to market changes and technical discoveries during development.
- ✗
Principle 9: Decentralize decision-making
Why it's wrong here
Decentralization refers to shifting decision-making authority to those with the local context and expertise. While the Product Manager might be centralizing authority, the core violation here is the rejection of variability. Preserving options is a distinct conceptual requirement that overrides the general preference for decentralized organizational structure in this scenario.
About these practice questions
One of 315 original SAFe-Agilist practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.