Watch a tutorial on how to use this template.
Running an effective sprint or project retrospective involves your whole team reflecting on what went well and didn’t go well during the current sprint. Learnings from the retrospective can be applied to the next sprint and future sprints. This template is an easy-to-use template for running an effective retrospective since all the key elements of the retrospective are right there in the doc. If your team utilizes scrum and agile methodologies for project management, this template is for you.
The retrospective is a type of meeting held right after a sprint or a major stage of your current project. This meeting is really effective at helping your team maintaining a tight feedback loop on what is going well and not going well so that the team can improve for the next sprint or phase of the project. During this meeting, all team members reflect on activities during the current sprint or project phase.
During the retrospective meeting, your team should discuss internal processes that could be improved to make the team more agile. Examples of questions that typically come up during a retrospective:
This template allows you and your team to answer these questions and more by providing a standard way of running sprint and project retrospectives.
In the template, anyone on your team can add their “highs” and “lows” to doc so that everyone’s feedback is transparent. If you are running the retrospective, you can aggregate and summarize everyone’s highs and lows under the “Themes” header in the template. This makes it easy to reference the key themes in the future from the retrospective if you ever need to revisit your notes in this doc.
After getting everyone’s highs and lows, your team should start thinking about how the team should operate in the future. By clicking the “Add Your Feedback” button, team members can log activities that they think the team should start doing, continue doing, and stop doing. After team members have entered in their feedback, have each team member read off their feedback which may spark more areas of feedback from other team members. This portion of the template provides a good direction for where the team should move next to be more effective at building and launching products.
Sometimes retrospectives don’t have any effect after the meeting is over because there are no action items assigned to team members. During the previous step, as team members log their feedback, there is a button that allows the team leader to turn the feedback into an action item (this gets added to the “Action Items” portion of the doc).
Now that there is a list of action items that have resulted from the feedback, you can go ahead and assign someone to each action item to follow up on after the retrospective. This creates more accountability within the team and more importantly, takes the feedback and ideas discussed during the retrospective and turns them into real change within the team. Check out this page for other templates related to meetings.
Product evangelist and solutions architect. Love building solutions to solve our users’ business problems!