The correct answer is A – Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.
Sprint reviews are designed to showcase the completed product increment to stakeholders and receive feedback. The primary goal is to validate that the work delivered provides value to the customer—not to present technical details. Demonstrating working software is one of the core tenets of Agile.
From the PMI Agile Practice Guide:
“Sprint reviews are working sessions designed to elicit feedback and foster collaboration. Teams demonstrate completed work and adjust the backlog based on stakeholder input.”
(PMI Agile Practice Guide, Section 5.3 – Value Delivery)
Mike Griffiths confirms:
“The output of every iteration should be potentially shippable product. The sprint review is for stakeholders to see that output and provide feedback to inform future development.”
(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 2 – Value-Driven Delivery)
Other options explained:
B may be helpful, but it doesn’t solve the immediate issue of misaligned sprint reviews.
C misunderstands the purpose of the sprint review—it’s not about architecture.
D changes the audience instead of correcting the approach.
Answer: A
══════════
