5

I'm going to be organizing the retro (Scrum) and I would like to get more experience on it. I have assisted to some and have organized some as well, but the format always seems to be

| What went wrong            | What worked
          ---                     ---
| What should continue doing | What should we stop doing

I will like to do something else or another format, but I'm not knowledgeable enough on the subject to know how to proceed.

TL;DR: I will like to get feedback from my team during a the retrospective in a way that it's fun, engaging and productive.

Improve this question
3
  • 1
    You can take a look at my Retrospectives Exercises Toolbox at benlinders.com/exercises/- it provides exercises, ideas, books, and tools to help you defining formats for your retrospectives.
    – BenLinders
    Commented May 18, 2019 at 14:10
  • 1
    I would strongly recommend "Agile Retrospectives" by Esther Derby and Diana Larsen.
    – Barnaby Golden
    Commented May 18, 2019 at 14:20
  • great resources from all. Thanks for the help. I would mark as "correct" @Jo Silverton's anwser cause that's the only one under "Answers" except if anyone has any objections ?
    – intercoder
    Commented May 21, 2019 at 11:14

2 Answers 2

Reset to default
2

There are a lot of different options for retrospectives depending on what you want to get out of them. The book Agile Retrospectives by Diana Larsen and Esther Darby is a great place to look.

I also highly recommend looking at Retromat for ideas.

As a final piece of advice, I would consider using the 5-stage retrospective talked about in both of those two resources. While it may feel a little over-structured and take a little longer, it ensures that the format of the retro is solidly geared towards valuable outcomes.

Improve this answer
1

The Spotify Squad Health Check model is quite interesting (here), and provides a list of topics that could be used as 'deep dives' if you wanted to vary the content of retrospectives, by focusing on a specific topic every now and then. We've used this to conduct a survey of all our technical staff on our existing projects, to find out areas that we should be concentrating on, and where the most painpoints lie.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.