Sprint Review vs. Retrospective: Simply explained with Image

Difference Between Sprint Review and Retrospective

We defined in the last article, what a retrospective really is . We also talked about Scrum as a framework for agile working methods. And in this framework, in addition to the retrospective, there is also a meeting format called Sprint Review.

So how do these two formats differ?

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 and Retrospective in the Scrum Cycle

Sprint Review and Retrospective in the Scrum Cycle

Sprint review vs. retrospective

Definition: Sprint Review

The Scaled Agile Framework Sprint Review is a workshop at the end of a Scrum Sprint cycle where a Scrum Team reviews what was accomplished during the last Sprint. Based on this, the so-called product backlog is updated.

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:

 Sprint ReviewRetrospective
FocusThe work products of the last sprintContinuous improvement of cooperation
AttendeesTeam members (i.e. developers, Scrum Master and Product Owner), and ideally also stakeholders (users, managers, customers or other specialist departments)Only the team itself, i.e. developers, scrum masters and product owners
TimeAt the end of the sprint, before the retrospectiveAt 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.

By the way, if you are still looking for a suitable retro board (with 60+ agile retrospective formats), this post can help you: Comparing the 6 best retrospective boards

Credits: Pointing photo created by wayhomestudio - www.freepik.com

Blog category

More articles on "Agility tips"

View all articles in this category
Agile Spotify Model: Squads, Tribes, Chapters & Guilds Explained

Agile Spotify Model: Squads, Tribes, Chapters & Guilds Explained

The agile Spotify model with Squads, Tribes, Chapters and Guilds simply explained. Learn more about advantages, typical stumbling blocks and use cases.

5 Ideas for Sprint Retrospectives Your Team Will Love

5 Ideas for Sprint Retrospectives Your Team Will Love

Discover 5 Sprint Retrospective Ideas Your Team Will Celebrate! From Battery Retro to Sailboat – Improve Your Agile Processes and Teamwork.

My 7 All-Time Favorite Agile Retrospective Templates

My 7 All-Time Favorite Agile Retrospective Templates

Discover 7 unusual templates for agile retrospectives that are guaranteed to motivate your team! From Battery to CEO – new impulses for your next sprint retro.

How can you improve communication in a remote software development team?

How can you improve communication in a remote software development team?

Improve communication in remote software teams! Discover effective measures for agile software development, from 1-1 meetings to retrospectives.

DORA & SPACE Metrics: 2 Team Workshops to improve them

DORA & SPACE Metrics: 2 Team Workshops to improve them

Optimize your software deployment with DORA & SPACE metrics! In this article, you'll learn how to improve performance with team workshops.

Working Agreements: 10 Examples, Samples & Templates

Working Agreements: 10 Examples, Samples & Templates

Agile Working Agreements: 10 Examples, Patterns & Templates for Scrum, Remote Teams and SAFe. How to improve collaboration and strengthen teams!

Checklist for Team Leads: 10 key Tasks (incl. PDF)

Checklist for Team Leads: 10 key Tasks (incl. PDF)

10 Tasks for Team Leaders: This checklist helps you keep track and lead your employees optimally. ✓ Download now as a free PDF!

The Scrum Master as Servant Leader: 8 Tips & Thoughts

The Scrum Master as Servant Leader: 8 Tips & Thoughts

Learn how to become a Servant Leader as a Scrum Master! 8 tips on communication, self-organization, and agile project management for your agile team.

Not Every Scrum Team Is Agile: Fake Agile

Not Every Scrum Team Is Agile: Fake Agile

Not every Scrum Team is agile: Learn what Fake Agile means, what causes it (lack of customer feedback, focus on velocity) and how to protect yourself.

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working