Adopting Scrum introduces several new meetings. Suppose your team is trying to work more efficiently. In that case, it’s understandable to be wary of extra appointments.
I’ve seen leaders be tempted not to do the retrospective or reduce it to every other sprint. That is a mistake.
The retrospective is an essential part of practicing Scrum. If you’re a new Scrum Master or part of a team newly adopting Scrum, this article will show you the value of a retrospective and how to practice it well.
The retrospective occurs at the end of the sprint, and I like scheduling it right after the sprint review. Together the scrum team (product owner, scrum master, and development team) focuses on self-improvement. The tone is positive and productive, focused on improving the team.
Let’s take a deeper look at the Scrum Retrospective.
The respective is an active meeting. To be successful, the whole team must fully engage, and it requires honesty, vulnerability and trust. But when done well, the retro also grows and strengthens these same qualities in the Scrum team.
The product owner, scrum master, and development team are all present for the retrospective. The scrum master may facilitate everyone to learn the process for the first few times. But once the team understands how the retro works, everyone comes to it with shared responsibility for it to be effective and fruitful.
Each Scrum team member should be a full participant, bringing observations and feedback. The whole team also owns the future by working together to identify and plan a solution.
Here are a few examples of changes and how different roles on the team help bring it to fruition.
The Scrum essentials of visibility, evaluation, and adaption in the retro are also present in the daily Scrum. By practicing this each day, the team increases the competence and confidence needed to grow together as a team effectively.
Scrum has a lot of meetings and it can be hard to keep them straight, especially when you're getting started.
The Scrum meeting checklist has all the details you need to run effective Scrum meetings.