The new year has just started, and it’s time for the next steps to rile your teammates. So let’s have a look at one of the activities in Scrum that can be easily sabotaged: the retrospective. Here are ten proofed ways to wreck any retrospective:
- Keep the retrospective as short as possible. No need to invest too much time in this meaningless gathering.
- Only focus on negative events and ignore any positive things. This is the only valid path to improvement.
- Handle a retrospective as any other meeting. Sit around a table and just talk.
- Ignore the complexity of the system around you. There is always a cause and effect.
- Always use crappy material such as cheap post-its that quickly fall from the walls or old pens that hardly write.
- Forgo a facilitator for your retrospectives. It is only a burden and will slow the whole “meeting” down.
- Don’t use any agenda and deliberately ignore the retrospective’s phase model.
- Directly start with defining what has to be changed in the next sprint. Everybody already knows what has to be done.
- Never check if the defined tasks of the last retrospectives were done or even had the desired effect.
- Never bring food to your retrospectives. Hungry participants will do anything to finish a retrospective as fast as possible.
What else could you do? I’m looking forward to your suggestions in the comments.