SAFe-Agilist Practice Question: Building a Foundation with Mindset, Values and Principles
A SAFe Portfolio is struggling with long queues of work in progress. The Lean Portfolio Management group wants to apply the principle 'Limit work in process (WIP), reduce batch sizes, and manage queue lengths' to improve flow. Which action best aligns with this principle?
⚠ Common exam trap
The trap here is equating high utilization with good flow, when in fact limiting WIP and reducing batch sizes are what actually shorten queues and accelerate delivery.
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
✓
Set explicit WIP limits for teams and ARTs and make the work visible on their boards
The correct answer is setting explicit WIP limits and visualizing work, because this directly applies the principle of limiting WIP, reducing batch sizes, and managing queue lengths. It helps teams and ARTs see bottlenecks, reduce multitasking, and improve flow. The other options increase WIP or maximize utilization, which worsen queues and delay value delivery, contrary to the principle.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the number of features in each Program Increment to keep teams busy
Why it's wrong here
Increasing the number of features in each PI violates the principle of limiting WIP. More features create longer queues, increase context switching, and delay value delivery. The goal is to reduce batch sizes and manage queue lengths, not to overload the system. Keeping teams busy is a local optimization that harms overall flow and predictability, so this action is counterproductive.
- ✓
Set explicit WIP limits for teams and ARTs and make the work visible on their boards
Why this is correct
Setting explicit WIP limits and visualizing work directly implements the principle of limiting WIP and managing queue lengths. It helps teams and ARTs identify bottlenecks, reduce multitasking, and accelerate flow. In a SAFe Portfolio, making work visible on program boards and portfolio Kanbans allows leaders to see and manage queues. This action is a practical, proven way to apply the principle.
- ✗
Encourage each team to work on as many features as possible simultaneously
Why it's wrong here
Working on many features simultaneously increases WIP and batch sizes, which lengthens queues and delays feedback. The principle advocates reducing batch sizes and limiting concurrent work to improve flow. This option would worsen the portfolio's problem by creating more work in process. It contradicts the core intent of the principle, which is to optimize the whole system, not local activity.
- ✗
Allow teams to pull as much work as they can to maximize utilization
Why it's wrong here
Maximizing utilization by pulling unlimited work is the opposite of limiting WIP. High utilization leads to congestion, longer cycle times, and lower throughput due to queueing theory effects. The principle explicitly warns against overloading the system. This option reflects a common misconception that keeping everyone 100% busy improves delivery, which it does not in complex development environments.
About these practice questions
This SAFe-Agilist question is part of Courseiva's 315-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.