Sprint Review vs Sprint Retrospective

 

Although sprint review and sprint retrospective can be confused as the same thing, these two Scrum events are completely different. Here’s what each one represents.

 

Sprint Review

In each sprint, the Scrum team should produce a potentially shippable product increment. Sprint review is the meeting at the end of the sprint where the Scrum team and all the stakeholders get together and discuss what has been accomplished during the sprint and whether the sprint goal has been met.

The meeting should be attended by the product owner and manager, Scrum Master, development team, management, and anyone else who is involved in the product creation process.

This is usually an informal type of meeting where the Scrum team presents the product increment, while the other stakeholders provide feedback. It shouldn’t last more than four hours per month-long sprint. The Scrum Master needs to ensure the meeting doesn’t run longer than that.

Sprint Review Agenda

Aside from presenting the work done during the sprint, sprint review meetings should have a few other things on the agenda:

  • The product owner needs to inform the team on the tasks that have been completed and those that are still not done.
  • The developers need to discuss the problems they encountered during the sprint and how they were solved.
  • The Scrum team answers sprint-related questions from the rest of the team. 
  • The team should discuss which tasks come next, something that gives a great basis for the next sprint planning meeting.

 

Sprint Retrospective

Sprint retrospective meeting takes place immediately after the sprint review. While sprint review is a discussion about what the team is building, sprint retrospective is focused on how they’re building it.

This meeting is usually slightly shorter than the sprint review and shouldn’t last more than three hours per month-long sprint. For the most effective meeting, the whole Scrum team, including the product owner, should attend and participate.

The goal of sprint retrospective is improving the development process. The Scrum team reflects on the previous sprint and discusses what’s working well, what could be improved, and how they could improve it to be more productive.

Although these improvements may be implemented even during the sprint, sprint retrospective gives the Scrum team a formal opportunity to discuss the process and motivates each team member to voice their opinion and ideas. 

Sprint Retrospective Agenda

For a successful sprint retrospective meeting, each team member should try to answer the following sprint retrospective questions:

  1. What went well during the sprint?
  2. Is there anything that can be improved?
  3. How can we make those improvements?

Instead of using the sprint retrospective as an opportunity for complaints, this meeting should be constructive with everyone on the team making an effort to improve the process and create an enjoyable work experience for the whole team. 

Share This Guide With Your Friends
Build Groundbreaking Products With This Framework
Fast-track your product creation process
Keep your teams always in-sync
Improve time management and work effectiveness