9. Remote Retros – What’s different?

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hi there,

last week’s post had a co-located perspective. But nowadays, a lot of meetings, retros included, are remote. I’ve mostly facilitated via videocall, ever since Covid hit. At my workplace, we switched to everyone working from home virtually overnight and all my retros were suddenly virtual. The good news is, most things translate well into online retros.

For a long time, I had assumed that almost every activity could be adapted to work remotely and ever since creating the Retromat Miroboard Mega Template, I’m sure: Out of 146 activities, only 16 do not easily translate into a remote context.

Apart from adapting the activities, there are other things that are notably different in a remote setting:

  • Easier to prep for, harder to run
    I find it easier to prepare for remote retros: No need to book a room, make sure that the markers work, clean boards or other physical prep work. And ever since I built the Miro Templates, I’ve gotten really fast at prepping for a remote retro.
    During the retro, I find it harder remotely, mostly because of the tech hiccups that inevitably happen, like people suddenly dropping from the call.
  • Harder to stay focused
    Maybe that’s just a me-problem but I find it much harder to stay focussed in a remote setting, especially when I am waiting for others to finish a silent round of writing. In a co-located retro, there is nothing else for me to do but be present. Remotely, everything else I could be doing is just one browser tab away.
    And concentration in general is harder to keep up when all you do is stare at a screen. I try to have a break roughly every 60 minutes (compared to every 80 minutes for a co-located setting).
  • Body language and positioning
    These are missing in a digital context. 
  • There is no implicit rotation
    If you are all in one physical space, sitting in a circle, participants can take turns in round-robin activities very easily. That’s much harder in digital settings and often leads to wasted time, while everyone is unsure who’s supposed to speak next. Some ways to solve this:
    • Have a virtual circle of the team members on a board
    • Use the list of participants in your video call tool, if it’s stable and the same for everyone
      (I’d love to use this but we use Google Meet which for each participant omits their own name in the list. Makes it very easy to be unsure about when it’s your own turn)
    • Ask participants to pick the next person at the end of their own turn
      (I mainly use this one, but honestly, with mixed results. People frequently forget to name the next person.)
    • Use the “raise hand” feature of your videocall tool
      (We use that feature all the time in free discussions but not when going around in circle, when I’d ideally want everyone to speak once.)
  • Anonymity is harder to achieve
    If you want to run an activity with anonymous input, you need to put in more thought beforehand

It’s very likely that there are things missing here

If I can, I avoid hybrid settings. My retros are either co-located or everyone is on the call independently. In my experience, in hybrid there’s a good chance that the sound is crap and there’s always someone out of the video frame. Plus, the co-located people tend to forget about the remote people. That being said, tech has actually gotten better in recent years, with mics and cameras that can focus on the speaker and it’s not a total pain anymore. But bad audio is incredibly exhausting and if I don’t have to, I don’t want to potentially waste my participants’ mental resources.

Take a minute:
Which mode do you prefer, remote or in-person? How do you solve the round-robin turn-taking in remote settings?

Okay, that’s that then! On to the “during” part of retros next week 🙂

Cheers, Corinna

PS: If you use Miro, our Mega Template might be interesting for you.

PPS: I’ve only mentioned digital boards like Miro, Mural, Conceptboard etc. There’s always other ways to do it. I’ve used easyretro.io and heard of shared Google Docs, shared Powerpoint decks and so on. As long as you can all edit and are all referring to the same source, try out what works best for you out of the tools that are available.

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

8. Co-located Retros – Preparing the room and materials

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Welcome back!

Up until Covid, all my retrospectives were co-located. It’s the context in which I learned to facilitate and what informed most of Retromat. Today we will go over the logistics for co-located retros and next week we’ll look at how remote retrospectives differ.

Holding space – literally

One way to describe good facilitation is “holding space”. It’s meant figuratively but if the meeting is co-located then you also need to prepare the real, physical space.

Book a suitable room in advance. Get there early to set everything up for the retro. If you’re new to facilitation, make that at least an hour. This time will get lower as you get familiar with everything. But you’ll always want to have some time for last minute fixes and fetching missing stuff.

