Today I bring you the second part dedicated to the format of the retrospective. Retrospective helps (not only) project managers get information from the team and move it forward. This time we will look at retrospective formats that are suitable for teams that may not work as intended.
In previous articles, we imagined what scrum retrospective is, anti-patterns and retrospective formats for well-cooperating teams, which are among the relatively traditional techniques for making a meeting. Today let’s look at less traditional methodologies.
The following types of retrospectives are especially for teams where we feel some obstacles, but we may not know where they are. Alternatively, it's for members which feel that it harder for them to talk about problems.
This type of retrospective simply visualizes "ups and downs" thanks to a parallel with the hills and valleys and a clearly marked timeline. It is a very suitable technique for larger groups of people and more ideas that are not lost, but are clearly visible. This activity could also prove successful for teams that we want encourage to greater openness or conversations, and we can also incorporate a "how I felt" scale into it.
This is a retrospective format used mainly for team members to get to know each other first. The goal is to create an environment where individuals feel comfortable giving personal feedback to others they may not have even met in person. It is a technique taken from "speed dating". It is an ideal format for personal retrospectives, but we can also modify it for remote teams
Create a small, inner circle and a large, outer circle. Each one gives feedback to the other, so you need to make sure that you choose the right strategy. Set the timer to, for example, 1 minute per person
In this retrospective, we try to improve the process by analyzing individual parts (ie stories). We can use User Stories straight from Jira here, but we can also replace the second word "story" with anything that fits us in context, such as Story of a (... project, team, order, bug ..). At the same time focus only one item, which pushes the team to be concrete and focus on the specific thing we want to solve.
The following retrospectives visualize the problems and focus directly on them, or they are looking for a way out of them. They are designed so that the team can better identify and realize that even though we are facing a problem, there is room to solve it.
This kind of retrospective is more of a forward-thinking exercise that shows risks. We use it when we need to look around but also point out what awaits us.
This retrospective shows the sprint and the project as a situation similar to a long mountain hike / rock climbing. There are obstacles and risks. Just as when climbing, there are risks that can slow down the group when moving to the top of the mountain, so it in sprint.
This kind of retrospective deals directly with the problem. It is used in teams where we know the problems they face and want to talk about solutions. This activity is very effective in situations where we want to literally save the project.
This retrospective helps the team identify errors, understand their nature and have a productive conversation about them. This is especially useful for teams that are struggling with many issues over a period of time. There are two possible types of decision errors: Error of Commission and Error of Ommission.
This type of retrospective is based on the FMEA principle, a tool used for systematic problem analysis and remedy identification. However, it can be a challenging activity where we focus on only one specific problem / failure and what the team should do to manage these consequences, work on corrective actions and verify their outcome.
Analysis: What is our failure / problem / error? What led to this?
Evaluation: What are the consequences of this failure? What is the severity? What is the probability that this will happen again
Action: What are the corrective and preventive measures (so that it does not happen again)
Verification: How can we verify their result with regard to the mentioned actions?