SAFe-Agilist Product Development Flow Practice Question
A Release Train Engineer notices that a feature has been in the program backlog for 12 weeks but only 3 weeks of actual work was performed on it. The rest of the time it sat in various queues. Which SAFe flow metric best highlights this issue?
⚠ Common exam trap
Many exam-takers confuse flow load or velocity with flow efficiency, which specifically measures the proportion of time work is actively progressed versus waiting.
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
✓
Flow efficiency
Flow efficiency is the SAFe metric that compares active work time to total lead time. With only 3 weeks of active work out of 12 weeks total, the flow efficiency is 25 percent, revealing that most of the delay is due to waiting in queues. This metric helps teams target queue reduction and improve overall flow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Flow load
Why it's wrong here
Flow load indicates the number of items in the system at a given time. While a high flow load can contribute to long queues, it does not directly measure the ratio of active work to wait time. The RTE needs a metric that exposes the 9 weeks of waiting, not just the count of items.
- ✗
Flow velocity
Why it's wrong here
Flow velocity measures the rate at which a train delivers business value, typically story points or features per PI. It does not isolate the proportion of time work spends waiting versus being actively worked on. Here, the issue is excessive queue time, so flow velocity would not pinpoint the delay between value-added activities.
- ✗
Flow distribution
Why it's wrong here
Flow distribution measures how work is spread across different types, such as features, defects, and risks. It helps balance investment but does not reveal how much time a single item spends waiting versus being worked on. The scenario points to a queueing problem, not an imbalance in work types.
- ✓
Flow efficiency
Why this is correct
Flow efficiency is the ratio of active work time to total lead time. In this scenario, active work was 3 weeks out of 12 weeks total, yielding a flow efficiency of 25 percent. This metric directly exposes the large amount of queue time and is the SAFe-recommended measure for identifying delays caused by waiting.
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.