Team Room vs Different Room
I’ve just now realized that I’m so used to meeting rooms for retrospectives that I didn’t even consider using the team’s room (if they have a shared space).
I prefer a separate room to make it easier for the team to get into the retro headspace (“we’re doing something different now”) and so that we won’t be disturbed.
That being said, for some activities it is beneficial to stay in the space the team work in, such as “Room Service” or when you focus flow on boards.

If the room is booked immediately before your slot, prepare your equipment outside of the room.

I always use white boards, so I prep:

  • Board Markers for writing on boards and felt tip pens (I like Edding 1200 and 1300) to write the notes. I actually draw a line with each pen and sort out the ones that don’t paint well anymore.
  • Sticky notes in different sizes
    The expensive ones from 3m, cheap ones fall off the board. Actually, my new workplace provides reusable magnetic sticky notes from Bambook and these work pretty well. They definitely don’t fall off the board 🙂
  • Since I’ve prepped my activities in advance, I already know what I will draw on the boards, as soon as I can enter the room. Well, if the boards are clean, which they rarely are. So cleaning the boards, then drawing.
    I put effort into a lot of things, but physical boards are not one of them, sorry. Mine are very basic, that’s why I don’t need much time. That being said, teams usually do appreciate extra art work. (I observed that with other more diligent and/or artistic facilitators)

If you use flip charts, your list will look slightly different. Flip chart markers (I’m with the Neuland truthers), maybe sticky notes and felt tip pens, and you probably draw your charts beforehand, ready to hang up. Oh, something to put paper up with: Magnets, tape, needles, … Depending on what background you’re working with.

(Btw, here are my secret tips for more polished flip charts and sketchnotes.)

If you’re giving me a choice between co-located and remote retros (and it doesn’t depend on anything else like travel time, costs, health risks etc.) I’ll always choose co-located, because it gives me additional tools to use:

Body language

Someone’s body language is a valuable (even if sometimes misleading) source of information, not just for me, for everyone in the room! All of this is lost in a video call, and facial expressions are also harder to catch. All the shrugs, frowns, half-snorts, shuffling and turning away that clue you in to ask for clarification. It’s easier to pick up weird vibes and check in, in person.

Position in the space

Where and how someone sits influences how much they will take part. I use this to the group’s advantage. If somebody barely participates I will often try to physically bring them into the fold more: Are they sitting slightly outside the circle or apart from the group? I’ll invite them in.

Depending on the situation, I might talk to them after the retro in preparation of the next one, instead of putting someone on the spot during the retro.

Oh, I haven’t talked about the room setup yet!

For bigger teams (7 people or more) I set up the chairs in a flat u-shape around the whiteboards, with me sitting at one end of the u, so that I can easily get to the boards.

In small teams I tend to just have everyone sit around a table. That means that some people have to turn to see the whiteboard. I usually position the board at an angle at one of the corners, with me sitting next to it on one of the long sides, not the head of the table.

My goal with either setup is to increase the likelihood that team members will talk to each other, rather than with me. When I’m not actively explaining an activity I try to blend into the background.

Take a minute:

What room setups have you seen in workshops and meetings? How have they influenced the flow of the event? What would you like to try in your next retro?

Next week we’re gonna cover remote retrospectives. See you then *waves*

Corinna

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

7. Other factors – How I plan a retrospective

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hello again!

Here’s the hodgepodge of topics that I didn’t want to squeeze into last week’s post on how I pick activities. It depends on your context how much of my process might apply to you but at the very least you will know one way to do it and can figure out your way from there.

So, other factors to take into consideration, when choosing activities:

Are there activities that will be accepted better than others?

  • What’s the attitude towards retros? Do people want to take part?
  • Have individual people expressed preferences?

I cater towards wishes unless I think they are harmful. There are teams who crave novelty and are eager to try “crazy” stuff. There are teams that dislike “creative” association games.

There was one person who was okay-ish with stuff like “If the sprint was a food, what kind of food would it be?” as long as they didn’t have to come up with it on the spot. So as soon as I had picked my “Set the Stage”-activity, I would slack the prompt to them in advance. Half an hour was enough. I got to do whatever check-in I wanted and they got to be comfortable with it. It worked for both of us. The rest of the team knew of our compromise and never wanted in on the “spoiler”.

How experienced are the participants with group discussions? 

  • Are they already good co-facilitators? Do they take turns talking? Do they start clustering similar topics on their own?
  • Do they know basics like dot-voting?

The less experienced the team is with retrospectives, the more time you need to plan in for explanations. Check out my free book Facilitation is a Team Sport to find out more about how to make your life easier:

How’s the power (im)balance?

  • Are there formal hierarchies at play? Informal ones like seniority, some job roles being taken more seriously than others? 

Ways to counteract imbalances:

  • More written activities – makes people less likely to withdraw something in premature conformity/alignment
  • More anonymous activities
  • Outside of the retro: Ask more influential people to go late or last in round-based activities
  • Does it make sense to run the occasional retro without the team lead (or similar)?
  • Work on Psychological Safety (we’ll cover that in a later email) but ONLY if it is actually safe for everyone to speak up

Pay attention to other things that might surface in subtle ways (sexism, racism, homophobia, transphobia, ableism, …). It doesn’t have to be an active thing by anyone: The way we are all raised makes some people more comfortable with taking up time and space than others, and some people’s voices get more amplified because of what they look like. 

What about posting an agenda?

Some people whose work I greatly admire, post an agenda everytime. I rarely do, because my retros are on the shorter side, I work with teams long-term and everybody quickly learns the underlying structure.

When I work with a team that is new to retrospectives, I will talk briefly about the steps we’ll go through at the beginning and mention what times I’ve planned the breaks for. Other than that, I usually only post agendas for workshops upwards of 2 hours. 

Because this course is a lot of “I do it this way” I’d like to explicitly state that for many, many of my approaches I also know someone who goes about it completely differently and it also works. For them. It might not work for me because I’m different or because my team is different. There are a lot of ways to be a good facilitator and there are a lot of different teams out there. You’ve got to find an approach and style that works for you and your team. And I think you’re gonna rock it!

Take a minute:
Think about your team for a bit: What kind of activities would they love to participate in?
And what’s the internal power structure? How can you make sure that everyone gets heard?

On that note, I bid you farewell! In the next email we’ll dig a bit more into preparing a co-located retrospective. See ya,

Corinna

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

6. Picking activities – How I plan a retrospective

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hiho,

Today, I’ll share what I do when I sit down to plan a retrospective. This post will focus on picking activities and the next one will be a bit of a mixed bag of “oh, you might also want to consider this”.

Anyway, the first thing I do is look up what activities I used with this team last time and the times before that. My memory is like Swiss cheese so I note down which activities I do with a team for each retro. I don’t want to repeat myself too much or too early so that people stay engaged by new activities. I currently facilitate remote retros and just keep all of the retros for one team in the same big digital board – hey, presto: automatic archive 🙂

If I run the retrospective for more than one team, I tend to reuse a plan once for each team, unless there’s something specific to tailor to a team, either their current situation or their identity. When a team’s name is meaningful, I love to riff off on it. The team name is the name of an art movement? Better believe I bring pics of significant works every time. (Completely unrelated side note: I have weird niche knowledge about Dadaism.) Pokemon? Asterix? I will reference the hell out of these to support a shared identity.

Apart from that, my retrospectives all tend to follow the same basic layout that you’ve already seen in my previous posts:

1) Set the stage

I try to vary the focus e. g. in one retro focusing on feelings, in the next one on the sprint results, next one just for fun, and so on. My check in is often independent of whatever follows after. This is not what I would recommend. If you can make the check-in relate to what follows, that would be better. (But I’m honest here and that includes pointing out things I could improve on.)

1.5) Revisit the action items from last retro

Sometimes I bring back our decisions from the last retro to check whether we implemented them and if so, how our experiments worked out. More on that later in the course.

2) Gather topics

I haven’t worked closely with a team in years, which means that I don’t experience the daily routines of the teams I facilitate retros for. If there is a major disruption, I’ll hear about it but small stuff will pass me by unnoticed. That’s why 99% of the time I will use generic topic gathering activities so that the team can set the agenda.

If a team asks me to focus on a specific topic, I ALWAYS follow that request and will tailor all the activities towards that – up to and including creating new activities.

If you are sitting with your team every day you will likely observe things that prompt you to plan retros to address specific pain points more often than me in my more detached role. For inspiration, you can check out “Plans for Retrospectives”.

3) My Inner Loop

4) Closing

I usually ask about something the participants learned during the retrospective. Occasionally I will ask about how to improve the way I facilitate. When I start facilitating for a team, I will ask about the latter more often.

My inner loop is fixed. For all the other parts I open Retromat (yeah, I really scratched my own itch with that one) and use the arrows to step through the activities in the given phase until I find one that fits. For the “Gather topics” activity I’ll peruse both “Gather Data” and “Generate Insight” because the lines are blurry with those two.

When I’m done, I look at all the activities together. Does the plan as a whole make sense or is there an abrupt change in topic? E.g. I would not start with Amazon Review and then follow it with Movie Critic

Above, I’m sharing the retrospectives that I actually run, not the ones I think I should be running. Because I think I should run retros that adhere to the “5 phases” ideal from “Agile Retrospectives”. Yet, my retros have no 1:1 mapping of activities to match these phases: phases 2-3-4 are usually kind of merged without each of them having a specific activity dedicated to them *shrug*

Again, this is due to the fact that in my retros the team set multiple topics. It is what it is. And it has served my teams and me quite well. 

Do the activities fit timewise?

Next, I check that the plan roughly fits into the available time. How long are your team’s retros? 

The shortest retros I ever ran were 30 minutes. That actually worked because it was weekly and there were only 3 people who were quite aligned already.

For the biggest chunk of my facilitator life, I was on a 1 hour schedule for a 2 week sprint. That was always tight. We routinely took 65 minutes and I routinely dropped the closing activity due to time pressure 🙁

Then I moved to a team with 90 minute retros every 2 weeks and that worked much better. At my new workplace it’s 120 minutes once per month which also feels more relaxed and we sometimes finish ahead of time. I don’t think I ever want to go back to less than 90 minutes.

Whatever timeframe you are working with, roughly estimate how long each phase will take and thus how much time you can allot to the inner loop. The Retromat book and the free Retromat Quick Ref flag activities as short, medium or long.

A major factor that determines how much time you need is team size. Most activities take more time the more people are there. I would not attempt a 60 minute retro with a team of 15. With a team of 6 though, 60 minutes are probably fine. (Some teams are more eager to discuss than others, though…)

Okay, let’s make the cut here and see you next week for more things to consider during planning.

Take a minute:
How are you currently picking activities? How do the resulting retros work?

Back in a bit, Corinna

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

5. The Ground Rules for Retrospectives

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

‘Ello!

One of the main goals of a retrospective is to build shared understanding. That every participant contributes their unique perspective on events – things they observed and how they interpret them.

For this to happen, you need open conversations and those need trust from everyone involved. Trust that they won’t be blamed and trust that what they share will stay within the group.

That’s why some facilitators read out both the Prime Directive and the Vegas Rule in the beginning of every retrospective to remind everyone.

Prime Directive

The Prime Directive (for retros, not Star Trek) was created by Norman Kerth (the godfather of retros – we owe him) to remind everyone to stay collaborative, constructive and focussed on the way forward rather than blame:

Prime Directive for Retrospectives:
Regardless of what we discover, we understand and truly believe that everyone did the best job they could given what they knew at the time, their skills and abilities, the resources available and the situation at hand.

The thing is, we can’t change the past. But we can influence the future. Results are better if we stay curious rather than become accusatory – in retrospectives and most other situations in life as well.

(If you don’t like the specific wording of the Prime Directive, you’re not alone. Google for one of the many alternatives or come up with your own. Take care to keep the spirit intact!)

The second common ground rule is the

Vegas Rule

“What happens in Vegas, stays in Vegas”

To enable candor and high levels of trust, retrospectives are confidential. You want people to openly share their thoughts. That is less likely to happen if they are afraid to feed the rumor mill. Be very careful how you use information gained during retrospectives outside of them. The only information that is okay to share outside of the retrospective are its action items.

