Beyond the AI Fear—Discovering What Makes Scrum Masters Truly Irreplaceable | Mohini Kissoon

Summary

---

Podcast Summary

Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Host: Vasco Duarte
Guest: Mohini Kissoon
Episode: Beyond the AI Fear—Discovering What Makes Scrum Masters Truly Irreplaceable
Date: January 14, 2026

---

Overview

This episode explores the anxiety surrounding artificial intelligence (AI) and its perceived threat to the roles of Scrum Masters and Agile Coaches. Vasco Duarte and guest Mohini Kissoon examine not just whether AI can replace these roles, but more importantly, what aspects of Scrum Mastery are truly irreplaceable. The conversation provides practical strategies for demonstrating value, overcoming fear, and evolving the role in a changing organizational landscape.

---

Key Discussion Points & Insights

1. AI Anxiety and the Scrum Master Role (02:11–05:29)

• Many Scrum Masters and Agile Coaches are concerned that AI might replace their roles, especially for procedural tasks (generating reports, analyzing metrics, etc.).
• Mohini shifts the conversation from "Will AI replace us?" to "What are the irreplaceable human aspects of our work, and are we focusing on them?"
  • Noted as: “I think we are asking the wrong question… the real challenge isn’t whether AI will replace grandmasters or Agile coaches, but rather, do we understand what parts of our work are actually irreplaceable…” – Mohini (02:40)

2. Distinguishing Between the AI Threat and Personal Response (03:08–04:22)

• Vasco distinguishes between the possible (but abstract) threat of AI and the personal, emotional response Scrum Masters have to that threat.
  • Quote: “There is that fear about AI, and the second one is, okay, so what do we do about it?” – Mohini (04:03)

3. The Uniquely Human Value Scrum Masters Provide (05:40–06:41)

• Mohini emphasizes abilities that AI cannot replicate:
  • Reading unspoken team dynamics and tensions
  • Building trust and presence
  • Asking questions that shift perspectives
  • Adapting in real-time to emotional and organizational contexts
• She highlights the importance of evolving with the environment and proactively demonstrating the “human touch”.

4. The Role’s Definition Problem—Process vs. Impact (06:41–08:45)

• The profession’s tendency to define itself through structure and process (meetings, reports) makes it vulnerable to organizational change and AI automation.
• Vasco warns: if Scrum Masters are viewed as "meeting callers," their value is easily questioned or replaced.
  • Quote: “If the Scrum Master is set up as calling meetings for the team, then the work… may also be seen as not valuable enough.” – Vasco (07:41)
• He suggests refocusing on being a “catalyst” for team growth rather than a “structure” role.

5. Demonstrating and Measuring Value (08:45–10:30)

• Track and communicate tangible changes facilitated by the Scrum Master:
  • Team happiness and morale improvements
  • Improvements in workflow (cycle time, lead time)
  • Personal growth among team members
• Use storytelling and before-and-after metrics to make the Scrum Master’s history visible and valued.
  • Quote: “If we can show and use the element of storytelling as well to give some use cases of how we have common teams and really help around, that would be something… history that we are creating rather than being concerned about AI.” – Mohini (09:26)

6. Communication and Ally-Building (10:30–12:36)

• Continuous, proactive communication of value is essential. Don’t wait for feedback; make your value explicit to teams and leadership.
• The Scrum Master is likened to a diplomat—working through influence and building allies both inside and outside of the team.
  • Quote: “We are a little bit like a diplomat. We work through influence, so we need to have allies in the team and outside the team and we need to give them the information they need…” – Vasco (10:53)
• Mohini suggests using "champions":
  • Bring in previous team members to share their experiences and increase credibility with new teams.
  • Let allies and team members act as advocates to amplify the Scrum Master's impact.

7. Creating a Culture of Trust & Continuous Improvement (11:44–12:36)

• Rather than being agents of disruptive change, Scrum Masters should:
  • Meet teams where they are
  • Understand context before driving changes
  • Use positive testimonials from past work to build trust with new teams
  • Quote: “Sometimes this is the fear of teams as well, that Scrum Masters and agile coaches are just coming in and they're going to change everything… it's really using those people who are our allies and really using their feedback to really elevate the work that we are doing.” – Mohini (12:00)

---

Notable Quotes and Moments

• “I think we are asking the wrong question… the real challenge isn’t whether AI will replace Scrum Masters or Agile coaches, but rather, do we understand what parts of our work are actually irreplaceable…”
  – Mohini (02:40)

• “If the Scrum Master is set up as calling meetings for the team, then the work… may also be seen as not valuable enough.”
  – Vasco (07:41)

• “If we can show and use the element of storytelling as well to give some use cases… history that we are creating rather than being concerned about AI.”
  – Mohini (09:26)

• “We are a little bit like a diplomat. We work through influence, so we need to have allies in the team and outside the team and we need to give them the information they need…”
  – Vasco (10:53)

• “Sometimes this is the fear of teams as well, that Scrum Masters and agile coaches are just coming in and they're going to change everything… it's really using those people who are our allies and really using their feedback to really elevate the work that we are doing.”
  – Mohini (12:00)

---

Timestamps for Important Segments

• 02:11: Mohini introduces the AI anxiety theme and reframes the conversation
• 03:08–04:22: Distinguishing AI threat from emotional response; discussing what’s in our control
• 05:40: Mohini lists the irreplaceable human aspects of the Scrum Master role
• 06:41–08:45: Vasco critiques the structuring of the role; transition from process to impact
• 08:45: Mohini on measuring and storytelling the Scrum Master’s value
• 10:30: Vasco on proactive value communication and building allies
• 11:44: Mohini shares the strategy of using previous allies as champions in new teams

---

Takeaways

• Rather than fearing AI, Scrum Masters should focus on amplifying their uniquely human skills: empathy, intuition, trust building, and perspective-shifting.
• The key to job security and career growth is continuous demonstration and communication of value—not just to teams, but to the broader organization.
• Use data, storytelling, and ally testimonials to make the invisible impact of Agile coaching visible and organizationally valued.
• The Scrum Master role should be seen—and set up—not as a process function, but as a catalyst for positive change and team evolution.

---

For Scrum Masters and Agile Coaches: this episode serves as a practical guide to future-proofing your role by focusing on irreplaceable human value, strategic self-marketing, and continuous relationship-building in the face of organizational change and technological advancement.

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 warfree. 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 the 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 our Wednesday, the Coaching Wednesday here on the podcast. This week we have with us Mohini Kisoon. Hey, Mohini, welcome back.

[B]

Glad to be back, Lasko.

[A]

Absolutely. So, as Scrum Masters, we are constantly facing new situations. I famously say that every time you go to work, you face a new team. Maybe somebody's got a, got a bad day, maybe somebody's feeling a bit under the weather. That's a whole new team right there compared to yesterday. And when we face these different situations, of course, sometimes they feel like challenges. And challenge is not a bad thing. It is an invitation to grow. And that's what we want to talk about. And at the same time, model what is a coaching conversation so that our listeners can get a real life example of how we could go about exploring a topic together. So this week, what do you have in mind for us to explore together, Mohini?

[B]

Well, I'm currently wrestling with a challenge that's coming up repeatedly in conversations with other Agile coaches and Scrum Masters. And that's around the anxiety around AI and what this means for our role. And to be honest, it's many, many other roles as well. But we focus on our role and I'm hearing questions like will AI replace Scrum Masters or Agile Coaches? And for me, what makes it interesting is that I think we are asking the wrong question. I think the real challenge isn't whether AI will replace grandmasters or Agile coaches, but rather, do we understand what parts of our work are actually irreplaceable and whether we are spending our time on those things to further demonstrate our value yeah.

[A]

So I hear kind of two aspects here that I think are quite separate. One is the eventual possibility of whatever AI system, present or future, to do similar work to what a Scrum Master does. Right. Like that's just if you could say that's an abstract conversation. Right. Like it needs to become true in some way. It isn't necessarily true yet, or at least not in all cases. And then the other kind of thread of the conversation is, how does this land with me? How does it land with me? The possibility that an AI or a set of AIs or a system that includes AI and other things might be able to do similar work to the work that I do today? For me, these are two separate conversations. Do you agree? How do you see that?

[B]

Yeah, it is different. The first bit is there is that fear about AI, and the second one is, okay, so what do we do about it? What can we do about it? What is within our control? So would you want to address the first bit?

[A]

Yeah, whichever you decide to go with first.

[B]

I think the fear is there and it's for more than our role. It's great, greater, but it's also in terms of how we interpret it, how we see it in a world where we're living in fast growing AI. So we need to make sure that we are evolving around it as well. And Scrum Masters and Agile Coaches need to be evolving with the environment that we are in. Because if you look at it currently, a lot of the roles that we have, even roles which are on the market, it's always something which is a mixture of Scrum Master or ba or they. It's not really a role that they think is a priority, it's a catalyst role. Yes, but it's always something that if we have to revisit the structure of an organization, that might be some of those, that might be one of the roles that they would.

[A]

So are you saying, in other words, that the way Scrum Master role is set up today is problematic even without AI?

[B]

It depends how the team sees it as well. And with AI, it just makes things even more difficult because people might have the impression that with AI, AI can generate Sprint reports, could analyze team metrics, and so why do we need Scrum Masters or Agile Coaches for that? So what I feel that what's missing here is that the human touch that Scrum Masters and Agile Coaches can bring, an example is the value that we can bring is reading the room and sensing unspoken tension, building trust for presence as well, and also asking questions that might help to Shift perspectives. So these are things that we need to further build upon and then see what else can we do to further show our value rather than, yeah, AI is here, so what do we do now?

[A]

And being anxious about it, I totally see that. Let's call it the challenge of demonstrating value, right? Like, that's a very important aspect. Because it's not enough that we believe that we bring value, others need to believe too, right? Starting with a team, that's the most obvious, but then also continuing with the rest of the organization. And in fact, one of the topics that you addressed was when there is a reorganization, right? Like whether through redundancies or shift in priorities or whatever, then it's very easy to drop the role of the Scrum Master. And I think that this points to a different, different problem than AI. Of course it's affected by AI, but in my mind, it points to the idea that the way the Scrum Master role is set up does not actually bring value. It may bring structure, which may have value, but the moment the structure changes, then the need for the structure that the Scrum Master brings is also changing, maybe higher or lower. And if it's lower, that's an easy answer, right? Like, I've worked with ctos that basically said I don't need anyone to call meetings for my teams. They should be able to call meetings for themselves. And when you hear that, you can't disagree. Like, that's an obvious yes, of course. But if the Scrum Master is set up as calling meetings for the team, then the work that they bring, which is valuable, may also be seen as not valuable enough. Right. So what I'm thinking is, have we accidentally in our community defined a role about the process and the structure, rather than the impact on the team? Because I don't think that the Scrum Master role was originally created or thought of as a structure role. I think it was more of a catalyst role. How do you see that?

[B]

Yeah, I think it's definitely a catalyst role, which is often misunderstood. And like you said, like, sometimes other people might be seeing, like just setting up meetings and all that, but it's up to the Scrum Master to prove that you know, what the. What are the value that you're creating. And they can make the use of metrics for that they could show before they joined the team, how was the team happiness, and just kind of see how they are going to measure it over time, how it has changed the moral, the energy in the team as well, and also in terms of the flow of the work. Itself has it improved using different metrics like the cycle time, the lead time as well. So there are different ways that we, we can still show the value that we are bringing and also how we have helped people to grow in their roles as well. So shifted some. If there were some developers who wasn't sure how to integrate in the team. So now they are very much comfortable in how they are in the team and they're working well and they are very confident in presenting the work which was different before. So if we can show and use the element of storytelling as well to give some use cases of how we have common teams and really help around, that would be something that a history that we are creating rather than being concerned about.

[A]

AI, I like what you said. I like that aspect of creating history, showing the before and after. And I would add to that the idea that it is our job to communicate that all the time. It's not the team's job to say, hey, you're a great Scrum Master. It's our job to show, here's what I'm doing for you, here's what I'm doing for your team. Dear manager or leader that we interact with. And I think that this is an important aspect. We are a little bit like a diplomat. And in that, I mean we are not the president, we are diplomats, we are, we work through influence. Right. So we need to have allies in the team and outside the team and we need to give them the information they need to continue to support the work that we're doing. And if we don't have that, if we don't have the ability to show the value, then of course the natural consequence is that the role would disappear. And it has in many organizations indeed disappeared. So I think that those two aspects, everything that you said, plus we need to recognize that the value that we bring needs to be seen by others. It cannot be just existing, it needs to be seen and recognized by others.

[B]

Yeah. And also use those people as champions. Like what I've done in the past is if I'm setting up a new team, I would bring someone from my previous team who I've worked with and to share their experience and to share what were some of the things, how they felt when we were changing the ways of working, how we work together and how we preferred to meet the team where they are, understand their current circumstance rather than just coming in and making changes. Because sometimes this is the fear of teams as well, that Scrum Masters and agile coaches are just coming in and they're going to change everything. So I think it's really using those people who are our allies and really using their feedback to really elevate the work that we are doing.

[A]

That's a great addition. Thank you for sharing that. Mohini.

[B]

Welcome.

[A]

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.