SAFe-Agilist Product Development Flow Practice Question
A Scrum Master notices that a team frequently starts new stories before finishing current ones, leading to many stories in progress and few completed. Which SAFe principle should the Scrum Master emphasize to improve flow?
⚠ Common exam trap
The trap here is selecting a general principle like system thinking or cadence, but the specific issue of too many stories in progress is best solved by limiting WIP and reducing batch sizes.
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
✓
Limit work in process and reduce batch sizes
Limiting work in process and reducing batch sizes is the SAFe flow principle that directly addresses the team's behavior of starting too many stories. By setting WIP limits, the team focuses on completing work before pulling new items, which improves flow, reduces lead time, and increases predictability. This principle is fundamental to achieving flow in product development.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply cadence, synchronize with cross-domain planning
Why it's wrong here
Cadence and synchronization are important for alignment, but they do not directly address the issue of too many stories in progress. The team's problem is excessive work in process, which requires a focus on limiting WIP and finishing work before starting new work, not on planning cadence.
- ✗
Implement system thinking
Why it's wrong here
System thinking helps understand the whole value stream but does not provide the specific practice of limiting WIP. The team's behavior of starting too many stories requires a direct flow control mechanism, such as WIP limits, rather than a broader mindset shift.
- ✗
Decentralize decision-making
Why it's wrong here
Decentralizing decision-making empowers teams but does not solve the problem of too many stories in progress. The issue is about flow control, not decision authority. While decentralization is valuable, it is not the principle that directly improves flow in this scenario.
- ✓
Limit work in process and reduce batch sizes
Why this is correct
Limiting work in process and reducing batch sizes is a SAFe flow principle that directly addresses the team's habit of starting too many stories. By setting WIP limits, the team finishes work before pulling new items, which improves flow, reduces lead time, and increases throughput. This is the core principle to apply here.
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.