Of course just reading these rules out will not turn an “unsafe” environment into one where people suddenly feel comfortable sharing. You might need to work on Psychological Safety first. It will help you create conditions for fruitful retrospectives:

Time to take a minute:

What’s the vibe in your team at the moment? Do you openly share information or are people guarded? How high do you think the Psychological Safety is? Are you happy with the current state?

May your retros always be high on trust and low on blame,

Corinna

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

4. My Inner Loop, or: Phases are not always linear

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hi, hello, welcome!

So far we’ve looked at the 5 phases and last week at a concrete plan to facilitate your first retro.

Surprise! This week I’ll circle back and make some adjustments because I’m not doing it “by the book”. 

You see, the phases were meant to be linear and when I talk about them I usually keep up the appearance that I use them in sequence. But that’s not how I actually use them in the majority of my retrospectives – because I rarely run single-topic retros.

When Esther Derby and Diana Larsen wrote “Agile Retrospectives“, they had single-topic retrospectives in mind. In those, someone (often you) would set a topic and that’s the focus of the entire retro.

Whereas, when I facilitate a retrospective, teams usually cover several topics of their own choosing. By default, I run a “gathering potential topics”-activity like “Speedboat” or “I like, I wish” and then the team works through 2 to 4 of the gathered topics. That’s also what I recommend in the best retro for beginners

It would be strange to first talk about 3 topics in depth and afterwards come up with action items for all 3 of them in a separate activity. That’s why I use the phases with a bit of an inner loop:

We talk about 1 topic in depth and when the discussion has run its course and the team votes to switch to the next topic, we’ll spend another 5 minutes on creating an action item for this topic. And only then do we start with the next topic.

Depending on whether you run single-topic or multi-topic retros, I thought it might be worth stating this explicitly.

Take a minute:
What type of retrospectives do you think makes the most sense in your situation?

Hope this helps, 

Corinna

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

3. Best Retrospective for Beginners

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hello again!

Last week, I declared my undying love for Lean Coffee. This week, I’m sharing a concrete retrospective that you can use if you’re looking for a plan to dive in and facilitate your first retro.

Before we get to that, maybe you’re wondering, why I share a specific plan with you? Can’t you just open Retromat and presto: a plan for a retrospective?

Unfortunately, that is a terrible idea. Retromat is random. It combines the activities without any regard of them fitting together and most of them don’t. That is really easy to see for experienced facilitators and almost impossible to realize for beginners. Retromat was never meant for beginners.

Now that I got the disclaimer out of the way, here is my “Given that I know nothing about you or the team’s situation here’s my best shot at a multi-purpose, straightforward to facilitate” retro plan:


A great plan for beginners

(If this is also the first retrospective for your team it’s probably a good idea to explain the purpose of a retrospective and to talk about keeping things confidential. We will cover the latter topic in two weeks.)

Set the Stage:
Positive & True

Why: Create a positive vibe and give everyone an opportunity to speak.
How: Think of a question that is tailored to get a response that is positive, true and about their own experiences, e.g.

  • What have you done really well in the last iteration?
  • What is something that makes you really happy?
  • What nice thing did you do for someone else last iteration?

Introduce the question and give a minute or two of time to think. Then ask your neighbor the question again. After answering, your neighbor asks their neighbor on their other side the same question and so on until everyone has answered and asked.

Everyone gets to participate right away, everyone gets a little boost and we set a positive tone for the retro.

Gather Data + Generate Insight:
Learning Matrix combined with Lean Coffee

Why: Learning Matrix is a great multi-purpose method that has “appreciation for others” built-in. I use it to gather topics and then use Lean Coffee to structure and time box the conversations about these topics.
How: Show a flip chart with 4 quadrants labeled ‘:)’, ‘:(‘, ‘Idea!’, and ‘Appreciation’. Hand out sticky notes.

  • Let team members silently write their ideas for all the quadrants onto sticky notes – 1 thought per note. Encourage them to come up with at least one sticky note per quadrant. This can offset a struggling team going too negative or a passive team avoiding unpleasant truths.
  • Go around the team and let everyone put up their stickies on the flipchart and describe each topic in 1 or 2 sentences. Cluster stickies that are about the same topic.
  • Hand out 3 dots for people to vote on the most important issues, i.e. the ones they’d like to discuss. They can distribute the dots any way they like, i.e. they can put them all on one topic or three different ones and everything in between.
  • Order the stickies according to votes.
  • Say how much time in total you set aside for this phase and then explain the rules:
    “We’ve now got X minutes to talk about the top topics. We’ll start with the topic of highest interest. I’ll set a timer for 10 minutes. When the timer beeps, everyone gives a quick thumbs up or down. Majority of thumbs up: The topic gets another 5 minutes. Majority of thumbs down: Start the next topic with 10 minutes on the clock.”
  • Stop when the overall allotted time is over.

Decide What to Do:
Worked Well, Do Differently 

Why: Keep track of suggested action items
How: In preparation for the retrospective head 2 flip charts with ‘Worked well’ and ‘Do differently next time’ respectively. Write down suggestions for actions that people mention during Lean Coffee. State clearly that these are only suggestions for now. The team will vote on these later.

When all Lean Coffee time is talked up, ask if there are any more suggestions for actions. If so, let them write in silence for a few minutes – 1 idea per sticky note. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Hand out 3 dots for people to vote on which action items to try to distribute any way they like. (If you don’t have sticky you can also let people draw dots or lines with a marker.) The top 2 or 3 voted become your action items. Who is going to do them until when?

Closing:
AHA

Why: Share lessons learned and demonstrate the usefulness of retrospectives
How: Throw a soft ball around the team to uncover learning experiences. Give out 1 question at the beginning that people answer when they catch the ball, such as:

  • One thing I learned in this retrospective
  • One thing that surprised me during the retro
  • One thing that makes me hopeful after this retro 

[It’s rare but depending on the question it might uncover events that are bugging people. If any alarm bells go off, clarify immediately and ask if you can follow up outside of the retro if need be.]


In many situations the above plan will result in a nice, effective retrospective for you and your team. If you use Miro as a digital whiteboard, I’ve prepared a Miroboard here that you can copy for free.

You need 90 minutes of time for this plan. It also makes good use of 120 minutes. I can squeeze it into 65 minutes if I have to. 

Take a minute:
Can this plan work for you and your team? Which bits will you adapt for your context and why?

Facilitate a few retros to gain experience and when you run out of ideas, Retromat is always there to help. But please don’t use the first random plan you get! Adapt it to your and your team’s needs. And start out with simpler activities. Do not get overly excited with something like an elaborate superhero retrospective. Give everyone – yourself and the team – time to get familiar with the basic flow, voting mechanisms and such. You want them to be able to focus on the content, the problems they are trying to solve. They can’t do that if they are trying to figure out how a complicated activity works. When in doubt, pick something simple. If it goes well, you can try something more elaborate the next time.

That’s it for now, have a great week,

Corinna

PS: If you’d like some ready-made plans to get started, I wrote “Plans for Retrospectives” for this exact purpose.

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

2. Lean Coffee, my beloved

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hi there!

Last week, I talked about what a retrospective is and isn’t. Before we look at a concrete plan for a retro in next week’s post, I’d like to focus on just a part of that overall plan. A single method that I use all. the. time. Not just in retrospectives, in all kinds of meetings. It’s so versatile, it’s almost like magic – one of my all time favorite facilitation methods:

Timeboxed Lean Coffee

What’s it for, you ask? Excellent question!

Whenever you find yourself in a meeting without an agenda or clear topic, you can use Lean Coffee to create a prioritized list of topics in minutes. Time you easily gain back by staying relevant and fewer people zoning out.

With Lean Coffee you make sure you’re talking about things that the majority of people care about. With time boxes you make sure that the more outspoken people cannot keep a topic going that most participants have lost interest in.

Here’s how it works:

1) Collect Topics

  • Everyone needs sticky notes and a pen
  • You each write down the topics you would like to talk about – one topic per sticky note
  • Going around the group, everybody puts their stickies up on a board and reads out their topic(s). Cluster stickies that are about the same topic. If there is disagreement about whether something is the same topic, don’t enter a discussion just leave them as separate votable topics. When in doubt, don’t cluster.

