SAFe-Agilist Product Development Flow Practice Question
Which TWO of the following are considered 'Flow Accelerators' in SAFe? (Select exactly two)
⚠ Common exam trap
Test-takers often select general Agile practices like refactoring or retrospectives, missing the specific 'Flow Accelerator' practices of Kanban visualization and strict WIP limits.
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
✓
Visualize work through Kanban boards to identify bottlenecks.
Flow accelerators are techniques that help the organization identify and remove barriers to value delivery. By focusing on visualizing work and limiting WIP, teams can better understand their bottlenecks. These practices, combined with techniques like small batch sizes and cadence, ensure that the system remains responsive and that the value stream remains efficient throughout the planning and execution phases of the train.
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 batch sizes to reduce the frequency of planning sessions.
Why it's wrong here
Large batch sizes increase risk and delay feedback. They create larger buffers of inventory that hide defects and cause massive delays at the end of a cycle. SAFe promotes smaller batches to reduce risk, improve quality, and ensure that value is delivered more frequently to the end customer.
- ✓
Visualize work through Kanban boards to identify bottlenecks.
Why this is correct
Visualizing work is a foundational practice for managing flow. By making the status of items transparent, teams can identify where work is piling up or stalled. This transparency allows for collaborative problem-solving to address constraints, effectively accelerating the movement of work through the various stages of the development pipeline.
- ✓
Implement strict WIP limits to improve throughput.
Why this is correct
WIP limits are essential to prevent system overload and context switching. By restricting the number of active items, teams can focus their attention on finishing work, which increases throughput. This practice is a primary driver for improving flow by ensuring that the system capacity is utilized effectively and efficiently.
- ✗
Centralize all decision-making to maintain consistent quality.
Why it's wrong here
Centralized decision-making is a primary inhibitor of flow, not an accelerator. It creates a bottleneck where all work must wait for approval from a small group. SAFe promotes decentralized decision-making to empower teams, reduce wait times, and allow for faster, more informed choices closer to the actual work being performed.
- ✗
Prioritize long-term projects over short-term feedback loops.
Why it's wrong here
Focusing on long-term projects without interim feedback increases the risk of building the wrong thing. SAFe relies on short, iterative feedback loops to validate assumptions and adjust course. Prioritizing long-term projects undermines agility and makes it impossible to pivot based on changing market conditions or stakeholder needs.
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.