Sprint Review vs. Retrospective
In this meeting, the team will identify the items that they felt worked well during the sprint, such as communication or task explanation. They will then identify the items that could have been improved and come up with solutions on how to improve them going forward.
The key elements of the Sprint Retrospective include:
The identified process improvements will be incorporated into the upcoming sprints. This ensures that the team is always improving and the process is becoming tighter and leaner.
The meeting should be structured into an open forum and remain a collaborative process in which all team members have a voice and participate. There are no right or wrong opinions and everyone’s thoughts should be heard.
The focus should be on how the team can improve the overall process and general productivity going in the future.
After the meeting, the Scrum Master’s priority will be to prioritize the lessons learned and takeaway actions and then disseminates the information to all attendees.
One of the key benefits of the Retrospective is that it will help to build the team’s sense of ownership and will empower them to make decisions and participate as they continue into the next sprint.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: