Happy Teams Embrace Obstacles—Building Psychological Safety Through Retrospectives | Stuart Tipples

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Episode: Happy Teams Embrace Obstacles—Building Psychological Safety Through Retrospectives | Stuart Tipples
Host: Vasco Duarte
Guest: Stuart Tipples
Release Date: June 12, 2025

---

Introduction

In this engaging episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Stuart Tipples, an experienced Agile Coach and Scrum Master, to explore the pivotal role of retrospectives in fostering psychological safety and building happy, resilient teams. The conversation delves deep into effective retrospective techniques, defining success as a Scrum Master, and the essence of maintaining happiness within Agile teams despite facing inevitable obstacles.

The Power of Retrospectives

Stuart Tipples opens the discussion by sharing his journey with various retrospective formats, emphasizing the importance of finding the right structure that balances fun and productive introspection.

"My personal favorite is the four L's: Liked, Learned, Lacked, and Longed for." [01:46]

The Four L's Framework

Stuart advocates for the Four L's retrospective format, highlighting its effectiveness in:

• Liked: Encourages team members to express what they appreciate, fostering a positive atmosphere.
• Learned: Focuses on growth and knowledge gained, promoting continuous improvement.
• Lacked: Identifies gaps in support, tools, or processes, allowing the team to address challenges honestly.
• Longed For: Provides space for dreaming and envisioning future aspirations, inspiring the team to aim higher.

"It's structured enough that people don't freeze up, but open enough to uncover genuine golden moments." [02:11]

Theming Retrospectives for Engagement

To enhance participation and engagement, Stuart suggests theming retrospectives based on team interests or cultural events. He shares his success with integrating themes like cricket during the World Cup or leveraging popular culture references such as Star Wars to make sessions more relatable and enjoyable.

"If somebody wants to talk to me, you draw parallels from things like Star Wars or pop culture and I will instantly become engaged." [05:34]

Building Strong Team Relationships

A cornerstone of effective Scrum Mastery, Stuart emphasizes the necessity of one-on-one interactions to build trust and understand team members both personally and professionally.

"We are dealing with people, not resources. One-to-ones are crucial for building those relationships." [05:37]

These personalized connections help Scrum Masters tailor their approach to meet individual and team needs, fostering a supportive environment where members feel valued and heard.

Defining Success as a Scrum Master

Shifting focus to success metrics, Stuart challenges conventional indicators like organized Jira boards and well-written user stories. Instead, he underscores intrinsic team dynamics as true measures of success.

"If a team does all those things while you as a Scrum Master are not in the room, that's your metric of success." [08:29]

Key Indicators of Success:

1. Healthy Conflict: Teams engage in constructive disagreements that lead to valuable insights rather than unresolved tensions.

   "Healthy conflict that ends with insight doesn't end with people running off to HR or handing in resignation letters." [06:41]

2. Transparent Priorities: Clear and visible priorities ensure that all team members are aligned and there are no hidden agendas.

   "Transparent priorities mean no Secret Squirrel work or hostage-held roadmaps." [08:17]

3. Self-Checking Behavior: Teams proactively assess their actions and decisions, embodying the principles and values instilled by the Scrum Master.

   "They are living the principles and the values that you've been instilling. They are calling, they're imagining your voice in their heads." [08:29]

These indicators highlight a mature, autonomous team that operates effectively without constant oversight, reflecting the Scrum Master's successful guidance.

Happy Teams Embrace Obstacles

Vasco and Stuart delve into the concept of "happy teams," clarifying that happiness is not the absence of problems but the presence of resilience and a positive outlook towards challenges.

"Happy teams look like committed individuals that want to overcome whatever problems come their way and still feel happy about their ability to do the right thing." [10:31]

Characteristics of Happy, Resilient Teams:

• Trust and Autonomy: Team members feel trusted to make decisions and take ownership of their work.

  "Feeling trusted, feeling value. That's gotta be as close to sort of happiness in the workplace as you can get." [11:24]

• Positive Challenge Perception: Obstacles are viewed as opportunities for growth and improvement rather than insurmountable barriers.

  "The ability to see an obstacle as a challenge, as something positive to build on, is what happiness means." [10:31]

• Energy and Engagement: Teams remain energized and motivated, even when facing difficult moments, maintaining a proactive and solution-oriented mindset.

Stuart paints a vivid picture of an ideal Agile team environment where members feel empowered to tackle daily challenges with confidence and enthusiasm, ultimately leading to higher productivity and satisfaction.

Conclusion

The episode underscores the critical role of retrospectives in cultivating psychological safety and fostering a culture of continuous improvement within Scrum teams. By adopting effective retrospective formats like the Four L's, building strong personal relationships, and redefining success through intrinsic team dynamics, Scrum Masters can guide their teams to become resilient, happy, and high-performing.

Stuart Tipples provides actionable insights and practical strategies that listeners can implement to enhance their Agile practices and achieve sustainable success. Ultimately, the conversation highlights that true happiness in Agile teams stems from trust, autonomy, and the collective ability to embrace and overcome obstacles together.

Key Takeaways

• Effective Retrospectives: Utilize structured formats like the Four L's to balance appreciation and honest feedback.
• Engagement through Theming: Tailor retrospectives to team interests to boost participation and enjoyment.
• Building Trust: Conduct regular one-on-ones to understand and support team members individually.
• Redefining Success: Measure success by the team's ability to self-manage, maintain transparency, and handle conflicts constructively.
• Happy Teams: Foster a culture where challenges are seen as opportunities, and team members feel trusted and valued.

Notable Quotes

• "It's structured enough that people don't freeze up, but open enough to uncover genuine golden moments." — Stuart Tipples [02:11]
• "If a team does all those things while you as a Scrum Master are not in the room, that's your metric of success." — Stuart Tipples [08:29]
• "Happy teams look like committed individuals that want to overcome whatever problems come their way and still feel happy about their ability to do the right thing." — Stuart Tipples [10:31]

---

For more insightful discussions and actionable Agile strategies, tune into future episodes of the Scrum Master Toolbox Podcast or consider joining the Scrum Master Toolbox Membership for exclusive content and community support.

Transcript

[Vasko]

Hey there, agile adventurer, just a quick question. What if, for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast. Hello everybody. Welcome to Success Thursday, the big question of the week this week with Stuart Tipples. Hey, Stuart. Welcome back.

[Stuart Tipples]

Hey, let's go.

[Vasko]

So looking forward to this. And we'll talk about success, of course. And that's the one I'm looking forward to. But to set that up, let's talk about retrospectives. We've mentioned retrospectives a few times this week, but when you think about retrospectives, retrospectives as a core engine of improvement and of course adoption in some cases. What's your favorite agile retrospective and why?

[Stuart Tipples]

So I have. Over my career, I have played with the retrospective format in so many ways. I will hold my hands up. I have been guilty of being that Scrum master that sort of tries to enforce fun on the team in the retros. Right. Learn that lesson very quickly. You can't.

[Vasko]

Fun will not be optional. You shall be laughing.

[Stuart Tipples]

Yeah, it's terrible. And really I have no excuse because I'm the worst person for that, right? If you try and tell me that it's going to be fun, I'm instantly going to pull my shirts down. Right? But having sort of messed about. There's a couple of key things that I've picked up and one, if we're looking at four format, my go to nine times out of ten is my personal favorite is the four L's liked, learned, lacked and long for. You're going to ask me why and it's a really easy response to me. It is for me. I find it. It's the perfect balance of it gives you the warm fuzzies. But it's also great for that sort of hard honesty. So if we break it down light, that gives us space for the appreciation. Right. So that's, that's the warm fuzzies bit I touched on. Right, Learned. So that's already shining a light on some growth. Okay. So again, that's brilliant. As a, as, as a, as a, as an agile team, as a scrum team, that's what we want to see in the lacked area. That's a great way for sort of exposing our gaps and whether that's support, tools, behavior, we want to shine a light on that. Right. That's what scrum is very good at. Right. It holds that mirror up and it shows us. And then last one, we've got the longed for. And what the longed for is great. And it sort of comes back to the warm and fuzzies. Is that space to dream and dream big. Right. Necessarily going to achieve it. But it gives us that space for people to sort of really sort of share those big dreams on what we'd like as a team to sort of see, to be able to do. It's structured enough that people don't freeze up, but it is open enough that it allows us to sort of, sort of uncover genuine sort of golden moments. It's very helpful, particularly in the early days of team formation, of building psychological safety. It's a really good format for, for that and you can play around with it. Right. So one thing I learned is I'm very visual in my style of learning how I like to share information and how I absorb information. So one of the sort of dialing down the force fun element of retrospectives is I used to take a lot of time that I would theme them and so we would either be around the team and sort of having built the relationship with the team, something I know they like. So if they're particularly with a lot of the offshore teams I've worked at the time, if it timed around the cricket World cup, then I would go away, I would learn about cricket because I knew nothing about it and I would do that. Obviously you can do the seasonal ones. Your Christmas, your Halloweens again. Diwali with some of the guys working in India was really successful. But just putting a visual theme on it, it's surprising how quickly that draw and engage people in. As we've talked about, I'm a huge Star wars nerd. So if somebody wants to talk to me, you draw parallels from things like Star wars or pop culture and I will instantly become engaged and it's a really effective way and we can actually.

[Vasko]

Work with the team to find what are those themes? Right?

[Stuart Tipples]

Yeah, yeah. I mean, that's a Scrum Master look. We focus on the team, the team is the collective and it's the team as a collective that's going to deliver these awesome products. Right. But remembering, as we've said before, we are dealing with people, we are working with people, we're not working with resources, we're not working with skill sets, we're working with people. As a Scrum Master, if you're not or if it's something you've let slip by, you absolutely have to have those one to ones, right? So you can speak to the people in your team individually and that's how you build relationships. That's how you learn about what they've got going on in work, but what they've got going on in their personal lives. If something exciting is coming along, whether it's their kids talking about one on.

[Vasko]

Ones and talking about building those relationships, of course that's a critical element for us to reach a successful outcome of our work as Scrum Masters. But in order to do that, we need to have a clear vision of what that looks like. So that's the next question. Stuart, how do you define success for yourself as a Scrum Master?

[Stuart Tipples]

What does success look like? I can tell you what it doesn't look like. I can tell you it's not shiny, organized Jira boards and well written stories. Although that sort of can seem like success very early on. Right. It seems like that's a great metric for success. That stuff will come, right. That's tooling and that's what you need, success as a Scrum Master. I think it comes back to a little bit what we talked about before. If you are working with a team where healthy conflict happens and it doesn't need you necessarily tease it out, but it's healthy conflict that ends with what should we say? It ends with insight. It doesn't end with people sort of running off to HR or handing in resignation letters. Right. That's healthy conflict. It's about teams having transparent, so visible priorities. So it's not about having sort of Secret Squirrel work. It's not about having a PO that sort of hides the roadmap, like almost that they keep it held hostage and it's a negotiation to sort of be able to get access to it. Right. I guess the ultimate success measure for me is if a team calls its own behavior out before I've had to sort of raise a sort of a Dr. Spock eyebrow up on camera. Right. That they know is my sort of instance, sort of. Are you sure about that? Is that really what we want to do?

[Vasko]

So they do that, but they do that like not as criticizing, but more like have we thought about the consequences or, or maybe we should try something like that.

[Stuart Tipples]

It's that self checking, right? It's not that sort of running away because you've got a great idea and you're, you know, we all do it, right? You get excited about something and you just want to get stuck in and you want to go to do it, right? So it's almost like the success boils down to if a team does all those things while you as a scrum master are not in the room, that's your metric, success, right? When they behave that way, you're not in the room and others see it. That's when as a scrum master, it's not a role that's often celebrated, but that's a time where you can give yourself a gold star, a pat on the back or you can give yourself go get a good fancy coffee or a beer. That's when you know all that sort of thankless work, it has paid off because they are, they are living, they are living the principles and the values that you've been instilling, they are calling, they're almost imagining your voice in their heads, right? It's, you know, quite often sort of say to teams like what would Stuart say? Ask yourself that question, what would Stuart say to this then? That, that's, that's a measure of success, then if they can, if they are celebrated, they are seen and they are seen as a successful, predictable team that has credibility within an organization, within your stakeholders. That's huge. That's so hard. Even though this agile game is decades old and yet people still don't trust this approach to work despite the data to show that this will offer value, this will prove success. It will make people in your teams happier. And if you've got happy teams, then you'll be happier, awesome products will be delivered. Build that trust, show that credibility, that success. Yeah.

[Vasko]

And you said something right now that I think it's important that when we talk about happy teams, it may sound that it's like just that no problems are there, that everything is just going perfect. But that's not what happy teams look like. Happy teams look like committed individuals that want to overcome whatever problems come their way and still feel happy about their ability to do the right thing. Instead of people who never see any obstacles or any difficult moments, toxic positivity, yeah, exactly. And the ability to see an obstacle as a challenge, as something positive to build on, is what happiness means, right? It's not the ability to overlook the challenges, it's the ability to take them on and feel energized, that it's a good thing, that we can work on this, that we can become better.

[Stuart Tipples]

Imagine working in a team where, like, problems are a given, right? You are going to face challenges daily, and that will be whether it's the product you're building, whether that's the people you're interacting with, whether that's stakeholders, whether that's downstream teams. Problems are there because if we didn't, none of us would have a job. But imagine being in a team where you not only felt trusted enough that you felt you had the autonomy to take on that problem. Just imagine being in that team, right? That's a good feeling. That's happiness, right? Feeling trusted, feeling value. To the point that, you know, your manager, your line manager, whoever that sort of person is, just goes, no, no, I know. You got it exactly. Go do it. Right? That's gotta be as close to sort of happiness in the workplace as you can get.

[Vasko]

Thank you for sharing all of that with us, Stuart.

[Stuart Tipples]

No worries, no worries.

[Vasko]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, Deep Dive interviews, books, and if you're into no estimates, we got the pioneers of no estimates in those Deep Dive interviews as well. Agile business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the [e-mail] membership because listening is great, it's important. But doing it together, that's next level. I'll see you in the community. Slack we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum Masters know about this valuable resource for their work. Remember that sharing is caring.