Retromat: Agile Analysis Event: 32-7-113-13-138

Emoticon Project Gauge (#32)

Help team members express their feelings about a project and address root causes early
Source: Andrew Ciccarelli

Prepare a flipchart with faces expressing various emotions such as:

shocked / surprised
nervous / stressed
unempowered / constrained
confused
happy
mad
overwhelmed

Let each team member choose how they feel about the project. This is a fun and effective way to surface problems early. You can address them in the subsequent phases.

Mad Sad Glad (#7)

Collect events when team members felt mad, sad, or glad and find the sources
Source: Agile Retrospectives

Put up three posters labeled 'mad', 'sad', and 'glad' (or >:(, :(, :) alternatively). Team members write down one event per color coded card, when they've felt that way. When the time is up have everyone post their cards to the appropriate posters. Cluster the cards on each poster. Ask the group for cluster names.
Debrief by asking:

What's standing out? What's unexpected?
What was difficult about this task? What was fun?
What patterns do you see? What do they mean for you as a team?
Suggestions on how to continue?

Set Course (#113)

Imagine you're on a voyage - Cliffs and treasures await
Source: Katrin Dreyer

Imagine you're navigating a boat instead of a product or service. Ask the crew the following questions:

Where is a treasure to be found? (New things worth trying)
Where is a cliff to be safe from? (What makes the team worry)
Keep course for ... (What existing processes go well?)
Change course for... (What existing processes go badly)

SMART Goals (#13)

Formulate a specific and measurable plan of action
Source: Agile Retrospectives

Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'.
Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.

Debriefing Cube (#138)

Close with a reflective question from the Debriefing Cube and cards
Source: Chris Caswell and Julian Kea

A good debriefing deepens understanding, learning and sharing. Preparation: Download and assemble the Debriefing Cube and cards. During the retrospective, roll the cube. Then draw a card from the category it shows and use it to prompt a discussion. Repeat as time permits. This will broaden your debriefing options and is especially great for groups without a facilitator to enable them to effectively debrief on their own.

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. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. 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.