POPM Iteration Execution Practice Question
If a team's velocity is consistently lower than the plan, what is the best first step for the Product Owner?
⚠ Common exam trap
Test-takers frequently assume the PO should immediately pressure the team to increase speed or reduce story sizes without investigating the underlying bottlenecks.
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
✓
Collaborate with the team to identify bottlenecks and impediments.
The PO should initiate an open discussion with the team to understand the root cause of the velocity gap. This might involve looking at technical debt, team capacity, or the complexity of the work itself. By engaging the team rather than making assumptions, the PO can identify realistic solutions to stabilize the delivery process and ensure that future PI commitments are based on accurate, achievable data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Assign more stories to the next iteration to force higher velocity.
Why it's wrong here
Force-feeding the backlog does not improve velocity; it only increases the amount of work in progress and lowers the team's morale. Velocity is a reflection of the team's actual capacity, and trying to manipulate it through arbitrary assignments is counterproductive and leads to poor quality outcomes.
- ✓
Collaborate with the team to identify bottlenecks and impediments.
Why this is correct
Identifying the root cause is the only way to address a performance gap. The PO's role is to support the team by clearing roadblocks and adjusting the backlog to ensure the team can work effectively. This collaborative approach turns a negative trend into an opportunity for constructive process improvement.
- ✗
Report the team to management for underperformance.
Why it's wrong here
Reporting the team is a punitive measure that destroys trust and psychological safety. It ignores the systemic issues that usually cause low velocity. The PO should be a partner in solving these problems, not a supervisor who reports on the team's failures to higher-level management.
- ✗
Reduce the team's quality requirements to increase speed.
Why it's wrong here
Sacrificing quality to achieve higher velocity is a classic mistake. It creates more technical debt, which will only slow the team down further in the future. Quality is the foundation of speed in Agile, and the PO should never encourage the team to cut corners on the Definition of Done.
About these practice questions
Courseiva writes every POPM question from scratch — 336 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 POPM 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 POPM exam.