Retrospectives are fundamental events not only in Scrum but also in various Agile frameworks as formal meetings to inspect and adapt the way and environment Agile teams work. There are plenty of interesting and attractive methods applied to determine the structure of retrospective meetings in real practices. So in this post, some of them are gathered and simply introduced.
Colouring a blob person image to depict how the sprint went. Details of Blob Football can be found in The Blob Retro.
Choosing a specific car brand to depict how the sprint went and then choosing your dream car. Details can be found in The Car Brand Retrospective.
DAKI helps the team identify specific features, behaviours or activities that the team members think they should Drop, Add, Keep or Improve. Details can be found in DAKI – Agile Retrospectives Exercise.
Using various emojis to gauge how the team feels during the Sprint. Details can be found in Emoji Retrospectives 😃.
Fast & Furious
Classifying the events each member performed during the Sprint into five categories and determining the emerged improvements. Details can be found in Retrospective #5: Fast and Furious.
Finding pictures of pirate Jack Sparrow online and using his various faces to gauge how the sprint went. Details can be found in Guest blog: Many Faces of Jack Sparrow – Agile Retrospective Exercise.
Using Kudo Cards to help deliver feedback and motivate people. Details can be found in Retrospective with Kudo Cards.
Having team members build something to represent how the sprint went. Details can be found in Agile Retrospectives with Legos.
Visualising and analogising each perspective to help the team identify the conditions they met during the sprint and discuss the solutions mutually. Details can be found in The Sail Boat Retrospective.
Using a weather metaphor to shift focus from simply looking back, to how the team expect things will go based on how things have played out so far. Details can be found in Predicting The Weather: A Weather Forecast Retrospective for Scrum Teams.
making a pie chart divided into 5 parts which looks like a starfish with a section for “start doing”, “stop doing”, “less of”, “more of”, and “keep doing”. Details can be found in Starfish retrospective and Starfish Retrospective Technique.
Saying “Thank you” to other members via a “Thank You” certificate. Details can be found in The Thank You Retrospective.
An action-oriented retrospective style, generating an immediate list of practical ideas for continuous improvement. Details can be found in Sprint Retrospective Techniques.
Evaluating how happy the team is about the different Scrum elements (roles, events, artifacts, principles, values, etc.). Details can be found in 40 ideas to spice up your retrospective
A great data gathering activity for recurring retrospectives. The Ls stand for: liked, learned, lacked, and longed for. Details can be found in 4 Ls: Liked – Learned – Lacked – Longed For.