What is a Sprint Retrospective Meeting?
- A sprint retrospective meeting is part of the Agile method of project development.
- The sprint retrospective comes at the end of each sprint, the relatively short periods of development in each iteration of the project.
- The goal of the sprint retrospective is to provide a time during which the development team can look back at their performance during the sprint, assess how well they did, and identify ways that they can improve during the next sprint.
- We recommend that you add the below template to your Project Management Templates and specifically to the list of Agile Project Documents.
|Sprint Retrospective Meeting Template|
Sprint Retrospective Agenda
- The agenda of the sprint retrospective should address what went well during the sprint and what went wrong.
- If this is not the first sprint, the retrospective may begin with a discussion of the opportunities for improvement identified in the last retrospective, along with a discussion of whether or not those improvements were implemented successfully.
- During the meeting, team members should offer examples of processes that worked well during the sprint, with the recommendation that the team should continue doing these things.
- Team members should also honestly point out the processes that did not work, with the suggestion that the team discontinue or modify these processes going forward.
- Finally, team members should offer recommendations for new processes that the team should consider implementing.
- After the team has compiled a list of processes to continue, stop, or initiate, the ScrumMaster should facilitate the creation of a final list of recommendations, typically chosen by team members' votes, that the team will pursue in the next sprint.
- The aim, though, is to focus on the processes rather than the outcomes; the retrospective is meant to examine how the team functioned, not what it accomplished.
Making the Retrospective Effective
- Keep it short. Ideally, the retrospective meeting should not last more than an hour, and its discussions should remain tightly focused on team goals. If individual team members have concerns or issues that they wish to discuss with the ScrumMaster, those issues should be discussed in private afterward, not during the meeting.
- Engage the entire team. The ScrumMaster may facilitate the meeting, but it should be a group effort that encourages participation from all team members. No one person should drive the agenda or dominate the meeting, and each team member should feel safe in bringing up any issue that he or she feels is significant.
- Include only relevant discussion. The meeting should include discussion of topics and processes that are relevant to all members of the team, regardless of their roles or their individual expertise. Any discussions that are relevant only to particular team members should be conducted in private outside the retrospective meeting.
- Keep it actionable. The meeting should include discussion only of issues over which the team has control. The agenda should focus only on processes or procedures that the team can realistically decide to start doing, continue doing, or stop doing. The retrospective meeting is not the place for airing grievances or discussing processes that the team has no power to change.
- Ensure the learning's are included in the sprint planning meeting and agile project plans.
- Document and publish the findings or meeting minutes at the end so that there a record of findings.
After an effective sprint retrospective meeting, an agile team emerges with enthusiasm for the new ideas to be implemented in the upcoming sprint, and each team member has a clear understanding of his or her role going forward. When the meeting is conducted correctly, it results in a team that is more efficient, productive, and united.
Using the Retro Template
Detailed instructions on how to use each of the slides are below.
|Sprint Retrospective Agenda|
Summary of Sprint Activities
- Include high level description of the projects and which sprint this retro is about.
- At a high level explain what was the sprint about and how did we plan the sprint.
- Briefly describe Epics, Sprints or Story points delivered.
- Also, mention in a line or two how this Sprint was important to the project and what all reusable components were developed if any.
- A quick mention of the project team including the scrum master, product owner and the team.
What did we deliver in this Sprint
- The whole point of having a retro is that we can learn from our mistakes.
- This slide contains a list of items that were delivered from the sprint backlog.
- On this slide discuss the various lessons learnt and if any actions were discussed in the last sprint retro.
- Edit the burndown chart to enter your sprint details.
- Enter any observations that were made during the sprint examples unplanned leave, estimates way out, etc
What were the impediments that we faced
- List down the issues the team faced during the sprint,
- At the end open it for the team for feedback.
- It is very important that the team gets a chance to put forward their views and issues.
What went well and What can we do better
- Change the list as per your needs.
- It is important to go phase by phase so that team will remember what happened in those phases.
Lessons Learnt, Action Items and Closing Comments
- Add an items if you are already aware.
- This slide should contain a list of improvements and suggestions, also a good place to collect action items after the sprint is complete.
- Always open this section up for discussion so that the team can provide their feedback.