2) Prioritize

  • Time to dot vote: People vote on the issues they would like to discuss by marking their 3 favorite topics
  • Order the stickies by number of votes

Boooyaa, there’s your prioritized agenda – reflecting interest in the topics \o/

3) Talk

Start discussing the top-voted topic. In the original description on LeanCoffee.org, you switch to the second topic, when the discussion peters out, and so on.

I always time box the discussions to make sure that no subgroup of people argues or rambles on forever about the same topic while everybody else is slowly falling asleep. My default time limits are:

  • Set a timer for 10 minutes. When the timer beeps, everyone gives a quick thumbs up or down. Majority of thumbs up: The topic gets another 5 minutes. Majority of thumbs down: Start the next topic with 10 minutes on the clock.
  • If applicable: Before you change the topic, write down any decision, todos, and the like
  • Stop when the total meeting time is up

Adjust these time limits to your context! If I know that a topic is highly controversial, I start with more time right away.

As a side effect, this method teaches two different ways of voting:

  • Dot vote – a fast way to choose between many options
  • Roman vote/Gladiator vote – a quick way to decide Yes or No for a specific choice

They are absolute facilitation basics that every team should know for less aimless talking and faster decisions.

Side Note on Turn Taking

In every discussion that you ever facilitate it is hugely beneficial if you introduce turn taking so that people who are comfortable with interrupting others will not bulldoze over those participants who are not. Turn-taking is even more important in remote settings. Raising your hand (either physically or digitally) to indicate that you want to speak and waiting for your turn, knowing that your team members will let you speak – that is a gamechanger. Going from the chaos of caucus to taking turns is simple and powerful.

Take a minute:

  • Are your team members already taking turns or are some voices crowded out?
  • Can you think of a meeting you regularly attend that would benefit from Lean Coffee? Or Dot Voting?
  • How can you introduce what’s missing?

I can’t wait for next week, when we’ll work through a specific plan to run a retrospective *excited*

Cheers from Germany,

Corinna

PS: Most of this email is an excerpt from my free ebook Facilitation is a Team Sport

PPS: A word on time keeping: If you are co-located, invest in a Time Timer. It’s an egg timer on steroids. It’s the clearest and easiest way to countdown time I’ve found so far. They are pricey (last I checked, about 60$) and they are worth every cent!

It’s super easy to set the time (you pull out the red disk) and it’s highly visible. Everybody is aware of how much time is left. Really helps with (self-)discipline. When the time is up, it beeps and nobody needs to be the bad guy that interrupts.

If you’re remote, check out the tools you are using for their time keeping features, e. g. I use the timer in Miro. Timers are also available in Mural and Conceptboard.

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

1. What is a retrospective?

[This post is part of Corinna’s Guide to Facilitating Retrospectives]

Hiho friend,

so, you might already know the basics and the standard five phases of retrospectives, but just in case you don’t (or if you’d like a refresher), let’s go through them and lay the foundation for the rest of the course:

So, what is a retrospective exactly?

It’s an opportunity to reflect, learn and improve as a team. It is time set aside – outside of day-to-day routine – to reflect on past events and behaviors. In its simplest form you answer three questions:

  • What worked well?
  • What didn’t work well?
  • What are we going to do differently?

In non-agile environments retrospectives are sometimes done after a project is finished as a “post mortem” to derive “lessons learned”. Those tend to be long meetings.

In contrast, in agile environments, a retrospective is short and done often (e.g. 90 minutes at the end of a 2-week sprint). Thus the project is still in progress and you can address issues jeopardizing the project’s success in time, hopefully keeping it on track. Additionally, you get into the habit of reflecting and improving, like a muscle that you train.

In Scrum, retrospectives belong to the cast of regular sprint meetings. In Kanban there’s a variety of ways to “schedule” retrospectives. In Lean, A3’s can serve the same purpose.

Who takes part?

“The team” – whoever that includes in your context. In Scrum it’s usually the whole Scrum team with dev team, PO and SM. If you have a specific topic that includes / affects people from outside the team, invite them to that retrospective to work on a joint solution.

