Retromat: Inspect & Adapt Example: 84-97-113-13-120

Last Retro's Actions Table (#84)

Assess how to continue with last retro's actions
Source: Sven Winkler

Create a table with 5 columns. The first column lists last retro's action items. The other columns are headed 'More of', 'Keep doing', 'Less of' and 'Stop doing'. Participants place 1 sticky note per row into the column that states how they want to proceed with that action. Afterwards facilitate a short discussion for each action, e.g. asking:

Why should we stop doing this?
Why is it worth to go further?
Are our expectations satisfied?
Why do opinions vary that much?

#tweetmysprint (#97)

Produce the team's twitter timeline for the iteration
Source: Thomas Guest

Ask participants to write 3 or more tweets on sticky notes about the iteration they've just completed. Tweets could be on the iteration as a whole, on individual stories, a rant, or shameless self-promotion - as long as they are brief. Hash tags, emoticons, attached pictures, @usernames are all welcome. Allow ten minutes to write the tweets, then arrange them in a timeline and discuss themes, trends etc. Now invite participants to favorite, retweet and write replies to the tweets, again following up with discussion.

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.

My Team is Awesome (#120)

Acknowledge what's awesome about your team
Source: Jesus Mendez

Give each team member a piece of paper and ask them to write down the following text:
'My team is awesome because _______________
and that makes me feel __________________'

Everyone fills out the blanks for themselves and signs below. When everyone is finished, put up the sheets on a wall. A volunteer reads out the sheets and the team celebrates by cheering or applausing. Take some time to review and share observations. Take a picture to remind the team how awesome it feels to be part of the team.

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.