22 Types of Ideas for Sprint Retrospective Formats

Ruth Hadari
Ruth Hadari
Agile Advocate, Engineering Ops Expert
Posted on
Jun 11, 2020
Updated on
Apr 3, 2023
Table of Content

Sprint retrospective meetings can be held following all kind of formats. Let’s look at the different sprint retrospective ideas and types and talk a little about each.

3 Columns Retrospective Formats

Start-Stop-Continue Sprint Retrospective

The Start-Stop-Continue template is oriented around action and encourages team members to collaborate and come up with ideas for team improvement. The structure of these scrum meetings is broken up into three parts:

  • Start: What they should start doing in next sprint
  • Stop: Stop doing
  • Continue: What they should continue doing

What Went Well Retrospective

The format of the what went well retrospective focuses on the team’s strengths and weaknesses and can be used to figure out a plan of action according to what works and what doesn’t. Two posters are put up and each team member writes down things that went well and didn’t go well and they are then put onto the coordinating poster. The team discusses each one.

Mad-Sad-Glad Retrospective

The Mad Sad Glad retrospective encourages team members to look at their emotional journey throughout the previous sprint. It is a great way to focus on the perspective of the development team as a whole.

The Mad-Sad-Glad Retrospective is broken up into:

  • Mad: Things that they did not agree with or made them upset
  • Sad: Things that have disappointed them or things that they wish they could change
  • Glad: Everything that made them happy
mad sad glad retrospective infographic

Three Little Pigs Retrospective

The Three Little Pigs Retrospective takes a queue from the story we've all grown up with :) It is a cool way to gain team insight covering instability, lack of solidity, and what is truly solid...like the different houses in the tale.

Lean Coffee Retrospective

The Lean Coffee format is structured but does not include an agenda because the members of the meeting build an agenda at the beginning. This is a good way to do things because it ensures everyone is on the same page and that all topics that team members want to cover will be covered. Team members come up with ideas about the topics they want to cover, vote (perhaps using a dot vote) on the priority of the topics, and then discuss.

lean coffee retrospective infographic

Movie Critic Retrospective

The Movie Critic Retrospective helps teams use metaphors and playful movie critiques to discuss the more complicated and frustrating aspects of their previous sprint. The format encourages teams to explore their more abstract feelings, while making practical suggestions and decisions for the next sprint in tandem.

Good, Bad and Ugly Retrospective

The Good, Bad and Ugly Retrospective highlights key opportunities for change and improvements for a team going into their next sprint. The retrospective is broken into:

  • Good: Things that went well
  • Bad: Things that didn't work well/work as planned
  • Ugly: Things that made this retrospective stand out

Rose, Bud, Thorn Retrospective

The Rose, Bud, Thorn Retrospective looks to acknowledge the strengths and weaknesses of the project just gone so to determine how to be successful moving forward for the next project. The retro is split into three parts:

  • Rose: Highlights positives from the project
  • Bud: Identifies ideas that are still developing
  • Thorn: Highlights negative aspects from the project

Once each member has given their thoughts for each section, the group engages in discussion to reach a consensus on which ideas they would most like to pursue.

rose bud thorn retrospective infographic

Post-Mortem Retrospective

The Post-Mortem Retrospective allows team members to discuss what happened in the last sprint, why it happened, and how to improve.

The Post-Mortem retrospective is structures around these points:

  • What happened: A summary of the incident that occurred.
  • Why it happened: A root cause analysis of the incident.
  • How to improve: A discussion of steps that can be taken to prevent similar incidents from happening in the future.

4 Columns Retrospective Formats

Sailboat Sprint Retrospective

The Sailboat retrospective format is a simple and creative retro. A sailboat is drawn with its sails, its anchor, some rocks, some clouds, and a few islands. The anchor is everything that slows the team down or holds them back. The clouds and wind represent everything that is helping them move forward. The islands represent future goals and visions. The rocks represent risks they might have to take to reach those island goals. It is a nice, visual way to break things down.

DAKI Sprint Retrospective

