Why Great Scrum Masters Create Space for Breaks | Scott Smith

Summary

Podcast Summary: Scrum Master Toolbox Podcast

Episode: Why Great Scrum Masters Create Space for Breaks | Scott Smith
Date: December 2, 2025
Host: Vasco Duarte (Agile Coach, Certified Scrum Master, Certified Product Owner)
Guest: Scott Smith (Certified Scrum Master, Agile Coach)

---

Episode Overview

This “Team Tuesday” episode explores the importance of creating space for breaks and constructive interventions during team conflict. Scott Smith, an experienced Scrum Master, shares insights from his agile journey, highlighting how the supportive influence of strong management can inspire career transitions and how Scrum Masters can de-escalate conflict within teams by creating space for reflection. The discussion offers actionable techniques for resolving heated situations and refocusing teams on their shared goals.

---

Key Discussion Points & Insights

1. Career Inspiration and Support for Change

• Scott Smith’s Transition to Scrum Master:

  • Scott’s career shift was catalyzed by the support of a former manager who inspired and believed in him.
  • Having workplace backing (including an MBA opportunity paid for by the employer) and the space to grow made a crucial difference.
  • "[My manager] gave me the space and the time to do the things that I wanted to do to achieve that transition to Scrum Master. That really inspired me to run with it and take that opportunity." (03:15, Scott)

• Lesson: Strong managerial support can be transformative in helping individuals pivot to new roles.

2. Recognizing and Managing Team Conflict

• Scenario Overview:

  • Scott recalls a product owner new to their role whose abrupt and terse demeanor led to a heated exchange in a team meeting.
  • Early signs of conflict included raised voices, signaling escalating tension.

• Scrum Master’s Intervention:

  • As a facilitator, Scott intervened decisively when the conflict became vocal.
  • He reminded the team of their shared purpose and encouraged understanding each other's perspectives.
  • Importantly, he recommended a pause: "Let's take this back a step and let's quieten things down a bit and understand each other's perspectives and really come back to… understanding. We're both on the same team." (06:14, Scott)

• Outcome:

  • The intervention led to immediate de-escalation.
  • The product owner later expressed gratitude, acknowledging the value of the interruption and the reflection it prompted.

3. Tactical Approaches for Scrum Masters

• Creating Space for Breaks:

  • Scott advocates for calling a break or pause when passions run high, emphasizing that stepping away helps parties calm down and prepare for constructive dialogue.
  • "First of all, stop what's going on, ask for a break if needed… get them back to a level playing field... comfortable going back into the conversation." (08:55, Scott)

• Refocusing on Shared Goals:

  • Both Vasco and Scott highlight shifting the conversation from personal disagreements to what the group is trying to achieve collectively.
  • Vasco suggests: "Helping each part describe what they are trying to achieve, not what they are trying to do ... because once we start looking at what does success mean, what’s the outcome, we start to see commonalities." (10:07, Vasco)
  • Scott echoes: "It is really about... focusing on what is the outcome that we're all trying to achieve here." (11:17, Scott)

• De-personalizing Conflict:

  • By focusing on objectives rather than personalities or past actions, tension dissipates and collaboration resumes.

---

Notable Quotes & Memorable Moments

• On Managerial Support:

  • "Having someone who believed in me and they were supporting me ... gave me the space and time to do the things that I wanted to do to achieve that transition to Scrum Master." (03:15, Scott)

• On Intervening in Conflict:

  • "As a facilitator in those sessions, I took the opportunity to jump in and, you know, say to the guys, listen up, we’re on the same team here. We’re looking for the same outcomes." (06:14, Scott)

• On Creating Space for Resolution:

  • "First of all, stop what’s going on, ask for a break if needed... back to a level playing field where they’re comfortable going back into the conversation..." (08:55, Scott)

• On Returning Focus to the Goal:

  • "It is really about... focusing on what is the outcome that we’re all trying to achieve here… takes the sort of heat out of any conflict that might have arisen." (11:17, Scott)

---

Timestamps of Key Segments

• 01:39 — Scott shares how mentorship and support sparked his Scrum Master journey
• 05:20 — Scott describes a real-world conflict in a team meeting
• 06:14 — How Scott stepped in to de-escalate and create space for pause
• 08:55 — Scott explains his process for preparing to intervene in team conflict
• 10:07 — Vasco discusses the value of focusing on intended outcomes
• 11:17 — Scott highlights the power of taking personalities out and refocusing on shared goals

---

Takeaways for Listeners

• Supportive leadership is vital in nurturing Scrum Masters and encouraging personal growth.
• Recognize early signs of conflict, and don’t hesitate to pause a heated discussion—creating space can be transformative.
• As a facilitator, focus teams on what they aim to achieve rather than differences in methods or personalities.
• Clear communication, empathy, and a shared vision can turn moments of tension into opportunities for greater collaboration.

---

This episode provides practical advice for Scrum Masters on navigating team conflict, emphasizing the role of breaks, reframing conversations, and fostering a supportive environment for growth and collaboration.

Transcript

[A]

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.

[B]

Hello everybody. Welcome to our team Tuesday. This week joining us we have Scott Smith. Hey Scott, welcome back.

[C]

Hey Vasco, thank you for having me join you.

[B]

Absolutely. It's a pleasure to have you. And of course, today's team Tuesday. We'll talk about teams in a second. But before we dive into that, Scott, share with us, what was the book that most influenced you in your career as a Scrum Master?

[C]

