Difference Between Sprint Review and Retrospective
Sprint Review and Retrospective in the Scrum Cycle
The sprint review and retrospective are back-to-back in the Scrum cycle. The order has a reason, as we will see in a moment:
Sprint review vs. retrospective
Definition: Sprint Review
Definition: Sprint Retrospective
The sprint retrospective however, takes place after the sprint review. Here the Scrum Team reflects on their collaboration and opportunities for improvement. In order to be able to fully carry out this reflection, a review must have taken place before the retrospective.
Differences Between Sprint Review and Retrospective
Here you will also find the differences clearly in table form:
|Focus||The work products of the last sprint||Continuous improvement of cooperation|
|Attendees||Team members (i.e. developers, scrum masters and product owners), |
and ideally also stakeholders (users, managers, customers or other departments)
|Only the team itself, i.e. developers, scrum masters and product owners|
|Time||At the end of the sprint, before the retrospective||At the end of the sprint, after the review|
Can I combine Sprint Review and Retrospective?
Yes, in principle Sprint Review and Retrospective can be combined. However, it is questionable whether the participants have enough energy to carry out these two comprehensive appointments in a row with full concentration.
As a rule, it is therefore recommended to plan at least one break between the sprint review and the retrospective. For example, ideally the sprint review would be in the morning and the retrospective in the afternoon. Alternatively, you can simply put the appointments on two consecutive days.
Conclusion: Sprint Review and Retrospective Are Not the Same
In short: In the Scrum cycle, the sprint retrospective takes place after the sprint review. While the sprint review focuses on the concrete work results, the retrospective focuses on the continuous improvement of cooperation.