8 Good Reasons for Retrospectives

Retrospectives are an agile method that, in software, is typically run at the end of a sprint.

They're about reflecting on how a team worked together, and essentially come down to these questions:

• What did we do well?
• What could we have done better?
• What did we learn?
• Where are the problems?

But isn't that just something for agile software teams? Why should we bother?

Retrospectives help every team move forward. Here's a whole list of good reasons why:

1. You get systematically better. Through targeted questions and by deriving tasks or actions from the topics you identify, you can use the retro to become better going forward.
2. You spot and work through problems together. Something feels off right now? Retrospectives can surface difficult, hidden problems too. The targeted questions of your chosen method give you a way to put these things on the table. The retro creates a protected space, and everyone knows: conflicts can be worked through here without anything having to escalate. By talking about it together, you find solutions together too.
3. You have a defined framework, a routine in everyday work. The ritual of a retro, and the regularity that comes with it, brings a team closer together and creates proximity even in a remote setting.
4. Everyone gets a say. Whether your team members tend to be loud or reserved, retrospectives are there for everyone on the team, making them a platform for balanced exchange.
5. Retrospectives answer the focus question. Sometimes you need to let go of unnecessary baggage. The questions in a retrospective make that possible. An action like that is incredibly valuable, sharpens focus, and motivates.
6. You strengthen team cohesion. A retro is also where successes and positive moments from the period get shared. Appreciation and gratitude are always welcome, and they're a boost for team cohesion.
7. You have fun together, even remotely. Retrospectives can even be funny. Have you ever tried acting out your superpowers in mime? The laughs are guaranteed.
8. Actively reflecting strengthens your feedback culture. By practicing reflection, deriving actions, and building more trust, giving open feedback keeps getting easier.

So How Do You Actually Do This?

There are countless retro formats, and it's worth trying something new again and again. The options range from a simple weather report (sunny to stormy, depending on mood) to full workshops with questions built around a specific topic.

Don't forget: a retrospective without derived tasks or actions unfortunately doesn't get you anywhere. As we describe in our article on why a learning that changes nothing isn't a learning: you can capture the results of your retro directly in Rocket Routine, for example, link them to your goals, or anchor them as a new principle.

Now have fun trying it out!