If you are working in a structure that has team leads/managers, it is not uncommon to exclude them hoping it will make it more likely that people speak up. I’m wary of that because these roles typically have to offer a lot of perspective. If your team goes the exclusion route, try to also have retrospectives with them at least quarterly and see what happens.

What does a retrospective look like?

In its simplest form, the relevant people

  • meet and engage with others
  • talk about stuff and
  • agree on some actions (that will hopefully improve the situation).

Usually retrospectives are a little more sophisticated than that. Most follow the five phases suggested in “Agile Retrospectives“ (the quasi standard book on retros):

  1. Set the stage
    Give people time to “arrive” and get into the right mood; Set the goal
  2. Gather data
    Help everyone remember; Create a shared pool of information (everybody sees the world differently)
  3. Generate insight
    Why did things happen the way they did? Identify patterns; See the big picture
  4. Decide what to do
    Pick a few issues to work on and create concrete action plans of how you’ll address them
  5. Close the retrospective
    Clarify follow-up; Appreciations; Clear end; How could the retrospectives improve?

You can support each phase with activities to spark ideas and interactions. (That’s what Retromat is for 🙂

What is a retrospective NOT:

  • A blame game – Retrospectives are not about ass coverage and assigning blame. In fact, some facilitators start their retrospectives by reading out the “Retrospective Prime Directive“:

    “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”

    Focus on what you will do in the future. We’ll come back to this in a later post.
  • Just another meeting in which talk is cheap but no change follows – If the retrospectives don’t produce concrete actions or if no one ever carries them out afterwards, retrospectives are a waste of time.

Take a minute:
How do the retrospectives you’ve taken part in (or even facilitated) compare to the above? Which of the basics did you already know? What was new?

By the end of this course, we will have covered everything you need to know to run retrospectives that make a positive difference in your team’s work life! I’m really looking forward to it! 

PS: Here’s a 1-page summary of retrospectives, should you ever need it – for yourself or to teach others:

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂

Corinna’s Guide to Facilitating Retrospectives

Hello there,

welcome to this course about retrospectives, friend!

First things first: this course will be biased. I started out writing a neutral course and it did not feel right. Because, I would write down one thing and then go do something else in practice. So I scratched that first version and we’ll be doing it differently:

Imagine you have just started as my colleague. It’s your first position as a Scrum Master (or Agile Coach or …) and I’m supposed to show you how to facilitate effective retrospectives. It’ll be very personal, very “this is how I do it in this specific context, your context might be different. Another way to do it is …”.

If you were my colleague, we’d set up a weekly meeting and each time I will teach you something from my 15 years of experience. In between you’ve got time to try things out because no amount of reading will magically make you a good facilitator. You have to actually do it – put it into practice, see what works, what doesn’t and adjust accordingly.

Here’s the topics we’ll cover:

  1. What is a retrospective?
  2. Lean Coffee, my beloved
  3. Best Retrospective for Beginners
  4. My Inner Loop, OR: Phases are not always linear
  5. The Ground Rules for Retrospectives
  6. Picking activities – How I plan a retrospective
  7. Other factors that influence how I plan a retrospective
  8. Co-located Retros – Preparing the room and materials
  9. Remote Retros – Adapting activities
  10. During the retrospective – The actual facilitation
  11. Why do we do retrospectives?
  12. How to craft good Action Items
  13. Following up on follow through – A New Phase
  14. Why vary activities?
  15. What’s up with the team right now? – Tuckman (and Glasl)
  16. What kind of questions do you ask?
  17. Smoother Retrospectives with a Kick-Off
  18. Other Resources
  19. Farewell

If you’re serious about improving your skills, block half an hour in your calendar every week for the next 20 weeks. These 30 minutes gives you time to read, put everything into your context and pick something to try.

If a calendar entry won’t work for you, what else can you do to increase the odds of you engaging with this course to learn how to better support your team with retrospectives?

Start with the first unit and we’ll explore what retrospectives are all about – the foundation. Hope to see you there,

Corinna

PS: A BIG thank you to my test readers who made this course MUCH better:

PS: If you'd rather read this Guide as an ebook, click here. Or go all in and get it as part of the Retromat eBook Bundle at a discount. A purchase also supports Retromat as a whole 🙂