6.3 Activity: Five Whys
Use this to generate insights in an iteration, release, or project retrospective.
Purpose
Discover underlying conditions that contribute to an issue.
Time Needed
Fifteen to twenty minutes.
Description
Team members work in pairs or small groups to look at issues. They ask “Why?” times to get beyond habitual thinking.
Steps
Introduce the activity by saying “Now that we know what’s happened, let’s look at why it happened.”
-
Review the issues and themes that the team has already identified.
-
Divide the team into pairs or small groups (no more than four to a group). And explain the process.
“One person asks the other(s) why an event or problem occurred.”
“In response to the answer, the questioner asks why that happened.”
“Record the responses that come out of the fourth or fifth ‘Why?’”
-
Monitor the time, and ring a chime or otherwise announce when the time is up.
-
Have the groups report what they discovered.
-
Use this information as input into the next phase, Decide What to Do.
Materials and Preparation
Use this in conjunction with an activity that generates themes or a list of potential problems, for example Patterns and Shifts.
Examples
Here’s an example. Say the issue is that the iteration review meeting never starts on time.
Q1: Why did we start our review meeting late on Thursday?
A: The room wasn’t available.
Q2: Why wasn’t the room available?
A: We forgot to put it on the meeting schedule.
Q3: Why did we forget ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access