Skip to content
How To Run A Sprint Retrospective Meeting [+Template]
Share
Explore

3 Tips To Run A Sprint Retrospective Meeting [+Template]

Run a project or sprint retrospective with this template that includes action items for your team to follow up on.
Run a project or sprint retrospective with this template that includes action items for your team to follow up on.

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 sprint retrospective template is designed for scrum masters or agile teams to run effective retrospectives since all the key elements are right there in the doc.

What is a sprint retrospective meeting template?
The sprint retrospective meeting is a recurring sprint review meeting held at the end of each sprint. The sprint retrospective aims to analyze and identify what went well and what didn't go well to improve upcoming sprints. Sprint retrospectives are a key part of the scrum framework to encourage frequent communication and iteration during ongoing workflows.

The sprint retrospective meeting template helps track the topics discussed during the scrum retrospective and to encourages continuous improvement.

3 Key Steps to Run a Successful Sprint Retrospective Meeting
Running a successful sprint retrospective meeting involves getting all the right attendees in the room and getting them to reflect and brainstorm on the previous sprint. The goal is to learn to collaborate as a team to improve the next sprint.

1. Talk about team highs and lows
In the template, anyone on your team can add their “highs” and “lows” to make everyone’s feedback 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.

2. Start, stop, and continue doing
After getting everyone’s highs and lows, your team should start thinking about how the team should operate in the future based on the last sprint. 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, the facilitator should have each team member read their feedback which may spark conversation from other team members. This opens up an avenue for open communication that is key to teamwork. This portion of the template provides a good direction for the team to build and launch products more effectively.

3. Discuss and create action items
Sometimes retrospectives don’t have any effect after the meeting is over because there are no action items assigned to team members. This is why we have included a button in the template that converts feedback into actionable steps, which gets added to the 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 for other templates related to meetings.

You can easily keep track of ideas or feedback that don't make it to the next sprint in the sprint backlog. If done consistently, the sprint retrospective meeting can really level up project management and teamwork in the future.

How to use this sprint retrospective meeting template
Before the next sprint, the scrum team should reflect on activities during the current sprint or project phase and put their thoughts in the template. If you click on the page of this template, you'll see a breakdown of what type of topics and questions to bring up during the sprint retrospective meeting. Here's how to get started:

Step 1: Identify the team and context
You can uncollapse the "Team" header and start writing people's names from the scrum team. You can @ mention the person when writing their name. The context can contain the goal of the sprint and any other facts that help team members get background information on the sprint.

Step 2: Have team members write their highs and lows
After sharing this template with your team, each person should brainstorm on the high and low points they felt during the sprint. This template is great for remote teams because anyone can click the Add Your Highs/Lows button and log their sentiments.

Step 3: Decide on actions to start, stop, and continue
After logging highs and lows, team members can enter actions that they think the scrum team should start, stop, and continue. As people enter their thoughts in real-time, the product owner or scrum master can start a discussion on the different actions team members want to start, stop, and continue. For any actions that should be turned into an action item, you can click the Turn to AI button which adds that action to the table.

Step 4: Summarize into themes
The methodology you use to summarize the meeting into themes is up to you. The goal is to go back to the Themes section of the template and write the key takeaways from the meeting. This way, other team members who didn't attend the meeting can get a summary of this agile retrospective meeting.

Remember, this is an opportunity for the entire team to discuss process improvements and share retrospective ideas. These ideas can be carried over to the next sprint planning meeting to help the team build more agile workflows. Examples of questions that typically come up during a retrospective:
How can we make our daily scrum or standup meetings more effective?
Do we need to revisit any of our standard operating procedures?
Are we communicating enough with our stakeholders?
Is the rest of the company aligned with our efforts?
This agile retrospective template allows you and your team to answer these questions providing a standard way of running sprint and project retrospectives.

👉 Get started with: sprint retrospective meeting template
Copy Doc
on how to use this template.


Sprint retrospective meeting FAQs
What do you discuss in a retrospective meeting?
It is crucial to look back at the end of each sprint and what happened during the previous sprint or project, discuss what areas needed improvement and celebrate positive moments. By regularly having this meeting, the next iteration of the project or sprint will be better. The retrospective meeting is a forum to discuss how to improve for the next project or sprint.

Who should attend a retrospective meeting?
The scrum master, the product owner, the software development team, and anyone else who participated in the project or sprint attend the retrospective meeting. You may want to limit the attendees to go through all the feedback in a timely manner. Additionally, the more focused the group, the more focused the areas of improvement and action items will be.

How long should a sprint retrospective meeting be?
For a sprint that lasts 1-2 weeks, the sprint retrospective meeting should be 60-90 minutes long. Many variables impact the length of the meeting, such as the number of people attending the meeting and the current meeting load for your team members. The longer the sprint, the longer the sprint retrospective meeting should be.





👉 Get started with:

A few of the 25,000+ teams that 🏃‍♀️ on Coda.
a77eed08d9f915aabec0346b67a40b7ec93457a9864e51bde1e9239fad175c59624ad1bd252ec5041198bc8e9a52ce31b441ab4767fbb714b9172474278d0b29434f118c46abc5c7a7377f4ad1ea733677ca74d97bc8661e4bbfde8d9cdafabc285f5616.jpeg
Coda is an all-in-one doc for your team’s unique processes — the rituals that help you succeed. Teams that use Coda get rid of hundreds of documents, spreadsheets, and even bespoke apps, to work quickly and clearly in one place. This template is a Coda doc. Click around to explore.

Find out how to Coda-fy your rituals.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.