Blog | Books | About
Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!
Join 6000+ subscribers and get new activities & tips for retrospectives in your inbox!

Wondering what content you'll get? Look at past emails | Privacy Policy
Replaced by JS

Know your neighbour - Opening (#108)

How did your right neighbour feel during the iteration
Source: Fabián Lewkowicz
Ask each team member to try to briefly describe how their neighbour to the right felt during the iteration. Their neighbour confirms or corrects their guess.
Once all participants said what they think about how their teammates felt, you get an idea of how connected they are, how the communication is flowing in your team and if people are aware of the feelings expressed, in some way, by others.

Consider closing with activity #109.

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.

Original 4 (#55)

Ask Norman Kerth's 4 key questions
Source: Norman Kerth
Norman Kerth, inventor of retrospectives, identified the following 4 questions as key:
  • What did we do well, that if we didn’t discuss we might forget?
  • What did we learn?
  • What should we do differently next time?
  • What still puzzles us?
What are the team's answers?

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
  • Address concerns, e.g. by writing it down and setting it - physically and mentally - aside
  • In this retrospective - If you were a car, what kind would it be?
  • What's something that caused problems last sprint?
  • If you could change one thing about the last sprint what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

Know your neighbour - Closing (#109)

How does your left neighbour feel about the retrospective
Source: Inspired by Fabián Lewkowicz
Ask each team member to guess if their left neighbour thinks this retrospective was a good use of their time and why. Their neighbour confirms or corrects their guess.

If you have set the stage with activity #108, make sure to go around the other direction this time.

(#)


Source:
Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

Created by Corinna Baldauf

Corinna wished for something like Retromat during her Scrummaster years. Eventually she just built it herself in the hope that it would be useful to others, too. Any questions, suggestions or encouragement? You can email her or follow her on Twitter. If you like Retromat you might also like Corinna's blog and her summaries on Wall-Skills.com.

Co-developed by Timon Fiddike

Timon gives Scrum Trainings. As Integral Coach and Agile Coach he coaches executives, managers, product owners and scrum masters. He has used Retromat since 2013 and started to build new features in 2016. You can email him or follow him on Twitter. Photo © Ina Abraham.