In this post, I will explain the exercise “Happiness Index”. This exercise can be found in the book: “Getting Value out of Agile Retrospectives”, a book written by me and Ben Linders with the foreword from Esther Derby. The book can be downloaded by free in LeanPub.com or InfoQ.com, please download it and spread it within your colleagues.
This exercise is a combination of “Develop a time line” and “Emotions Seismograph” from Norman L. Kerth.
What can you expect to get out of this technique
The purpose of this exercise is to draw a graphic representation of team members´ emotions during sprints, connecting their emotions to sprint events. With this kind of information, the team can identify what exactly affects its performance during the sprint. For example, if they have some problems with the build server, most probably the mood will drop because of the team frustration not being able to proceed with the work. This kind of exercise is a great way to represent team emotions within the sprint.
When you would use this technique
I believe this technique is quite simple and does not require any special occasion. Although, it might be suitable for situations when a team has many different emotions within the sprint and they wish to analyse the consequences, or when the team has several challenges within the sprint and would like to understand better when and how the issues appeared.
Happiness Index is suitable for any team, it does not require any specific level of maturity.
How to do it
To perform this exercise, you simply need a A4 white sheet and some post-it notes. Start by dividing the sheet in two parts, having positive and negative axis. After, divide the X axis in the number of days that your sprint has.
There are two ways of doing this exercise:
1) The exercise is done within the retrospective itself with all the team
2) The exercise is done in small pieces during the sprint
Let´s start with the first option, create small groups of 2 or 3 persons. Ask them to do a small brainstorming session and let them think about all the events that occurred during the sprint. Afterwards, ask them to create a graphic showing emotion levels with events occurred during the sprint. When all groups are done, create a representation of all small groups in a single graphic. Do not forget to put an explanation of each different emotion.
For the second option, instead of the team drawing the graphic in the retrospective, each person will draw his own emotion level at the end of each work day. This approach will make sure that all events are covered and not forgotten.
Using one way or another, we will have a fantastic picture of what happened during the sprint. With this kind of information, a facilitator can help the team to identify events that should be repeated and events that cause delay in the team. The root of problems can be found using normal root cause analyses techniques.
With the right imagination, this exercise can be applied to remote teams as well. Being collocated is not a requirement to run this exercise.
What do you think about this exercise? Do you think this would be a good retrospective exercise for our new book? To find more information about the book, check my post here.
On my next blog post I explain how to use the “Star Fish” exercise to run a retrospective.
Please leave your comments, all your comments and ideas will help me to improve the exercise and the book.
In case you are interested in Agile Retrospectives I am at the moment preparing a 10 DAYS FREE AGILE RETROSPECTIVES PROGRAM. This is a complete self-study program where you will learn anything that you need to become a great Agile Retrospectives facilitator.