Skip to content
BENIBIX Learn

Sprint Review vs Sprint Retrospective

People think the review and the retrospective are one meeting. The review looks at the product, with stakeholders in the room. The retrospective looks at how the team worked, and only the team is there.

Business📋 Agile Delivery

Sprint Review

The meeting where a team shows a sprint's work. The people it is for say what should come next.

The Sprint Review is the event near the end of a sprint where the team shows what it made. The Scrum Team and key stakeholders look at the work together. They talk about what has changed around the product. Then they decide what to do next, which can reshape the Product Backlog. It takes up to four hours for a one-month sprint.

Example
At the end of sprint 8, Lucy's team shows the new search page to three shop owners. They ask for a price filter, and it goes near the top of the backlog.
Why it matters
It brings real users and buyers into every sprint. Feedback arrives while it is still cheap to act on.
Full entry
Business📋 Agile Delivery

Sprint Retrospective

The meeting at the end of each sprint where the team improves the way it works.

The Sprint Retrospective is the last event of a sprint. The Scrum Team looks at how it worked, not at what it built. It asks what went well, what went wrong and why. Then it picks the most useful changes to try. Some may go straight into the next sprint's plan. It takes up to three hours for a one-month sprint.

Example
Emma's team finds that half its bugs came from rushed code reviews. They agree that in the next sprint, no code goes in without a second reader.
Why it matters
A team that never looks at how it works repeats the same mistakes. Small fixes each sprint add up fast.
Full entry

In one line

Sprint Review
The meeting where a team shows a sprint's work. The people it is for say what should come next.
Sprint Retrospective
The meeting at the end of each sprint where the team improves the way it works.