SAFe-Agilist Product Development Flow Practice Question
Exhibit
System Flow Metrics: - Lead Time: 28 days - Processing Time: 6 days - Wait Time: 22 days - Throughput: 4 items/iteration
Refer to the exhibit. Based on these metrics, which strategy should the ART prioritize to optimize Product Development Flow?
⚠ Common exam trap
Test-takers often assume workers need to increase their individual speed or output, missing that high wait times require shrinking batch sizes and removing handoffs.
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
✓
Implement small batch sizes and reduce handoffs.
The ratio of wait time to processing time is significantly high, indicating that the system suffers from excessive queueing. In product development, work spends most of its time waiting for the next process step, not being actively processed. By focusing on reducing wait times—often caused by handoffs, batch sizes, or resource contention—the ART can drastically improve overall lead time without necessarily needing to increase individual worker effort or speed.
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 developer hours to improve processing time.
Why it's wrong here
Processing time is only six days out of twenty-eight. Even a significant reduction in processing time would yield minimal impact on the total lead time. The bottleneck is clearly the wait time, suggesting that work is sitting idle rather than being hampered by slow manual effort.
- ✓
Implement small batch sizes and reduce handoffs.
Why this is correct
Reducing batch sizes is the most effective way to address wait times. Smaller items move through the system faster and create fewer dependencies. Minimizing handoffs reduces the time work sits in a queue waiting for someone else to pick it up, directly lowering the lead time.
- ✗
Increase the throughput target for the next iteration.
Why it's wrong here
Increasing throughput targets without addressing the current wait time will likely increase the work-in-process (WIP). Higher WIP leads to even longer queues, which would further inflate the already high wait time, potentially causing a feedback loop that degrades the overall system's stability and predictability.
- ✗
Focus on automating the testing phase.
Why it's wrong here
While automation is beneficial, the current metrics show that wait time is the dominant factor in the lead time. Unless the testing phase is identified specifically as the primary queue, focusing exclusively on automation may not address the systemic issues causing the high wait time.
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.