The DAKI Retrospective is designed to help the team reflect on the last sprint, get on the same page, and re-focus all on the goal/s. The DAKI format helps see the different team members' perspectives on various behaviors, patterns, and activities they handle.

The talking points for a DAKI retrospective are:

  • Dropped: What isn’t working well
  • Added: What new ideas and innovative action plans could help address cnay needs/changes
  • Kept: Things that are working well and should be kept during the course of the project
  • Improve: Things that are already being done but can be tweaked to increase productivity

4Ls Agile Retrospective

The 4Ls retrospective format is a space for the team to have the opportunity to share their thoughts about the last sprint from each of the 4L categories. The categories are as follow:

  • Liked: All the positives about the last sprint
  • Learned: What new things were learned over the last sprint
  • Lacked: What could have been done better
  • Longed for: What things did the team want during the previous sprint which weren’t available

Iteration Agile Retrospective

The Iteration retrospective format involves reviewing the past sprint both quantitatively and qualitatively. By looking at both things, the team is able to decide what worked and what didn’t, as well as come up with realistic goals and actions for the next sprint.

Good, Bad, Ideas, Action Retrospective Format

The Good, Bad, Ideas, Action Sprint Retrospective is an easy way to go over the previous sprint and what went well (or hasn't) as well as come up with real ideas and actions to be used in the following sprint.
This retrospective format is also known by the name "Quick Retrospective" since it's a way to quickly dive in and gain insights on the previous sprint, covering: what was good, what was bad, ideas forward, and actions needed.
It's a simple and straightforward way to ease your team into running sprint scrum retrospectives...and hopefully for it to become a team habit.

KALM Retrospective Format

The KALM Sprint Retrospective Format is used to moderate conversations between dev team members or what is being done and its actual value overall; are goals being achieved? The team covers the following categories:

  • Keep: Things that the team recognizes as value-add
  • Add: What could help the team accomplish their goals
  • Less: What held the team back during the last sprint
  • More: What are the team already doing, that they could be doing more of

Wedding Retrospective

The Wedding Retrospective is an expansion of the What Went Well Retrospective, the key difference being that this format has a section for bringing in outside ideas to the retrospective. The retrospective uses four columns:

  • Something Old: Thoughts on existing practices within the group
  • Something New: Opinions on newly implemented strategies
  • Something Borrowed: Ideas from team members on how to improve
  • Something Blue: The areas of frustration/sadness from within the last project

All-Hands Meeting

The All-Hands Meeting template is a great tool for keeping members of an organization up-to-date and aligned on key updates, announcements, and goals. To effectively organize and facilitate these meetings, an all-hands template is a useful tool. This template ensures that all relevant topics are covered, and important information is shared with the organization during the meeting.

The All-Hands meeting uses theses for columns:

  • Agenda: A list of topics that will be discussed in the meeting.
  • Updates: A summary of any important updates or announcements that need to be shared with the organization.
  • Goals: A summary of any important goals or objectives that the organization is working towards.
  • Q&A: A time for team members to ask any questions they may have.

Quarterly Retrospective

The Quarterly Retrospective is an effective method for helping teams reflect on their progress, identify areas for improvement, and plan for the future.

The Quarterly retrospective is composed of the following points:

  • Lesson learned: What did the team learn over the past quarter
  • Achievements: What did the team achieve over the past quarter
  • Feedback: A space to provide feedback about performance over the past quarter
  • Ideas for next quarter: What ideas could improve the team's performance in the next quarter

OKR Retrospective

The OKR Retrospective helps team members to discuss all relevant topics during the meeting and capture important information related to the goals and objectives.

The OKR retrospective is made up of the following ideas:

  • Goal performance: How is the team progressing towards achieving the current OKRs.
  • Blockers: Are there any obstacles or blockers that are preventing the team from achieving the current OKRs.
  • Learnings: What lessons were learned while working towards the current OKRs.
  • Next steps: What are the next steps required for the team to achieve the current OKRs.

5 (or more) Columns Retrospective Formats

Oscar Academy Awards Retro Format

Oscar Academy Awards agile retrospective is exactly what it sounds like. Team members are nominated for different awards such as communication, leadership, etc. Also, stories are nominated and voted on for best story, worst story, etc. This is a good way to motivate the team to keep doing a great job.

Starfish Retrospective Format

The Starfish Retrospective helps reflect on the previous sprint with structured categories to be discussed and covered.

The Starfish retrospective consists of the following talking points:

  • Keep: What should be included in the next sprint
  • Stop: What's not adding value to the team
  • Start: What new ideas could help the team become more efficient
  • Less: What would be good, but at a lesser scale
  • More: What could the team do more of, or more often
starfish retrospective infographic

Choosing the right format for your team is important. In the next article, we will talk about how to choose the retrospective format that is perfect for you and your team.

Pacman Retrospective

Inspired from the Pacman video game, the Pacman Retrospective asks team members a wide variety of questions on the sprint just gone. The retro is divided into: The Pacman (What did we do well?), The Ghosts (What problems confronted us), Energy Pellets (What should we do more of?), Remaining Lives (What would we do differently next time?), Fruits (What was a pleasant surprise during the project?), High Score (What's our next exciting short-term goal?)

Final Thoughts

GoRetro streamlines and simplifies the sprint retrospective process, enhancing team collaboration across multiple projects via various boards. It offers the effortless creation of boards, comment threads, and easy sorting and filtering of cards and comments for efficient team discussions.

GoRetro also offers a voting system, which assists with decision-making and identifies actionable items. GoRetro is an ideal solution for productive and collaborative scrum meetings that work equally well for remote and on-site teams.

Frequently Asked Questions

What is a Sprint Retrospective?

The Retrospective solution, also known as retro, is a chance for your scrum team to take a look at itself and its operations and create a plan of action to be put into place during the next Sprint.

The retro step occurs in between the Sprint Review and Agile Sprint planning, so your team is able to fully understand their progress and see what needs to be changed or fixed in order to continue progressing effectively, efficiently, and overall build software better as a team.

What Happens During the Sprint Retrospective Process?

During this process, the scrum team will sit down and have an internal look into their proceedings and techniques. They will discuss things like:

  • What went well during the Sprint
  • What, if anything, could be improved
  • What will be committed to attend, change, focus on for the next Sprint

During each of these Sprint Retrospective meetings, the team decides what has gone well and what needs to be improved in order to increase productivity and quality of the product they are producing.

How can a Sprint Retrospective Meeting Benefit my Team?

The biggest benefit of a Sprint Retrospective meeting is that the team has an opportunity to sit down at a scheduled time and reflect on past events, choices, procedures, and behaviors that have occurred throughout the past Sprint. They can look at how these things have affected their growth and productivity. This gives the scrum team the opportunity to change things that need to be changed or reinforce things that are working well.

It also gives the opportunity for successes and positive actions to be reinforced and celebrated. This keeps morale up and sets the bar for the next Sprint.

Sprint Retrospectives give teams the opportunity to celebrate their successes and work on a plan to better themselves for the future. It is very beneficial to all parties involved, individually, as well as the scrum team as a whole.

If your scrum team is looking for a way to continue to grow together and understand exactly how productive your techniques really are, then a Sprint Retrospective might be exactly what you are looking for.

About the author

Ruth Hadari
Agile Advocate, Engineering Ops Expert

Highly experienced in leading multi-organizational teams, groups, in-shore as well as off-shore. The go-to person who is able to simplify the complex. An agile advocate, experienced in all common methodologies. Responsible for the entire software development lifecycle process from development, QA, DevOps, Automation to delivery including overall planning, direction, coordination, execution, implementation, control and completion. Drives execution, and communicates on status, risks, metrics, risk-mitigation and processes across R&D.

Related Posts

Contact Us
Thank you! Your message has been sent!
Oops! Something went wrong while submitting the form.

Join thousands of companies

Start for free - update any time
Joining as an organisation? Contact sales