The World Cafe is useful to spread Scrum patterns, practices, tips, and tricks across teams. If done well, you can expect to gain benefits by using Scrum processes and experiments done by your teams. On top of that, you as a Scrum Master will get a good picture of where your team currently is in Scrum adoption.
I recommend performing this exercise using round tables. Count six to ten people per table. Place a big sheet of paper, pens or markers with various colors at each table. I´d suggest trying paper napkins instead of flipchart sheets. In my experience, writing directly on the table triggers some kind of psychological effect that increases creativity and removes the typical "post-it-format" boundaries set by countless "mad/glad/sad" retrospectives.
In addition, you´ll need to write three questions. I´ll describe more about that in a bit.
First, divide the group evenly at the tables and let them elect a moderator for each table. The moderators will stay at their tables during the whole retrospective.
Groups start discussing the first question and write down all the ideas they have. They are allowed to do anything - brainstorming, sketching, mind mapping, etc. Set the timer for each discussion, and when done, ask participants to go away.
The participants should now form into new groups, if possible, grouping with people they haven´t yet talked to. The moderators present a brief summary of what has been discussed at their table and introduce the second question to the new group. They moderate the discussion further using the same or another technique, as they wish.
Repeat the same format for the last question.
The questions or statements to be discussed in this technique are key elements of a retrospective. Tip: choose the questions wisely, because choosing the wrong ones could threaten the whole discussion.
Some examples of statements:
Discussing the first question, you will experience current problems being verbalized and developed as people tell what has been painful in the past. Through the second question, different people will be laid onto the problems that are still visible on the table. Doing that, we want to have people think about the solution they implemented while being influenced by problems faced by others. The intention of the third question is to get new ideas out, ideas that often came out from the discussion but could not be expressed in the second round.
This technique is simple, but efficient in helping teams influence each other and come up with ideas on their own. Do not expect any radical ideas to emerge, but you should be able to see great ideas and experiments to run immediately.
To close this retrospective, gather the whole team and ask the moderators to present the outcome of their discussions. If you want, collect action items using silent voting (raising your hand) to prioritize the items in order of their importance.
Pictures credit: Tim Bourqguignon (Pictures are licensed under “Creative Commons Attribution-ShareAlike 4.0 International License”)
An Agile Retrospective is an event that ́s held at the end of each iteration in Agile Development and it serves for the team to reflect on how to become more effective, so they can tune and adjusts its behavior accordingly.
I believe the SailBoat exercise is quite a simple Agile Retrospective Exercise and does not require any special occasion.
If you are interested in getting some extra Agile Retrospectives exercises, I created a blog post with dozens of Agile Retrospectives Ideas, check them and see if you find something interesting.