Jean Michel Diaz
Jean Michel Diaz

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 (including 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
5 Ideas for Sprint Retrospectives Your Team Will Love

5 Ideas for Sprint Retrospectives Your Team Will Love

As a psychologist and Scrum Master, I probably have an unusual view of Sprint Retrospective ideas. I have a slightly stronger focus on the "soft" side of continuous improvement. You could also talk...

My 7 All-Time Favorite Agile Retrospective Templates

My 7 All-Time Favorite Agile Retrospective Templates

In my team, we conduct an agile retrospective more often than average: every Friday, i.e. once a week. And you won't believe it - thanks to the many super agile retrospective templates, among other...

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

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

There are various measures and approaches to improve communication in virtual or remote engineering teams of software developers and software engineers. It is irrelevant whether they are front-end,...

DORA & SPACE Metrics: 2 Team Workshops to improve them

DORA & SPACE Metrics: 2 Team Workshops to improve them

If you're a tech leader, you probably want to know how well your team is delivering software and how you can improve it. You may have heard of the DORA metrics and the SPACE framework, two powerful...

Working Agreements: 10 Examples, Samples & Templates

Working Agreements: 10 Examples, Samples & Templates

Effective collaboration in teams is crucial for success, especially in the context of agile methods such as Scrum. Working Agreements play a crucial role in creating a clear framework for collabora...

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

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

As a team lead, you take on a lot of responsibility for your employees and your team. This checklist for team leads will make it easier for you to keep an overview and ensure that nothing goes wron...

The Scrum Master as Servant Leader: 8 Tips & Thoughts

The Scrum Master as Servant Leader: 8 Tips & Thoughts

As an experienced psychologist and Scrum Master, I understand the challenges that team leads face in agile environments. Finding the balance between agility and leadership is no easy task. In this...

Not Every Scrum Team Is Agile: Fake Agile

Not Every Scrum Team Is Agile: Fake Agile

Fake Agile: Is every Scrum team agile? No, unfortunately not every Scrum team is actually agile. Let me explain: A Scrum team is defined by working according to the Scrum framework: So it has sprin...

Fix Zombie Scrum in 3 Steps

Fix Zombie Scrum in 3 Steps

What is Zombie Scrum? Zombie Scrum describes teams that have retained the Scrum structure (rituals, roles, etc.) but have lost the actual core – customer benefits, values and continuous improvement...

Echometer Newsletter

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