Sprint Review vs. Sprint Retrospective: Purpose and Audience

WHAT THIS TESTS: This question tests your understanding of the two core feedback loops in Scrum, which are based on the principles of inspection and adaptation. The interviewer is checking if you can distinguish between the feedback loop for the product (what was built) and the feedback loop for the process (how it was built). For a senior candidate, this demonstrates an understanding of continuous improvement at both the product and team levels.

A GOOD ANSWER COVERS: A strong answer clearly differentiates the two events across three dimensions: purpose, audience, and outcome. First, explain the Sprint Review: its purpose is to inspect the outcome of the Sprint (the Increment) and determine future adaptations. Its audience is the Scrum Team and key stakeholders. Its primary outcome is a revised Product Backlog that reflects new knowledge and feedback. Second, explain the Sprint Retrospective: its purpose is to plan ways to increase quality and effectiveness. Its audience is strictly the Scrum Team (Developers, Product Owner, Scrum Master) to ensure psychological safety. Its primary outcome is a list of actionable improvement items for the next Sprint.

COMMON WRONG ANSWERS: The most common red flag is describing the Sprint Review as a 'demo'. A demo is a passive, one-way presentation. A Sprint Review is an active, collaborative working session to gather feedback and adapt plans. Another significant error is confusing the audiences, such as suggesting stakeholders should attend the Retrospective (which undermines open discussion) or that the team's internal process is the main topic for the Review. Weak answers simply recite definitions without connecting them to the 'why'—the empirical process control at the heart of Scrum.

LIKELY FOLLOW-UPS: Expect questions like: 'How do you handle a Sprint Review when key stakeholders consistently don't attend?' or 'Describe a specific, impactful process improvement that came out of a Retrospective you participated in.' or 'What happens if, during the Review, you realize the Increment doesn't meet the Definition of Done?'

ONE CONCRETE EXAMPLE: In a Sprint Review, the team presents a new user profile page. Stakeholders from the legal department attend and point out that the data privacy controls are not compliant with a new regulation. The Product Owner immediately adds a high-priority item to the Product Backlog to address this. The Review inspects the product. The next day, in the Sprint Retrospective, the team discusses how this was missed. They identify that their refinement process lacks a legal review checkpoint. They decide to add this checkpoint to their Definition of Ready for all user-facing stories. The Retrospective inspects the process.