Tips for a Successful Retrospective
At the conclusion of the meeting, the Scrum Master should review the takeaways and action items and discuss the schedule for starting the next sprint. This final step ensures the entire team stays on the same page before everyone walks away from the event.
Within 24-hours, the Scrum Master should compile the notes and post or distribute for the entire team, including the Product Owner, to review.
Moving into the Next Sprint
The learnings from the Sprint Retrospective will be incorporated into the next sprint, so it is imperative that the notes be finalized and distributed prior to the start of the new sprint. At the kick-off meeting for the sprint, the Scrum Master should review the items for improvement that were identified and explain how they will be addressed in this sprint.
While the Sprint Retrospective marks the conclusion of the sprint, it is one of the most critical elements as it defines the behaviour for the coming sprint. Without it, the team would never improve and would miss out on the opportunity of becoming a stronger unit.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: