Retros are a very team-specific process. A retro that works great for one team might not work so well for another, so make sure to tailor your retro to your team’s dynamics and needs 🙂

We run our retros using a tool called Retrium.

We find it works great for managing our time and coordinating the session.

Our planning retros use 4 questions to facilitate discussion:

• What went well in the last planning cycle + demo week?
• What were our biggest obstacles in achieving our goals?
• Do you think we should run a 6-week planning cycle + demo week again?
• What should we do differently next time?

We add tickets to the board before the meeting, then spend the meeting discussing them.

Everyone blocks out 30 minutes in their calendar in the 2 days before the retro to add tickets to the Retrium board.

Then, we spend the retro meeting voting and discussing the tickets raised on the board.

We write up actions and add them to our internal work board in GitHub.

And that’s it! 😊