Sprint Review vs. Sprint Retrospective: Purpose and Participants
Tests if you distinguish inspecting the product (Review) from the process (Retro). A good answer defines purpose (what vs. how), participants (stakeholders vs. team-only), and outcomes (backlog vs. process improvements).
What's really being asked
This question tests your practical, not just theoretical, understanding of Scrum's feedback loops. The interviewer is checking if you can distinguish between inspecting the PRODUCT versus inspecting the PROCESS. For a senior candidate, this means articulating the 'why' behind the structure of these meetings, especially regarding participants and psychological safety.
The full answer
A strong answer defines the two events across three distinct axes. First, PURPOSE: the Review is about inspecting the Increment and adapting the Product Backlog (the 'what'). The Retrospective is about inspecting the team's effectiveness and planning improvements (the 'how'). Second, PARTICIPANTS: the Review includes the Scrum Team and key stakeholders. The Retrospective is strictly for the Scrum Team (Product Owner, Scrum Master, and Developers) only. Third, OUTCOMES: the Review's main outcome is a revised Product Backlog. The Retro's main outcome is at least one actionable process improvement for the next Sprint.
The mistakes people make
A major red flag is suggesting stakeholders should attend the Retrospective. This undermines the psychological safety required for the team to have a candid discussion about its internal workings. Another common mistake is calling the Sprint Review a 'demo' or a 'sign-off' meeting. It is a working session for collaboration and feedback, not a formal gate. Finally, describing the Retrospective as just a venting session without a focus on creating specific, actionable improvements for the next Sprint shows a lack of maturity.
What usually comes next
A common follow-up is, 'How would you handle a senior stakeholder who insists on joining the Retrospective?' This tests your ability to uphold process and explain its value. Another is, 'What do you do in a Sprint Review if the team didn't complete an Increment?' This tests your understanding of transparency. Expect behavioral questions like, 'Tell me about the most effective process improvement that came out of a Retrospective you were in.'
A concrete example
For a two-week sprint, the Sprint Review might be a 2-hour meeting. The team presents a new checkout flow. Stakeholders from marketing and finance provide feedback, noting that the tax calculation is confusing. The Product Owner adds 'Simplify tax display in checkout' to the Product Backlog. The Sprint Retrospective would be a 90-minute meeting afterward. Only the Scrum Team attends. They discuss that vague requirements for the tax feature caused rework. They decide to implement a 'requirements readiness' checklist as their process improvement for the next Sprint.
Interview question
Which statement accurately distinguishes the participant attendance between a Sprint Review and a Sprint Retrospective?
- a.Stakeholders are invited to the Sprint Retrospective to provide feedback on team performance, and the Sprint Review is a formal sign-off meeting for the Product Owner.
- b.Both meetings require the full Scrum Team and key stakeholders to ensure complete transparency and feedback.
- c.The Sprint Review includes the Scrum Team and key stakeholders, while the Sprint Retrospective is exclusively for the Scrum Team.Correct
- d.The Sprint Retrospective is primarily for the Development Team to discuss technical issues, with the Scrum Master facilitating, while the Product Owner leads the Sprint Review.
Why? this is the answer
The card explicitly states that the Sprint Review includes the Scrum Team and key stakeholders, focusing on product inspection. Conversely, the Sprint Retrospective is strictly for the Scrum Team only to ensure psychological safety for candid process inspection. Inviting stakeholders to the Retrospective, as suggested in a distractor, is a common misconception and undermines its purpose.
Just read this? Test yourself on what you have been reading.
Read the original → scrumguides.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles