POPM Iteration Execution Practice Question
During an Iteration Review, a key stakeholder expresses dissatisfaction with a delivered user story because it does not include a critical compliance workflow. The Product Owner is surprised since the team finished all acceptance criteria. How should the Product Owner handle this situation?
⚠ Common exam trap
Candidates often try to 'fix' the story by pressuring the team to redo it, failing to recognize that new requirements must be managed through the backlog refinement process.
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
✓
Capture the missing requirement as a new backlog item, refine it, and prioritize it for an upcoming iteration.
The Product Owner must collaborate with the stakeholder and team to capture the missing compliance requirement as a new backlog item and prioritize it for the upcoming iteration. This scenario highlights the importance of continuous stakeholder engagement throughout the iteration execution lifecycle to prevent surprises and maintain alignment on business value.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately halt the current iteration and force the team to rework the completed user story.
Why it's wrong here
Halting the iteration discards the team's completed work and destabilises delivery cadence; the missing compliance workflow is new scope, not a defect against agreed acceptance criteria. It is tempting as decisive action, but the Product Owner should instead add the workflow to the backlog and let the team prioritise it through normal flow.
- ✓
Capture the missing requirement as a new backlog item, refine it, and prioritize it for an upcoming iteration.
Why this is correct
Capturing the requirement as a new backlog item ensures it goes through proper refinement and prioritization. This maintains the integrity of the current iteration while addressing the stakeholder's valid compliance concern in a structured manner.
- ✗
Refuse to add the workflow since the team successfully met all previously agreed-upon acceptance criteria.
Why it's wrong here
Meeting acceptance criteria does not discharge the Product Owner's duty to manage stakeholder expectations and backlog transparency; refusing forecloses renegotiation. It is tempting because acceptance criteria are the agreed contract for a story, and refusing scope creep is legitimate when the workflow was never in scope and a new story should be raised instead.
- ✗
Blame the stakeholder for failing to communicate the compliance workflow during backlog refinement sessions.
Why it's wrong here
Blaming the stakeholder for a refinement gap damages trust and ignores the Product Owner's accountability for backlog completeness and stakeholder engagement. It is tempting when the PO feels the requirement was never raised, but the constructive response is to acknowledge the gap, capture the compliance workflow, and prioritise it transparently.
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.