Which retrospective template is best for your needs and team engagement?
We’re already aware of how retrospectives assist scrum and agile development teams to improve, collaborate, and progress productively from sprint to sprint.
But which retrospective template is best for your needs and team engagement?
Below is a list of retrospective formats available for your use as pre-built retro templates, so you can get started instantly and gain value as quickly as possible. Select any retro type to learn more about it or get started for free (no limit) and select the retro board of your choice.
The start-stop-continue retrospective
template works well for developing action plans, reviewing the previous sprint, and assessing product results. In short it asks:
The remote sprint retrospective
is a great retrospective solution for remote teams to run a retro together and improve as a team even while working remotely and not within the same space.
The mad sad glad retrospective
template focuses on how the team felt through the previous sprint. Teams analyze which techniques assisted them and should continue, as well as develop concrete directions to progress positively.
The lean coffee retrospective format
hopes to gain valuable insights from the team through open-ended questions and discussions covered by the team itself. With it, the team focuses their time and attention on certain topics of interest.
The sailboat retrospective
looks at the big picture by covering the variety of aspects of a project, allowing the team to provide insights on what helped, slowing them down, and developing an action plan to move forward.
The 4Ls retrospective template
is great for breaking down the previous sprint and projects worked on to look deeper at what was learned, what the team was lacking, and what they would like to see in the future.
The Oscar Academy Awards retrospective
template can help motivate your team by giving due credit to team members for the various areas they shined in during the previous sprint.
The iteration retrospective
is a reflective format to look back on the previous iteration, where your team focuses on qualitative and quantitative reviews to help paint a bigger picture and assess goals and techniques.
The ‘what went well’ retrospective
format is one of the easiest and most efficient methods for your agile team to complete their sprint retrospectives. This retrospective template opens discussions on what went well during the previous sprint, as well as what didn’t go well (or as planned). Post discussion, team members decide upon specific action items to improve future engagement and sprint results.
The starfish retrospective
format helps by generating data from team members to reflect on the previous sprint and understand what worked well, and what is to be improved. Its structure is like a Starfish, covering the following categories:
The three little pigs retrospective
is a fun format with a call-back to the old story of the 3 little pigs, and their three houses made of straw, wood, and brick. It allows team members to discuss the previous sprint and assess:
What was unstable (Straw house)
What improved yet lacked solidity (Wooden house)
What was solid (Brick-made house)
The DAKI retrospective
format aims to reflect on the previous sprint, named per the abbreviation of DAKI to provide the talking points/categories:
The KALM retrospective
template is used to open up a discussion among dev team members and hopefully keep you calm while at it. Its abbreviation introduces the areas up for discussion among all participants:
While the name SWOT retrospective
may suggest a marketing/sales analysis, it is extremely useful as a retrospective format to look at the previous sprint and discuss the following:
What is a retrospective template?
Retrospective templates are used to structure positive and negative feedback after a project is completed or a working sprint is completed. During retrospectives, teams reflect on their ways of working and continuously improve their production by examining current problems and goals, brainstorming new ideas, and identifying what actions are required to make progress.
What is it good for?
Sprint retrospectives are a great way for your team to reflect on the previous sprint or milestone, the work that was done, the goals achieved, and to generate ideas for improvements. A good rule of thumb is to switch up the format every now and then – repeating the same agenda is tedious after a while. The use of different retrospective templates keeps meetings engaging and fun and allows team members to provide their own reflections.
How do GoRetro's templates work?
When creating a new retrospective board in GoRetro, you get to choose a template out of various popular retrospective templates. Once you choose a predefined template your board will be created with the template’s number of columns and respective names. You can then update the column titles, add more columns, remove and even change styling to adjust the template to your team’s flavor.
Can I create a custom retrospective template?
Yes you can! GoRetro's simple and flexible boards can be customized to fit your team's needs. When creating a board in GoRetro, you can either choose a predefined template, or choose a “Custom Columns” option.
To use your own template from scratch:
1. Choose one of the “Custom Columns” options and click “Create”. Your board will be created with the number of columns you chose, each column will be named “Column 1”, “Column 2” and so on.
2. Click on the column’s default name to rename it according to your desire.
3. If you need more columns for your custom template, click on the “New Column”
To customize a predefined templates :
1. Choose one of the predefined templates and click “Create”. Your board will be created with the template’s number of columns and respective names.
2. You can then update the columns’ title, add more columns, remove and even change styling to adjust the template to your team’s flavor.
For all board customization options, check out our how to videos.
Suggest your own retro template
Do you know or use another retrospective format which you found has been very effective for your dev team and process? Please share with us, and GoRetro may end up creating a new retrospective template to help others.