Sprint Review vs. Retrospective: Purpose and Participants

WHAT THIS TESTS: This isn't just a vocabulary quiz. It tests if you understand the fundamental separation between inspecting the WHAT (the product) and inspecting the HOW (the process). Interviewers want to see that you recognize these are two distinct, equally important feedback loops that drive empirical process control in Scrum. Your answer reveals your depth of understanding of WHY Scrum works, not just what the events are.

A GOOD ANSWER COVERS: A strong answer clearly distinguishes the two events across two axes: purpose and participants. First, for Sprint Review, state its purpose is to inspect the Sprint's outcome (the Increment) and adapt the Product Backlog. Mention the participants are the Scrum Team AND key stakeholders. Second, for Sprint Retrospective, state its purpose is to inspect the team's effectiveness (people, processes, tools) and create a plan for improvement. Emphasize that participants are ONLY the Scrum Team (Product Owner, Scrum Master, Developers) to ensure psychological safety. Mentioning the timeboxes (max 4 hours for Review, 3 for Retro, for a one-month sprint) adds valuable precision.

COMMON WRONG ANSWERS: The biggest red flag is mixing up the participants, especially suggesting stakeholders attend the Retrospective. This shows a fundamental misunderstanding of the need for a safe space for the team to be candid. Another common mistake is describing the Sprint Review as just a "demo." While a demonstration of the Increment may happen, its primary purpose is inspection and collaboration, not a one-way presentation. Finally, weak answers are vague, using terms like "talk about what went well" without connecting it to the specific focus of either the product or the process.

LIKELY FOLLOW-UPS: "What is an example of an actionable outcome from a Retrospective?" (e.g., We will add a linting step to our CI pipeline). "How would you handle a Product Owner who wants to skip the Retrospective to 'save time'?" (e.g., Explain its value in long-term velocity and quality improvement). "Who is responsible for facilitating these meetings?" (The Scrum Master ensures they take place and are productive).

ONE CONCRETE EXAMPLE: In a Sprint Review for a new e-commerce feature, the team and stakeholders (like the Head of Marketing) might decide that based on the Increment shown, the planned "social sharing" feature is less important than improving checkout performance. The Product Owner then re-orders the Product Backlog. In the subsequent Sprint Retrospective, the team alone might identify that code reviews were taking too long and decide to experiment with a 24-hour SLA for initial feedback in the next Sprint.