Answer guide
Read the answer guide
A demo shows finished work; a Sprint Review inspects the Increment with stakeholders and uses what is learned to adapt the Product Backlog. The team and stakeholders discuss what was done, what changed in the market or the business, what to do next and how progress is heading towards the Product Goal. A demonstration may be part of it, but the aim is a working conversation and feedback, not a presentation. For instance, a stakeholder's comment can reorder the backlog for the next Sprint.
What the interviewer is assessing
Whether you see the review as collaborative inspection that changes the plan, not a showcase.
A strong answer covers
- The Sprint Review is where the team and stakeholders inspect the Increment together, not just watch finished work.
- What is learned is used to adapt the Product Backlog, for example a comment reordering the next Sprint.
- A demo may be part of it, but the aim is a working conversation and feedback, not a showcase.
- Cover what changed in the market or business and how progress is heading towards the Product Goal.
Common mistakes
- Treating it as a formal presentation where stakeholders just watch and approve.
- Holding it without stakeholders, so no feedback reaches the backlog.
Practise a follow-up
- How would you run a review when the Increment has little visible change?
- Who decides whether the Increment is released after the review?