SAFe-Agilist Product Development Flow Practice Question
Exhibit
Team Velocity: 40 points/iteration Average Feature Duration: 2 weeks Queue Size: 12 features Policy: Maximize Flow Efficiency.
Refer to the exhibit. Based on the provided metrics, what is the most significant indicator of a flow efficiency problem?
⚠ Common exam trap
Candidates often misidentify low developer velocity as the primary flow issue, ignoring the massive hidden waste represented by inflated queue sizes in the exhibit data.
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
✓
The large queue size of 12 features.
The large queue size relative to team velocity suggests that features are waiting significantly longer than they are being worked on. In a flow-based system, excessive queue sizes are the primary indicator that the system is 'stalled.' This waiting period represents a massive cost of delay and indicates that the team is failing to maintain a smooth, continuous flow of value, requiring an immediate reduction in active WIP to clear the backlog.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
High team velocity.
Why it's wrong here
A velocity of 40 points is a measure of capacity and is neither good nor bad on its own. The problem is not how fast the team works, but rather that the queue is too long, meaning they are likely working on too many things simultaneously.
- ✗
Average feature duration of 2 weeks.
Why it's wrong here
A 2-week duration might be appropriate for the feature size. The issue is not necessarily the speed at which a feature is completed, but the time spent sitting in the queue before development even begins, which is driven by the total number of items currently in the system.
- ✓
The large queue size of 12 features.
Why this is correct
A queue of 12 features indicates that work is piling up faster than it is being completed. This queue size is the primary cause of long wait times and poor flow efficiency, necessitating a reduction in WIP to restore balance and ensure a faster delivery of individual features.
- ✗
The iteration length is too short.
Why it's wrong here
Iteration length is a standard SAFe construct and is not the cause of flow inefficiency. The problem lies in the work management and queueing behavior, not the structural cadence of the PI, which is designed to support, not hinder, the delivery of features to the customer.
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.