An agile team delivered a feature in the last iteration. The product owner, who missed the planning and review meetings, was dissatisfied with the feature. The team conducted a retrospective and…

Question

Options

• AEnsure that the product owner reviews the acceptance criteria for delivered user stories.
• BAugment the quality assurance and continuous integration processes for delivery.
• CApproach the relevant developers and testers regarding quality issues in upcoming iterations.
• DAsk the product owner to define the entire scope of delivery two to three iterations in advance.

• A
  72% (41)
• B
  4% (2)
• C
  7% (4)
• D
  18% (10)

Explanation

The core issue is that the product owner missed both the planning and review meetings and was then dissatisfied with the output. This signals a breakdown in acceptance criteria validation. The correct next step is to ensure the product owner reviews and agrees to the acceptance criteria for delivered user stories-this prevents future misalignment between what was built and what the PO expected. Option B addresses process quality but not the root cause. Option C targets developers/testers but the problem stems from unclear requirements and absent PO engagement. Option D (locking scope 2-3 iterations ahead) is contrary to agile's adaptive nature.

No community discussion yet for this question.