Use the Retrospective Exercises Toolbox to design your own Valuable Agile Retrospectives!
One technique often used in agile retrospectives is to ask questions to the Scrum team, and collect and cluster the answers. Based upon that, improvements can be defined that the team can do in the next sprint, which help the team to improve continuously. Asking questions is a technique that is easy to learn, but the effectiveness depends on the questions that you ask to the team. So let’s explore the questions that you can ask in a retrospectives.
Asking Questions is a retrospective exercise which is included in the successful book Getting Value out of Agile Retrospectives that Luis Goncalves and I have written. Order your copy from any bookstore (including Amazon, iBooks, Scribd, etc)!
Four Key Questions
When I start with a team that is new to retrospectives, I often use The four key questions. These questions come from the book Project Retrospectives: A Handbook for Team Reviews, by Norm Kerth. The questions are:
- What did we do well, that if we don’t discuss we might forget?
- What did we learn?
- What should we do differently next time?
- What still puzzles us?
The book from Norm Kerth was originally intended for project retrospective, but my experience is that much of it is also useful in agile retrospectives.
I’ve been using the 4 retrospective questions for many years, for me they have shown to be very effective. I like the question “What did we do well”, it’s a Solution Focused approach to find strengths which can be deployed to improve further. The addition “if we don’t discuss we might forget” makes this question even stronger: If something good happened by accident, that’s great, but what can you do to assure that you will keep on doing it? Also the question “what puzzles us” has given very useful insights for teams, by revealing things which had remained unspoken before I asked the question.
Valuable Retrospective Questions
Working with agile and non-agile teams, I’ve been doing project evaluations, audits, assessments using the CMMI and the People-CMM, retrospectives, and many other kinds of feedback sessions. Below are some questions that I often use, that have proved to help teams finding things that they could improve upon:
- What helps you to be successful as a team?
- How did you do this sprint?
- Where and when did it go wrong in this sprint?
- What do you expect, from who?
- Which tools or techniques proved to be useful? Which not?
- What is your biggest impediment?
- If you could change 1 thing, what would it be?
- What caused the problems that you had in this sprint?
- What’s keeping you awake at night?
- Which things went smoothly in this sprint? Which didn’t?
The trick is to pick the ones that help the team to get insight into the main/urgent issues and improvement potential, and adjust the questions where needed during the retrospective.
I’ve created a card deck with agile retrospective questions. These are powerful questions which are based on the Manifesto for Agile Software Development.
You can use these cards to coach teams, foster an agile mindset, and spice up your agile retrospectives.
One of the most valuable questions that I have experienced in retrospectives is asking why? Some examples are:
- Why did you do it like this?
- Why did this (or didn’t this) work for you?
- Why do you consider something to be important?
- Why do you feel this way?
- Why did you decide to work together on this?
Why is also a great follow up questions for any of the questions from the first list, it helps you and your team to create a better understanding of the problem that you are investigating.
Some people find it difficult to ask why, because they think or have experienced that people feel offended if they ask why. I have less difficulty with the why question, which may be because I have a genuine interest to understand situations and how people work together, without judging them. Once people know me, a “why” question doesn’t scare them.
Other Techniques for Retrospectives
There are a lot of techniques for retrospectives. Getting Business Value out of Agile Retrospectives describes many of them that I have used in retrospectives. Some examples are Root Cause Analysis, Timelines, Solution Focused, and the Perfection Game.
I vary retrospective techniques, it has happened more than once that I decided to change the approach while I was in the retrospective meeting, because another approach seemed more appropriate for the situation at hand. Or just to try something new, to keep the team interested in doing retrospectives.
If you want to learn new exercises and practice your retrospective facilitator skills then I suggest coming to one of my Valuable Agile Retrospectives workshops.
Which Questions do you Ask?
Retrospectives are a great way for teams to improve their way of working, to become more agile and lean. Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve continuously. I’m always interested to hear about experiences with retrospectives, there is still a lot that we can learn!
So I’d like to hear from you: Do you do Retrospectives? Which questions do you ask?
The Leanpub bundle Agile Retrospectives offers six great books to do amazing Agile Retrospectives. Together these books will make your Agile retrospectives rock! Teams will love to do them. And now you can get these books with a significant discount :-).
Retrospective Facilitator Tools
The following books and tools are available:
(This popular post from BenLinders.com post has been revised on September 2, 2015, May 29, 2017, and July 8, 2019)