SAFe-Agilist Product Development Flow Practice Question
Exhibit
Team Velocity Graph: - Iteration 1: 20 pts - Iteration 2: 22 pts - Iteration 3: 15 pts - Iteration 4: 21 pts - Iteration 5: 19 pts
Refer to the exhibit. What does the dip in Iteration 3 suggest regarding Product Development Flow?
⚠ Common exam trap
Candidates often assume the dip represents a team performance issue or lack of skill, leading them to choose answers focused on retraining or performance management rather than systemic flow analysis.
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
✓
There was likely a systemic interruption or blocker.
In an Agile environment, a single-point dip in velocity is often caused by external factors such as dependencies, team sickness, or a specific bottleneck encountered during that iteration. Rather than blaming the team, SAFe advocates for investigating the systemic cause (the 'why'). Analyzing this dip helps teams identify impediments that disrupted the flow of work, allowing them to adjust processes and prevent the same issue from reoccurring in future iterations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The team needs more training on estimation techniques.
Why it's wrong here
Estimation is not the issue here. A drop in velocity usually reflects an interruption in the work process. Assuming it's an estimation problem ignores the real, systemic blockers that occurred during the iteration. The team needs to inspect the process, not just their planning capability.
- ✗
The team is unmotivated and needs management intervention.
Why it's wrong here
Assuming a lack of motivation is rarely the correct conclusion. SAFe emphasizes building self-organizing teams. A velocity dip is a data point, not an indictment of team character. Management intervention often creates more fear and disruption, damaging the psychological safety required for high-performing, flowing teams.
- ✓
There was likely a systemic interruption or blocker.
Why this is correct
Fluctuations in velocity often indicate external dependencies or system bottlenecks. Investigating the specific circumstances of Iteration 3 will reveal what stopped the flow. This allows for root cause analysis and proactive mitigation, ensuring that future iterations are less susceptible to similar disruptions and maintain a consistent flow.
- ✗
The team should commit to fewer points in the next PI.
Why it's wrong here
Blindly committing to fewer points does not address the actual cause of the drop. The team should analyze what went wrong to make the process more resilient. If the issue is resolved, they can likely return to their normal velocity without artificially lowering their commitment levels.
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.