A sprint retrospective is a core ceremony in Scrum, at which the team discusses three aspects of the completed sprint: what went well, what needs to be continued, and what needs to be stopped. The retrospective is "owned" by the ScrumMaster.
How do we make the retrospective engaging, interesting, and motivational for Scrum team members, so that they actively contribute? Here are some suggestions:
- Previous retrospective action items – These either should have been completed or should be being worked on with sufficient progress, per the committed plans. This will give confidence to the Scrum team to move ahead with new retrospective action items.
- In fact, have the retrospective action items from previous sprints always available to the team to look at. People should be able to see how they're being updated. This could be done on a wiki if the team is distributed.
- Recognition – Start with recognitions from team members for the support they received from others on the team. This could be done as a "round table" exercise, in which each team member has one or two minutes to speak.
- Recognition for what was done – The team deserves recognition for its achievements in the previous sprint.
- Feedback – Every team member should get the opportunity to talk about the three key points (what went well, what to continue, and what to stop doing) in a timeboxed manner.
Consider various models for getting good input during retrospectives.
- Ask team members to give input on the happiness index (how happy are you to be part of your Scrum team, on a scale of 1 to 5 ). This could trigger open-ended questions about actions required to improve the happiness index and team engagement.
- Have a discussion based on the sprint timeline so the team remembers all the things that happened during the sprint.
- Gather retrospective input or discussion points throughout the sprint. This could be also be done on a wiki if the team is distributed.
I look forward to your further suggestions and experiences with improving retrospectives.