The best Retrospectives techniques avilable in Atlassian

We already talk about all the benefits that Agile retrospectives have for teamwork and how this important ceremony helps us to highlight the failures and the achievements that the team had during the past sprint. All of this inspection is with the purpose to take and to find new proposals and better options for continuous improvement.

There is a lot of ways that you could be having your retrospectives. Today we are going to show you 4 easy games to play retrospectives in our platform Agile Retrospectives for Jira or Confluence.

Collaborative games refer to several structured techniques inspired by gameplay but designed for a purpose beyond pure entertainment, typically to develop a better understanding of a problem or to inspire new ideas about solving a problem.

(source)

First of all, we need to organize the way the retrospective will be onboarded, all of this with the objective to avoid failing before start the retrospective.

  • Learning about history and environment:The team’s history, general assumptions about the current state, and team morale should be taken into account.
  • Retrospective goal: Express freely why this ceremony is important and what we expect to learn from this ceremony.
  • Duration of retrospective: sprint iteration length, complexity, team size and level of conflicts, and controversy.
  • Facilitator: Assign a person who manages activities, group dynamics, and time. You can select easily which member is going to be the current facilitator to ensure a better performance.
  • Activities (games): Now that you are starting your retrospective, it is important to determine which template or game you are going you choose. Your game should be selected based on the retrospective approach and participant list.
  • Data collection: Don’t worry about saving your info, with our tool agile retrospectives you can save all the report and check it every time you needed.
  • Agenda: Structure of your retrospective to be more effective. In this situation, it is only needed all the team is aware of the retrospective that could be asynchronous if works better for your team.

Retrospectives techniques (Source)

Retrospectives games

Speed boat.

This game could be your better option if you are looking for better results than the standard game. This game should not be used too often. Considering that risk, vision and mission are not very variable.

This game is to help the team to think about their impediments, risks, good practices, and where they want to go. In this game the principal scenario is about a speedboat with an anchor, this scenario is around rocks, wind, and an island.

Every object in the scenario represents something (a column): The island represents the team’s objectives/vision. The rocks represent the risks the team might encounter along the way. The anchor is everything that slows them down on their journey. The wind represents everything that helps them to reach their objectives. (Source)

4 L’s

This game overs perfectly all the important aspects that the Retrospective need. It is one of the best if you are trying to improve communications, learning, and involvement easily.

For this game you need to configure your template with 4 columns, each of one will say:

  • Liked: what the team appreciates about the sprint, things that the team likes during their past performance.
  • Learned: What things the team learns during this sprint.
  • Lacked: What could be better? What the team could do instead of the way they did it All the possible improvements the performances could need.
  • Loathed: The things that the team dislikes during the sprint.

You can add a new column and include “Longed for”

  • Longed for: The things that the team was expecting and never happened.
  • More: activities or practices that are useful but not fully taken advantage of; and the team believes that they will bring more value if are done even more. 4L  retrospectives technique

Mad/Sad/Glad

It is considered as one of the easier ones and it is perfect if you want to revise the team spirit and gather data about feelings during the Sprint. Also can be very helpful if you are trying to improve communication.

For this game you need 3 columns:

  • Mad: frustration and things that were annoying during the past performance. Maybe things that go bad or waste a lot of time.
  • Sad: disappointments, things that went wrong or not as planned
  • Glad: Pleasures. Things that made the team happy or things that went better than expected.

Mad sad glad retrospective

KALM or the typical retrospective questions.

This game will help the team to understand each other perceived value on the way they worked.

  • Keep: Things that have created value and the team should keep fostering.
  • Add: Activities that the team wants to bring to the team.
  • More: activities or practices that are useful but not fully taken advantage of; and the team believes that they will bring more value if are done even more.
  • Less: Things that could be bringing value but requires more effort than needed.

agile retro game

The standard way is just: Start, Stop, and Continue.

There is a lot of effective ways you could be doing your Retrospectives, find those templates based on your retrospectives needs. Try to change the technique anytime that you need, this will avoid that the team feels the ceremony repetitive and useless.

You even can make your retrospective of retrospectives in our tool configuring every column as you consider better, you can customize the colors and the votes. To ensure a follow-up you can assign tasks as Jira issues.

Discover more of our agile remote tools: