For some people, sprint review and sprint retrospective might sound almost the same. And if you are that person who is just starting to use Scrum then it is highly likely you’ll find no differences between the two terms. Sadly, even the experienced scrum teams are sometimes unable to point out the difference between the two. And as a result, they either run only one of the two meetings. Or what they also do is merge these two meetings into some detrimental combination. So my friend, it is very important that you don’t make any such type of mistake. As both meetings serve completely different purposes and both have clear differences, it is important to clear up your mind relevant to these two terms.
Sprint Reviews/Sprint Retrospective in a nutshell:
Before diving deep into the terms, we thought why not explain both the terms to our readers in just one line?
Well, sprint review is all about the product. And sprint retrospective is all about the team.
This means that the focus of the sprint review is to regularly meet the customer expectations. Whereas, scrum retrospective helps the team to become even faster and deliver on time. Now that you know what both the terms are, let us now dive deep into what both terms have to offer.
Understanding what sprint review is?
As the focus of sprint review is to meet the customer expectation, this meeting makes sure that the team is producing a potentially shippable product increment. It is meeting that is held at the end of the sprint and is attended by the scrum team and all stakeholders. Together they discuss what has been accomplished so far during the sprint and whether the goal has been achieved or not.
Who can attend the sprint review?
The individuals who are authorized to attend this meeting are:
- Product Owner
- Product Manager
- Scrum Master
- Development Team
And all those are a part of the product creation process.
More or less an informal meeting
Sprint review is considered to be an informal meeting where the team has to present the product increment. When the scrum team is done presenting, the stakeholders then provide feedback.
Duration of the sprint review:
Usually a sprint review should not last for more than one hour per each week of the sprint. This means that the duration of sprint review in a month has to be 4 hours or less and not more. A scrum master thus has to make sure that the duration of the sprint review is not exceeding the designated time limit.
Agenda of sprint review:
A sprint review meetings should have the following things on agenda.
- Sprint review involves the product owner informing the entire scrum team about the completed tasks and the ones which are in-completed.
- The developers are supposed to discuss problems that they encounter during the sprint and how to solve them.
Discussions about which tasks are next thereby providing a great basis for the next sprint planning meeting.
Understanding what sprint retrospective is?
Just when you are done with the sprint review meeting, what comes next is the sprint retrospective meeting. And if you have read all of the above and this, then by now you should have understood both are not the same thing. Sprint review as we explained earlier focuses on what the team is building, the sprint retrospective is highly focused on how they are building it.
Who can attend the sprint retrospective?
The following three must attend this meeting:
- Scrum team
- Product owner
- Scrum master
Duration of sprint retrospective:
This meeting is a little shorter than the sprint review and that is why it lasts around three hours per month-long sprint. As the time is short and you don’t even have a full hour for each sprint retrospective, you must make sure that the entire scrum team and the product owner attends and participates in this meeting. You might also be interested in best operations management courses.
Agenda of the sprint retrospective:
Sprint retrospective has the following agenda:
- The purpose of this meeting is to improve the overall development process.
- The scrum team in this meeting sheds light on the previous sprint and discusses what is working well and what can be improved.
- Similarly, what can be done to improve the overall productivity is also discussed.
Now you would say that all these improvements are also implemented in the sprint. You might be right here but discussing all this in the sprint retrospective gives the Scrum team a chance to discuss the process in detail. With that, the team members are also given a chance to voice their opinions. If you’re looking for a guide to Scrum & Agile software development, then visit here.
So you see, both sprint review vs sprint retrospective are quite different from one another and it is important that everyone must know what they are. And that is what this article is about. So understand Sprint Review VS Sprint Retrospective here and never stop learning.