SAFe-Agilist Practice Question: Building a Foundation with Mindset, Values and Principles
A Product Manager insists on finalizing all requirements before development begins to ensure predictability. Which SAFe Lean-Agile Principle does this behavior violate?
⚠ Common exam trap
Candidates often mistakenly believe that finalizing requirements is a 'good' project management practice, failing to see how it violates the SAFe principle of preserving options for flexibility.
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 finalize requirements prematurely, the Product Manager restricts the ability to pivot based on learning. SAFe emphasizes maintaining multiple requirements and design options for a longer period during the development cycle. Adhering to this principle allows teams to discover the optimal solution through empirical evidence rather than relying on flawed, early-stage assumptions that often lead to poor outcomes.
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
Economic view focuses on sequencing jobs and managing the cost of delay. While early finalization might seem cost-effective, the primary violation here is about stifling exploration and flexibility, which is the hallmark of managing variability rather than just focusing on the financial aspects of individual project delivery.
- ✗
Principle 2: Apply systems thinking
Why it's wrong here
Systems thinking relates to understanding the interconnected nature of the value stream and optimizing the whole rather than parts. While rigid requirements hinder flow, the specific act of locking down scope prematurely is a direct contradiction to the need for keeping options open during development.
- ✓
Principle 3: Assume variability; preserve options
Why this is correct
Preserving options means keeping design and requirement alternatives open as long as possible. By forcing a final decision early, the Product Manager destroys the agility needed to react to new information. This prevents the team from utilizing a set-based design approach, which is vital for complex system development.
- ✗
Principle 9: Decentralize decision-making
Why it's wrong here
Decentralized decision-making empowers those with the most context to make choices. While the Product Manager might be centralizing control, the core issue is the refusal to accept that requirements evolve during the process, making Principle 3 the more direct violation regarding the handling of uncertainty.
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.