Retromat: Lessons Learned Activities: 32-65-74-100-16

Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!

Retromat.org – by Corinna Baldauf

Plan-ID:

New random retrospective plan
Search activities for ID or keyword

Close

Search titles, summaries & descriptions

◄

Set the stage

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.

►

◄

Gather data

Appreciative Inquiry (#65)

Lift everyone's spirit with positive questions
Source: Doug Bradbury, adapted for SW development by Corinna Baldauf

This is a round-based activity. In each round you ask the team a question, they write down their answers (gives everyone time to think) and then read them out to the others.
Questions proposed for Software Development teams:

When was the last time you were really engaged / animated / productive? What did you do? What had happened? How did it feel?
From an application-/code-perspective: What is the awesomest stuff you've built together? What makes it great?
Of the things you built for this company, which has the most value? Why?
When did you work best with the Product Owner? What was good about it?
When was your collaboration best?
What was your most valuable contribution to the developer community (of this company)? How did you do it?
Leave your modesty at the door: What is the most valuable skill / character trait you contribute to the team? Examples?
What is your team's most important trait? What sets you apart?

('Remember the Future' (#37) works well as the next step.)

►

◄

Generate insights

Pessimize (#74)

If we had ruined the last iteration what would we have done?
Source: Judith Andresen

You start the activity by asking: 'If we had completely ruined last iteration what would we have done?' Record the answers on a flip chart. Next question: 'What would be the opposite of that?' Record it on another flip chart. Now ask participants to comment the items on the 'Opposite'-chart by posting sticky notes answering 'What keeps us from doing this?'. Hand out different colored sticky notes to comment on the comments, asking 'Why is it like this?'.

►

◄

Decide what to do

Landscape Diagram (#100)

Assess action items based on how clear they are and take your pick
Source: Diana Larsen adapted it from Human Systems Dynamics Institute

This activity is helpful when a team is facing an ambiguous, volatile, uncertain or complex set of problems and has many suggested action items to choose from.

Draw a Landscape Diagram, i.e. an x-axis labeled 'Certainty about approach' and a y-axis labeled 'Agreement on issue'. Both go from low certainty / agreement in their mutual origin to high towards the top / right. For each action item ask 'How much agreement do we have that solving this problem would have a great beneficial impact? How certain are we about the first steps toward a solution?' Place the note on the diagram accordingly.
When all actions are placed, shortly discuss the 'map' you created. Which actions will give the greatest benefit in the next iteration? Which are more long term?

Choose 2 actions from the simple / ordered area of the map or 1 action from the complex area.

►

◄

Close the retrospective

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives

Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.

►

◄

(#)

Source:

►

Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

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.