Facilitating retrospective for the first time — report
Tags: agile, beginners, tutorial, scrum
Published: 2022-11-28 12:02:32



Recently I had the opportunity to facilitate a retrospective for the first time in my life, this will be my summary of the experience.

The idea began with one of our founders asking me if I'd like to do that.

Originally posted couple of years ago as [Facilitating retrospective for the first time - report](https://grski.pl/retrospective.html)

Me? Agile/scrum-slavery/whatever-sceptic, leading a retrospective? Sounds like a recipe for a disaster.

Well, I agreed immidietely. Despite the fact that for the most part, I'm not a huge fan of all the current buzz around agile, scrum slaves (I love this term and abuse it often) and so on, plus the one pleasant thing that comes to my mind when I hear retrospective is just this song. Seriously, it's either just me or some people have gone mad, coming up with more extreme and weird practices when it comes to ~AGILE~, that produce little to no results other than annoying the developers and wasting business people's time.

Anyway - seeing lots of such hype, I get sceptical instantly. Hence I decided to look what's behind the other side of the fence.

Of course, I was aware that there are lots of worthwhile practices, things, habits and thinking patterns to learn from Agile bunch, it's not like I'm saying that all agile is useless. Do not interpret my words as such. It's just that some people are doing crazy stuff that is not Agile and calling it Agile. Especially in Poland so it seems. And that spirals into madness at times. I've seen it happen, no psychotherapist helped. I digress.

As it was my first time, I got offered some help. The company got me some hours with our friendly agile coach that helps us with building certain processes within the company. We had a quick chat before I planned my retrospective.

I've learned a bit about setting the stage, gathering the data, insights, nice tools to use and so on. This quick session, despite my initial doubt about it, helped me quite a bit. So thanks a lot here and shout out to Marcin Konkel!

## Ready, set, go

So came the day and time. The meeting started. I got nervous once we were all there. If it wasn't enough that it was my first retrospective, because of the way we work, and we work 100% remotely, it was a remote one. I personally find it harder to communicate remotely - you need to be more precise, exact, more communicative and attentive. It takes some time and skill to get used to this.

## Set the stage

Before we began, I decided to set up some clear rules and say out loud my assumptions, which were: We do not interrupt each other when talking. Considering how we hold the retrospective remotely, we need to adhere to this even more than ever. If you have anything to add outside of your turn/speaking time, raise your hand to the camera. The speaker or facilitator should take notice and give you the occasion. The first person to speak in a given round for a given exercise is chosen by the facilitator. That person gets some time to answer the question while others listen. After you are done speaking, you point the next person who should speak. After we agreed on these rules, I mentioned one thing.

It was a retrospective for our team. I'm a part of that team, actively participating in the development and work. Today though I was a facilitator. I was nothing more. Therefore I clearly stated, that today I'm doing just that - facilitating. Monitor, manage, facilitate and moderate the talk. Let them do the rest.

Also, I'm a bit of a direct guy - instead of using any fancy tools, I just went with talking. No post-it notes. No whiteboards. Just our faces, voices and me, quietly noting the whole retro in the background. Yeah - scary you actually have to talk to people. Ugh.

## Warm-up
I at first wanted to lighten the mood a bit, get people talking, as I was perfectly aware of what they were feeling at the moment. Some of them got interrupted mid-work, got thrown out of the flow to attend this meeting. They're in another context right now, so it's time to bring them here, into the moment.

How to do that? I asked everyone a simple question.

> What, be it in your private or work life, has recently made you happy?

This allowed the team to get a new little glimpse into each other. Maybe finding a new way of looking at each other. I know it sounds simple, but that's what actually happened. Everyone surprisingly shared some happy little moments from their private lives and you know what? I felt like it kind of tightened the bond that we all share, as a team.

## Past retrospective
Before this one, we held another retrospective in the past with a different agile coach, which resulted in some goals declared. Now it was the time to check upon them. So I've asked each person that had a goal defined, about the status of their goal, how is it going and what's their opinion, experience so far.

All the people agreed that previous goals were necessary, they are done or in progress and they improved our work somehow. Nice.

## Goodies - gathering the data
We work in a very multicultural and international team, yet despite that, it somehow turned out that on this retrospective, only Polish teammates were present. Being Polish myself, I know about our quirks, one of which is complaining. It's like hyperinflation, once it starts, there's no going back.

To set a proper vibe, I decided to first talk about some good things, to get people into a good mood. I've asked them all a question:

> What are some things that you think we do that make us deliver faster, better and overall contribute to us doing a better job or what are you pleased with recently?

Here everyone shared their perspective, insights and so on.

## Baddies - gathering the data
So, while they were still in a good mood and the aura was positive, I dropped in the bomb, that sometimes opens the gates of hell on Polish retrospectives - what went bad? Let's get down to the business. Enough of the sugar coating. The Polish way. Onion way.

Lo and behold, the complaining started. Or so I thought - that it'd start. Instead, it didn't.

I asked a question:

> What do you think we did wrong recently? What have you observed that makes us deliver less, slower? What makes your work less enjoyable?

Instead of simply spewing mindless blabber, the team did something nice. They came up with constructive and clever observations, insights and comments. It was quite amazing to witness honestly. Somehow I'm surprised at times how clever the people I work with are.

## Happies - still gathering the data
As I like to change the moods the way sinusoid function changes its value, I changed the topic again.

This time I decided to facilitate talk about things that we do that make them happy. It was different from the first question - good things we do - as here it wasn't about delivering, productivity and value generation. It was all about human connection and how we behave towards each other, how we interact. I thought it would be nice if they told each other what they notice about each others behaviour and what they appreciate.

I don't know about you, but I like a pat on the back sometimes - a sign that someone appreciates my efforts.

So:

> What do you appreciate that we do? Not in the aspect of productivity, coding or technicalities, but just like human beings - what makes you want to stay with us and spend our time together?

And this, oh boy, this point was quite sweet honestly. So, if we had sweet, then time for bitter again.

## Stop, it hurts
Now I decided to make the waters murky a bit. Threw in a topic:

Goals to improve. What should we stop doing? What should we achieve to improve?

And here I decided that this retrospective shouldn't end with just empty talk. I mean yeah sure, we improved the bonds a bit, got to know each other a tiny bit better and had a blast talking to each other (really!), but it's not enough for me.

So I threw in an idea.

Anyone, if they had such a wish, could choose one or more tasks, voluntarily, pain points of theirs, that they want to resolve till the next retrospective.

Other than that, they had to also choose a ~~witcher~~, watcher for their tasks. Maybe owner would be a better word here. That person will be responsible for checking up on their progress and so on. Basically, someone to make sure that the job will get done, other than that person. Someone to nag them a bit, like every other day, just ask a famous, in our company at least, question - What's the status here?

Why? While I trust my teammates that they will deliver project related things fully, these tasks were in the category of nice to do and all, but we won't die if we don't do them. They weren't critical, just a nice to do. Hence it'd be good to have some accountability and additional motivation to do them.

It also went well - almost everyone decided on some tasks for themselves.

## Inception
After that, there came a time for small inception. Retrospective for the retrospective. Basically, a short round of feedback regarding today's retrospective, my facilitation, value generated and so on. Supposedly they liked it, or that's what she said. Yeah.

That'd be it I guess. After that, the retrospective came to an end. I survived and actually found it meaningful. Yet quite challenging on the other hand.

I'm young, got this problem with my ego you know. It was a bit hard being at the sidelines, just spectating most of the time, being the moderator, instead of an active participant. I had some moments where I wanted to ditch my role as a facilitator and engage as a team memeber starting my endless blabbering, throwing in my two cents, but I refrained from doing so, managing to stay in my role.

It was a bit humbling and rewarding honestly.

Just so you know, later these tasks that we defined - they got done actually. So it, in fact, didn't end with just empty talking. Supposedly this idea with owners/watchers helped a bit too - maybe you can use it? No idea.

So well, Agile processes can be nice and useful too, that's first. Second, show some empathy and check out the other side of the fence. Maybe there's something valuable there, you just don't know it. Lastly, get out of your comfort zone. You'll grow.

If you are preparing for your first retro too, maybe you'll find this article helpful. Also: protip. Take notes. I did. Then, after the retro, I've turned it into a nice confluence page and tasks on Jira.

That'd be it for today, I, Olaf, was your humble host, hope you enjoyed.