In this episode of Tangents with TorranceLearning, Meg Fairchild and Megan Torrance explore one of the most valuable practices in Agile: the retrospective.
They discuss why retrospectives matter, how often teams should hold them, and what makes them effective. Meg shares a practical structure for running retros that encourage honest conversation, meaningful reflection, and clear next steps—from opening activities and data gathering to prioritizing actions the team can actually implement.
Along the way, Megan and Meg talk about common challenges, including how to prevent retrospectives from becoming complaining sessions or opportunities to assign blame. They also share ideas for creating psychological safety, encouraging participation, and using tools like Miro to support anonymous input in virtual environments.
Whether you’re new to Agile or looking to strengthen an existing practice, this conversation offers practical tips for helping your team learn, adapt, and continuously improve the way they work.
Hosts: Megan Torrance and Meg Fairchild
Producers: Meg Fairchild and Dean Castile
Music: Original music by Dean Castile
Principles behind the Agile Manifesto
Pinpoint problems with Miro’s Fishbone Template
UX / UI Design Blog: Expert Trends, AI Tools & Career Guides | IxDF
Sprint Retrospective: How to Hold an Effective Meeting | Atlassian
AI Innovation Workspace | Miro
AI Transparency Statement: AI was used to generate the first draft of the transcript and the show notes for this episode. It was then edited by real humans.
Hey, Megan, let's do a podcast. Great idea. What should we talk about?
Speaker:Today
Speaker:we're talking about Agile retrospectives, which I
Speaker:know is one of Meg's favorite components of the Agile
Speaker:methodologies and techniques. So Meg, one of
Speaker:the Agile principles goes like this: "At regular intervals, the team reflects
Speaker:on how to become more effective, then tunes and adjusts
Speaker:its behavior." So that's retrospectives.
Speaker:Yep. What do you love so much about Agile retrospectives?
Speaker:Well, I mean, I think that sentence or that principle
Speaker:really says a lot, right? It's about that continuous
Speaker:improvement. I love continuous improvement. I love the opportunity that, like,
Speaker:we might be doing something today that's not working; that
Speaker:doesn't have to stay that way forever. We can make it better, but we can
Speaker:only make it better if we start talking about what it is that
Speaker:we see might be a problem or might need to be improved. I
Speaker:also love that we're coming at it from this structured format.
Speaker:It's not just, "hey, let's get in a room and complain."
Speaker:We have a very, like,
Speaker:reliable way that we can go about them, and when you
Speaker:have that structured format, everybody knows what to expect. You come in
Speaker:and you go through the activities in
Speaker:a certain order, and then that makes it easy. It makes
Speaker:something that could be really fraught much easier.
Speaker:And then I think you get this added bonus sometimes, depending on how you run
Speaker:them, of getting to really acknowledge the the hard work and the
Speaker:accomplishments that all of your colleagues have put in
Speaker:together over the past period of time. I love that part of it too. Yeah.
Speaker:So all right, here's a challenge that I have with retrospectives
Speaker:because I love them too. But the word retrospective
Speaker:makes it sound like it comes at the end. The way you describe it though,
Speaker:it sounds like something we ought to be doing more frequently. So how
Speaker:do you advise teams to make that happen on a regular basis?
Speaker:Or what regular basis should it be done? Right. Well, I mean,
Speaker:retrospectives come from Agile, which has this
Speaker:idea of having sprints. So
Speaker:sprints are 2 weeks in Agile. And so, yes, the
Speaker:retrospective comes at the end of that 2-week sprint. Wait, wait, wait.
Speaker:Not the end of the project? Not the end of the project. Oh.
Speaker:Right. Yeah. So you're supposed to be doing them on this more
Speaker:frequent, regular basis. And yes, it's at the end, but it's at
Speaker:the end of a short chunk. I think though
Speaker:that depending on the work that you do, and if you're not in a
Speaker:software development team or role, there might be a little
Speaker:bit more nuance to that. That cadence, your team
Speaker:might not work in 2-week sprints. Maybe it's like here we
Speaker:have iterations. We've got an
Speaker:Alpha. We've got an
Speaker:Alpha iteration. We've got a Beta iteration. Maybe they come at the end of those
Speaker:iterations. Maybe they come
Speaker:at the end of every month because that's a cadence that works well
Speaker:for whatever process it is that your team works with.
Speaker:So I think you need to think about where are you going to
Speaker:reap the most benefits in terms of your cadence.
Speaker:You don't want it to be so spread apart and
Speaker:so long in between them that
Speaker:there's, you know, so much has happened, it's hard to really even
Speaker:think back to the beginning. And then there's no opportunity to make
Speaker:things better if they come at the end unless there's a next thing
Speaker:that's coming after. And you also — but you also don't want to make them
Speaker:so frequent that there's nothing
Speaker:new that's happened. It's like you're almost having the same
Speaker:conversation over and over and over again. Yeah. And it
Speaker:sounds like if you're doing them frequently, it's not just — it sounds like you're
Speaker:not doing them just when somebody screws something up. Or if something's gone bad.
Speaker:Absolutely, yeah. So the other
Speaker:thing you might want to think about is who needs to be involved in that
Speaker:retro. So you also want to consider,
Speaker:if you can, having a facilitator join. Somebody who's
Speaker:not necessarily on the team that's been doing the work. It might be,
Speaker:if your organization has this capacity, bringing in somebody
Speaker:from another team who knows the process,
Speaker:and can lead everybody through that, but they
Speaker:haven't been kind of hands-on in that particular
Speaker:workstream. Who else to invite?
Speaker:Obviously, everybody who has been doing that work. They need to be the ones to
Speaker:be sharing their ideas,
Speaker:identifying issues, participating in that
Speaker:retrospective. But it needs to be also limited
Speaker:to that team. You're not going to say, "oh, hey, come join our retrospective. You
Speaker:can see how it works!" Or "we want
Speaker:to share it with everybody!" No, it really needs to be focused on that team
Speaker:because you also need to be able to have frank conversations
Speaker:about that work. And if you're on display for
Speaker:the entire company to see what's happening in your retrospective, that's
Speaker:not going to lead to those honest, open conversations.
Speaker:Then it's just performance. Right, exactly. So
Speaker:around here, we love our templates. They help us move fast.
Speaker:They help us keep the flexibility and the creativity where it
Speaker:needs to be in a process and helps us be
Speaker:consistent and scalable. You have made
Speaker:us a pretty awesome template or agenda for our
Speaker:retrospective. So can you walk us through that? Yeah, absolutely. And
Speaker:this template has — there's about 5 parts or
Speaker:so. So we'll go through each one. So first, and
Speaker:actually before first, I'm going to add one up at the top, which is
Speaker:helping just to open the meeting by
Speaker:grounding everybody in the goal. Reminding everybody why are we here,
Speaker:what is this retrospective about. I think that can be a really nice way to
Speaker:bring everybody's mindset into the right place. Kind of like an
Speaker:orientation. Kind of like an orientation or like an agenda. "What's on our agenda
Speaker:for today?" Or yeah, "where are we
Speaker:aiming for?" "Where are we pointing here?" The next thing that you would
Speaker:want to do is just a really quick set-the-stage at the beginning,
Speaker:kind of like an icebreaker. It could be
Speaker:like a one-word "how are you feeling?" You could have a list of
Speaker:feelings, emotions — just pick a word and say it, and the goal here actually
Speaker:is not to use any of that going
Speaker:forward, it's really just to get everybody speaking, everybody in the
Speaker:room saying something, because research shows
Speaker:that if somebody comes off of
Speaker:mute and says one word at the beginning of a
Speaker:meeting — a virtual meeting or an in-person meeting — they will then have more
Speaker:likelihood that they'll participate in the rest
Speaker:of the meeting. So we want everybody's voices here. So just always, it's not
Speaker:optional. You have to pick a word.
Speaker:It doesn't matter what your word is. It's just how are you feeling in
Speaker:that moment. Alternatively, you could ask a question like, "what part
Speaker:of process or part of the project were you
Speaker:most interested in talking about today?" But that gets... it's less... I don't know,
Speaker:it might get more complicated and isn't
Speaker:quite as quick.
Speaker:So it feels like you want an icebreaker, not a conversation
Speaker:stopper by getting in deep. Yep, yep, and it depends on what works best
Speaker:for your group. If you have a different way to open it up, just get
Speaker:people talking. The second part, and this is where I
Speaker:think the biggest meat of your time is going to be spent, is in
Speaker:gathering information. So there's
Speaker:different ways that you could go about
Speaker:doing this, and if you search for templates or
Speaker:retrospective templates or ideas for
Speaker:how to run a retrospective, this is what you're going to get is
Speaker:these pictures or tools
Speaker:that you can use to pull out ideas from
Speaker:everybody about what has happened over the past period of time. So it might
Speaker:be like a timeline exercise, or it could be...
Speaker:there's like a sailboat one. There's all sorts of different things that people have
Speaker:come up with, but a really common one is like "start, stop, change, continue."
Speaker:Or there's
Speaker:what I— "Roses, thorns, buds"? "Roses, thorns, buds,"
Speaker:"what I know, what I wonder, what I learned," those types
Speaker:of things. So those are... that's where you're going
Speaker:to really start to identify, and you're going to want other —
Speaker:everybody in the room is going to be putting their ideas into one
Speaker:of those categories or participating in
Speaker:throwing things out there. From there,
Speaker:one of the things that you can do is
Speaker:then start to identify from any issues
Speaker:that you have, any problems that you've identified,
Speaker:dig into why. Why is that an
Speaker:issue? So you can use the technique of the 5 Whys and start
Speaker:with that issue and
Speaker:then go backwards. Well, why did that happen? Or why did that happen? Maybe
Speaker:a fishbone 5 Whys exercise
Speaker:would work well here. And then from there,
Speaker:if you identify some action items, and those action items
Speaker:might come out of 5 Whys, they might come directly from the
Speaker:issues that you identified above, then
Speaker:you can pull those down and figure out
Speaker:what are some action items that we want to come out of this
Speaker:retrospective with? And what we have in our
Speaker:template is to take an action item, try to
Speaker:estimate, "what is the impact?" If we were able to solve or take
Speaker:this action forward, how is that
Speaker:going to impact how we work together? Is it going to be a large impact,
Speaker:a small impact? And we use t-shirt sizes, which is a common Agile approach
Speaker:here. So we measure or
Speaker:estimate the impact. We also estimate the effort.
Speaker:How much effort is it going to take us to get this done? We also
Speaker:use t-shirt sizes there. And then we vote on who
Speaker:has energy around what. And it's not who has energy to do
Speaker:what, but who has energy like, "ooh, I really think
Speaker:this is the thing we need to focus on." Now, if you're
Speaker:doing your retrospectives more frequently, you're going to try
Speaker:to keep those votes to 1 or 2 items. You're
Speaker:not going to be changing a lot in between iterations. If
Speaker:you're doing things in longer timescales, you
Speaker:might have identified a lot of issues and problems, and so there might be more
Speaker:action items that come out of that. And then lastly, you're
Speaker:going to close with trying to get a sense
Speaker:for how did you do? Was the retrospective good and helpful to
Speaker:your organization? So you could have a couple of real quick survey questions
Speaker:at the end for people to look at. Okay, I kind of love that your
Speaker:evaluating was effectively an evaluative process
Speaker:about the team's process. And what
Speaker:I love about retros is that you're talking about the process,
Speaker:not the product. It's the product of
Speaker:the work that you do, that's for the customer, the stakeholders,
Speaker:the business to evaluate. Here you're talking really about the team's
Speaker:process. Yeah, exactly. Yeah, how can we make our process better?
Speaker:So we just completed a big chunk of work
Speaker:with a team of about 2 dozen people. And we had a series of
Speaker:retros. So how do you keep a retrospective from becoming
Speaker:a blame game, a big complain-a-thon, a chance for
Speaker:bullying, otherwise basically a miserable experience for
Speaker:everyone? That's a great question. I think it really comes
Speaker:down to what is the mindset of the leaders of your
Speaker:project team, of your organization around retrospectives and making
Speaker:sure that, as I talked about,
Speaker:having that goal up front. Part of the goal is to make sure that everybody
Speaker:feels heard and that they have a voice and that they have a seat at
Speaker:the table. And if that's your goal, and that's the
Speaker:mindset that you're going in with, then
Speaker:that makes the focus less about "what did so-and-so
Speaker:do wrong?" But it's like, "what can we, together as a team, do
Speaker:better and how can we improve?"
Speaker:So it's that team mindset and
Speaker:also focusing on "what is our goal? Our goal is to continuously
Speaker:improve." I love that. And it's also, it seems
Speaker:very much in line, it's not just the culture of the
Speaker:retrospective, but the entire project itself.
Speaker:Yeah, super cool. My takeaways from this conversation.
Speaker:One is I love the opportunity for a team
Speaker:to say, "wow, let's not do that again" early in the process rather
Speaker:than not surfacing these great ideas
Speaker:from the team and only finding out at the end that we shouldn't have been
Speaker:doing something, there was a better way to do it. And I remember
Speaker:back early in my career doing a number of lessons learned at the end of
Speaker:— or after-action reviews — at the end of project, and we would
Speaker:have this lessons learned, we'd
Speaker:write it up we'd put it away in some file somewhere only to be
Speaker:discovered years later, like, "oh, somebody already had this idea —
Speaker:it just went nowhere."
Speaker:Yeah. So the ability — and I'm watching you and the team surface
Speaker:these action items, identify accountability,
Speaker:responsibility for moving them forward (the ones that had energy) and
Speaker:doing something about it. And when people
Speaker:feel listened to, like they do by you and this team,
Speaker:that keeps the ideas flowing. So I love it
Speaker:so much. So Meg,
Speaker:is there one last thing that you want to add here before we close
Speaker:this out? There is one more thing.
Speaker:We have used Miro or an online
Speaker:whiteboard like Miro for our retrospectives and have
Speaker:found that that helps immensely, especially for a virtual team that's across
Speaker:distance. They can be really helpful for
Speaker:also keeping — if not everybody in your organization has an account, maybe just
Speaker:one person does — you can keep the brainstorming somewhat
Speaker:anonymous because everybody's coming in as an anonymous
Speaker:architect or an anonymous panda bear
Speaker:or whatever they come in as in those
Speaker:tools. So that can be a really effective way
Speaker:to go about structuring your retrospectives. And then you
Speaker:have this, like, copyable template that you can use over and over and
Speaker:over again. Super quick and easy.
Speaker:So Meg, how did that go? I think it went well. I
Speaker:think, I think I got a little lengthy in my describing of the template,
Speaker:but I think overall, I hope we got people
Speaker:a good high-level overview of how retros
Speaker:can possibly help out their organizations and help
Speaker:them continuously improve their teams working
Speaker:together. You know, Meg, people love getting copies of our templates. Can we
Speaker:put a copy or a screenshot or something of our template out?
Speaker:Absolutely. Let's do it. All right. This is Meg
Speaker:Fairchild and Megan Torrance. And this has been a
Speaker:podcast from TorranceLearning. Tangents is the official
Speaker:podcast of Torrance Learning (as though we have an unofficial one). Tangents
Speaker:is hosted by Meg Fairchild and Megan Torrance. It's
Speaker:produced by Dean Castile and Meg Fairchild, engineered and edited
Speaker:by Dean Castile, with original music also by
Speaker:Dean Castile. This episode was fact-checked by Meg
Speaker:Fairchild.