Maybe not a book, but more so I think person who I saw in a role that really inspired me to become a Scrum Master. This individual was an ex manager of mine before when I was a business analyst. And they really had inspired me to chase my goals and be what I wanted to be. And after 10 years of being a BA, I had gotten to the point where I was, I suppose, ready for a change. I had done an MBA and found that I was really interested in, you know, that avenue of change management. So I had decided to take my PSM1 and go down that course and then look for opportunities within my workplace to start to practice Scrum Mastery.

[B]

What was the aspect in that person that really inspired you to chase your goals? Because I think that's an amazing and powerful story. Right? Like we all have people in our lives that at some point had had an influence on us and whatever choice we might make in the end, whether it's career or private or personal or anything. But what was that aspect that really made you think that, okay, this is something I can do?

[C]

I think it was really having someone who believed in me and they were supporting me as well in that transition. So being my manager and having that support and someone who I could go to and they would give me the space and the time to do the things that I wanted to do to achieve that transition to Scrum Master. That really inspired me to run with it and take that opportunity. These opportunities don't come along all the time, so it was really, I think, grab it whilst it was there. And things kind of aligned up for me in that whilst I was with this manager I'd applied for through the workplace that I was working, I'd applied to do my mba and that happens, but the workplace actually paid for it. So it was an additional, suppose, added bonus to me pursuing my goals to be a Scrum Master was having. Having that paid for by the. By the workplace and going through that four years and then I moved on to do the PSM one in the end and yeah, took it from there.

[B]

I think it illustrates how important it is to have the right managers in our career and the influence that they can have. Definitely a great story now, talking about managers, or maybe not. Let's see how the story goes on Tuesdays. We also want to explore the story of a team and how sometimes teams create their own problems, Scott. And here we want to hear about what were maybe some behavior, some patterns, some interactions that maybe started small in the beginning, but eventually grew and became a problem for that team. So tell us that story, Scott.

[C]

Yeah, I can recall one squad that I worked with and the product owner. They were new to the role and I think on this one occasion we're in a meeting with the team. Can't remember if it was Sprint Review or Sprint Planning or something, but the product owner was really short and sharp with their tone of voice and there was a bit of conflict between the product owner and the team.

[B]

Conflict emerged. Like as you were observing it, what were the signs of that conflict?

[C]

Well, the signs were there were raised voices on both sides and so the.

[B]

Discussion ran high, clearly.

[C]

That's right. Yeah, they did. They were heated. And as a facilitator in those sessions, I took the opportunity to jump in and, you know, say to the guys, listen up, we're on the same team here. We're looking to for the same outcomes. So let's take this back a step and let's quieten things down a bit and understand each other's perspectives and really come back to, you know, understanding. We're both on the same team. We're not trying to fight with each other for different things. So it was really helping that product owner who was a bit maybe keen to get things done in their way rather than working collaboratively with the team, bringing it back into perspective for them to ensure that they did it amicably and they had no sort of ongoing conflict or heated discussions. They really thanked me afterwards as well, actually, for stepping in and telling. Having. Having them take that break in that conversation, which really, I think hit hard for the product owner as they. He probably realized, you know, it was his attitude and behaviors that were probably not suitable at that point in time.

[B]

So when you think about that, of course, the conflict kind of became obvious when people started shouting at each other, obviously, right? But it does take courage to step in. And of course, it takes a certain amount of, how do you say, preparation. Because it's not just about stepping in. It's about knowing what to do and how to follow up and what might be a step, Positive step forward rather than increasing the conflict and maybe getting embroiled in the conflict ourselves. So when you think about that kind of situation, when you're observing that conflict and then you want to step in, and then, you know, how do you prepare that? Like, what are the things in your mind as you start to step in and also as you present the way forward for the team and the P.O. in this case, you said that you asked them to take a break and have a conversation, but of course, that conversation also needs to be facilitated. So how do you prepare yourself for this kind of intervention?

[C]

My approach to these types of conversations and interventions is really to think about the people involved. You know, there's people on both sides there, but there's obviously a difference in opinion, perspectives, and it's really about putting yourself in the shoes of the other. So I try to take the approach where, first of all, stop what's going on, ask for a break if needed, and, you know, speaking to individuals to have them, you know, back to a level playing field where they're comfortable going back into the conversation with the other party without the need for raised voices, heated sort of discussions, so that they can be working together collaboratively without any sort of ongoing undercurrents in the conversation.

[B]

One of the things that when I think of this kind of situation, right, like you're bringing people together, even if it is a team and a PO in this case. So it's not just two people, it's like a group, right? You're bringing people together to talk about something difficult. The conflict is there because there's something difficult. Otherwise we would handle the conflict without conflict. One of the things that I often think about is to start from the perspective of helping each part describe what they are trying to achieve, not what they are trying to do, because that would be the task and that's where the conflict is right now, the task, but rather what they are trying to achieve. Like what would be success for them and asking it in that kind of positive thing. Because my intuition at least is that once we start looking at what does success mean, what's the outcome we're looking for, we start to see commonalities. Right? And that's where I start to where I try to start the conversation. How about you? When you go into this kind of situation, what is something that you bring in to help people come together despite the conflict?

[C]

I think you're spot on there. And it is really about taking the people thing out of it and personalities out of it. It's really about focusing on what is the outcome that we're all trying to achieve here and focusing on that outcome as opposed to he said that or she said this. So really peeling it back to together, what is it we're trying to achieve and what is that outcome really takes the sort of heat out of any conflict that might have arisen and takes the focus back to the goals that people are trying to achieve.

[B]

Yeah, absolutely. And the goals are really important. It's a great story. Thank you for sharing that with us. Scott.

[A]

Alright, 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, 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] because listening is great. It's important. But doing it together, that's next level.

[B]

I'll see you in the community. Slack.

[A]

We really hope you liked our show.

[B]

And if you did, why not rate.

[A]

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.