SAFe-Agilist Product Development Flow Practice Question
Which of the following is a common symptom of 'hidden queues' in a product development process?
⚠ Common exam trap
Candidates often assume 'hidden queues' only exist in physical manufacturing or are caused by external vendors, missing that internal 'Done' status items are the most common source of hidden inventory.
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
✓
Items waiting in a 'Done' state for integration or final validation.
Hidden queues often manifest as items that are 'done' but not truly finished—for example, code that is written but not yet integrated, tested, or deployed. These items represent inventory that has not yet delivered value. Detecting these queues is essential because they frequently hide the true lead time and create significant delays that aren't immediately obvious on a surface-level status report.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Teams finishing their work ahead of schedule every time.
Why it's wrong here
Finishing ahead of schedule is usually a result of good estimation or low complexity, not a symptom of hidden queues. If teams were constantly finishing early, it might suggest that they are not taking on enough work, but it does not represent the presence of queue-related delays.
- ✓
Items waiting in a 'Done' state for integration or final validation.
Why this is correct
This is a classic form of a hidden queue. Items that appear complete but are waiting for another process step are not delivering value yet. Because they are marked 'done,' they are often ignored in reports, but they are still contributing to high lead times and delaying the feedback loop.
- ✗
A high number of bugs being found in production.
Why it's wrong here
High bug counts in production suggest quality issues, not necessarily hidden queues. While poor quality can lead to rework and bottlenecks, the specific symptom of a hidden queue is an accumulation of work waiting for the next step, not the failure of the work that was already delivered.
- ✗
Consistent team velocity across multiple iterations.
Why it's wrong here
Consistent velocity is a sign of a stable and predictable team process. It is a positive indicator in Agile, not a symptom of a problem. Hidden queues would typically cause velocity to fluctuate as the team struggles with dependencies, but consistency itself is a sign of good flow control.
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.