What should the product owner have done differently?

Iteration reviews (or sprint reviews) are designed to demonstrate completed, potentially shippable product increments. According to the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance), the purpose of the iteration review is to showcase work that meets the Definition of Done (DoD) and to receive stakeholder feedback. Demonstrating incomplete or in-progress stories can mislead stakeholders about progress and reduce trust in the team.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) emphasizes the importance of showing only completed work to maintain transparency and clarity in stakeholder communication.

Option A is correct: only completed stories should be demoed to ensure expectations are managed effectively.

Option B and C are not part of the typical iteration review agenda unless explicitly required.

Option D is incorrect, as it blurs the line between done and in-progress work.