Mad Sad Glad is a popular agile retrospective technique that promotes emotional well-being by encouraging team members to consider ways to improve morale and create a positive team environment. While “old school” corporate practices might have promoted hiding your emotions at work, this retrospective exercise gives teams the opportunity to let them fly! If you want to learn how the team feels after the previous sprint, Mad Sad Glad is a straightforward option that is easy to explain and run.
Highlight different perspectives of shared experiences on the team.
Consider how systems and processes are affecting team and individual morale.
Take a closer look at the impact a certain event may have had on the team.
Use the Mad Sad Glad retrospective template to check on your team's emotional wellbeing. Allow your team members to analyze the positive and negative emotions they may have experienced during past projects. The mad sad glad template will allow you to build a positive team dynamic that will improve communication and increase productivity in the long run.
Not surprisingly, this agile retrospective exercise is designed to focus on what made the team experience three core emotions - mad, sad, and glad. Before the retrospective meeting begins, the facilitator selects this technique from the options in the retrospective exercises toolbox.
Get your team ready for the retrospective by briefly sharing your expectations for the retrospective, explaining how the technique works and defining the three columns:
Things that the team found frustrating in the last iteration
Things that the team found disappointing in the last iteration
Things that made the team happy and excited in the last iteration
Make sure all team members are aware of the procedures and everyone understands the prime directive of learning and encouraging positive attitudes. Depending on the size of your team, setting a timer - or timeboxing - can help keep the meeting on schedule and moving forward. Most teams are able to complete a Mad Sad Glad retrospective in about 60 minutes.
Ask your team to take time to think about the most recent iteration and create a sticky note for each idea or experience that made them mad, sad, or glad. Create a 10-minute timebox for participants to brainstorm and add their ideas to each column. Participants should keep their ideas private so a variety of honest ideas are provided. Doing this anonymously is the best way to collect honest feedback as it allows team members to think independently and to avoid being influenced by others’ experiences or input. When the timebox ends, the participants should finish adding their ideas to each column.
This next step helps the team find common themes in the ideas they generated and will help focus the upcoming discussion on the big ideas on everyone’s mind. So, if there are 5 notes on a new retro tool, you’ll most likely want to group those together under the same group to discuss. 😉 Announce the timebox (5-10 minutes) and allow participants to collaboratively group and name the notes on the board.
Sometimes it is clear that there is one point that needs to be discussed during the retrospective. And, sometimes it’s not so obvious and it can be challenging to identify the most pressing topics for the team. If this is the case, the facilitator can use dot voting to prioritize the discussion based on votes cast by the group.
Now it’s time for the best part, discussion! 🎉 If your team used dot voting, then the discussion should begin with the note group that received the most votes. If dot voting was not used, the facilitator can choose the order of discussion. The facilitator can optionally choose to timebox the discussion of each individual idea as well, usually setting aside 5 or 10 minutes for each topic of discussion. The advantage of this approach is that it tends to keep the conversation focused and moving at a faster pace.
Retrospectives are designed to organize actions that lead to change. The best way to ensure follow-through is to create and save SMART action items with each topic the team discussed. Create action items that help your team create tangible goals the team can measure when you are ready for your next retrospective. 😉