The Silence Test — How to Know Your Team Doesn't Need You Anymore | Mirco Gerling

Summary

Scrum Master Toolbox Podcast: The Silence Test — How to Know Your Team Doesn't Need You Anymore

Guest: Mirco Gerling
Host: Vasco Duarte
Date: July 16, 2026

---

Episode Overview

In this engaging episode, Vasco Duarte welcomes back Mirco Gerling to discuss what true success looks like for Scrum Masters—specifically, how to recognize when your team is self-managing to such a degree that they no longer need you. They explore practical signals of self-management, the importance of authenticity as a Scrum Master, and essential retrospective formats to foster continuous improvement. The conversation is filled with concrete examples, candid advice, and actionable strategies for Scrum Masters aiming to “work themselves out of a job” by empowering their teams.

---

Key Discussion Points & Insights

1. Mirco’s Favorite Retrospective Format

[01:42 – 04:17]

• Mirco’s Go-To Tool: Mirco prefers “liberating structures” for retrospectives, particularly for larger groups, because they involve everyone and require minimal preparation if you're familiar with the methods.
• Real-World Example: Mirco shares a story from the Agile by Nature camp in Germany, where he co-facilitated a retrospective for 60 people in just 20 minutes using Liberating Structures—proving its scalability and effectiveness.
• Adapting to Context: Mirco mentions facilitating retrospectives in a Hamburg park during the pandemic, making use of outdoor settings and transitioning between locations, maintaining engagement.
  • Quote:

    “We moved from one station in the park to another, to the lake to have some ice cream. And later we returned and it was a very good and constructive retrospective.”
    — Mirco Gerling [03:43]

2. Mirco’s Definition of Success as a Scrum Master

[04:28 – 08:58]

• Be Authentic: Mirco emphasizes that new Scrum Masters should find their own style and avoid copying others.
  • Quote:

    “They should be authentic and they should be their self. Every Scrum Master has its own style, I think.”
    — Mirco Gerling [04:49]

• Implement the Scrum Guide: Success means striving to live the Scrum values and facilitate all Scrum events—especially retrospectives, even pushing teams to hold them in the Scrum Master's absence.
• Artifacts & Feedback Loops:
  • Ensuring clarity in the Product Backlog and Sprint Backlog.
  • Focusing on commitments like Product Goal and Sprint Goal.
  • Stresses the importance of Definition of Done for increments.
• Feedback Loops Must Not Be Broken: Emphasizes the significance of continuous improvement cycles: Sprint Review feedback impacting the Product Backlog, and Sprint Retrospectives driving ongoing team development.
  • Quote:

    “…for me it’s important that we don’t break the feedback loop… There’s an arrow from the Sprint review to the product backlog. That is one feature loop for me that shouldn’t be broken. And another feedback loop is from the Sprint retrospective to ensure that we get a continuous improvement in the team.”
    — Mirco Gerling [07:27]

3. Signs Your Team Is Self-Managing

[08:58 – 10:25]

• Observing Independence: The clearest indicator is when Scrum events (Daily, Planning, etc.) happen without the Scrum Master’s presence or prompting.
• Personal Example: During time off for paternity leave, Mirco’s team maintained all Scrum practices independently—proof of success.
  • Quote:

    “It was nice for me to see that they are still working in the same way, they didn’t cancel the meetings or the Scrum events.”
    — Mirco Gerling [10:00]

4. The “Stepping Back” Strategy

[10:25 – 13:08]

• Letting the Team Take Ownership: Vasco describes intentionally stepping back—e.g., “forgetting” to send invites or not preparing for retrospectives—to test what the team takes responsibility for, highlighting their priorities and level of self-management.
  • Quote:

    “If we step back, we see what’s really important for the team because they will not drop the things that they feel are important…”
    — Vasco Duarte [11:11]

• Mirco’s Approach: Prefers to wait and let others propose solutions, only stepping in as necessary and mostly guiding with questions instead of directives. Early in his career, he found it challenging to resist making decisions for the team but now insists on shared decision-making.
  • Quote:

    “I sometimes are waiting if another person has a good idea and in most cases they have a better idea than I had. And that’s my strategy, not to talk too much… I prefer to ask questions instead of giving commands.”
    — Mirco Gerling [11:34]

  • Quote (on “mirko management”):

    “To help the people in self management and not to make micromanagement, e.g., mirko management in this case, right?”
    — Vasco Duarte [13:06], Mirco Gerling [13:08]

---

Notable Quotes & Moments

• On Retrospectives and Authenticity:

  “That’s my message. Be authentic and be yourself.”
  — Mirco Gerling [04:53]

• On Success Without Presence:

  "My goal is that the team is making or performing a retrospective even if I’m not working, if I’m having holidays or something. And that means success for me too."
  — Mirco Gerling [05:51]

• The Value of Stepping Back:

  “Self management starts with very basic steps, right? Like owning the things that are important for us.”
  — Vasco Duarte [10:43]

---

Timestamps for Key Segments

| Timestamp | Topic | |-----------|-----------------------------------------------------------------------| | 01:42 | Mirco describes his favorite retrospective formats and real examples | | 04:28 | Mirco explains his personal definition of Scrum Master success | | 07:27 | Importance of unbroken feedback loops and continuous improvement | | 08:58 | Vasco asks about signals of team self-management | | 10:25 | Discussion about stepping back and observing team priorities | | 11:34 | Mirco explains his strategy: asking questions, resisting micromanagement | | 13:06 | Vasco’s quip on “mirko management” |

---

Takeaways for Scrum Masters

• Liberating structures are powerful, especially for large group retrospectives or when flexibility is needed.
• Team independence is the clearest sign of Scrum Master success—when all Scrum events and practices happen without the Scrum Master’s involvement.
• Be authentic: Develop your personal Scrum Master style and avoid simply imitating others.
• Don’t micromanage: Use silence and open questions to let the team solve their own problems.
• Test self-management: Step back occasionally to see what the team owns and sustains on their own.

---

Final Thoughts

The “silence test” and stepping back as a Scrum Master are signs of true growth—not just for the team, but for Scrum Masters themselves. If your absence is barely noticed because the team carries on with energy and discipline, you’ve succeeded.

---

Transcript

[A]

Hey there, Agile adventurer, just a quick question.

[B]

What if, for the price of a

[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.

[B]

Hello everybody.

[A]

Welcome to our success Thursday.

[B]

This week we have with us Mirko Gerling. Hey, Mirko, welcome back.

[C]

Thank you. It's a great honor for me to be on your show and we're very

[B]

happy you're here with us this week. And for those who haven't, check out yesterday's episode, I'm sure you will find it insightful. But now let's dive into the Thursday questions and we'll talk about success for Scrum Masters in a minute.

[A]

But before that, share with us.

[B]

Mirko, what's your favorite agile retrospective format and why?

[C]

That's a little bit difficult because I have several favorites, but my universal tool is to use liberating structures to, to involve everybody, especially in large groups. And there's nearly no preparation needed. If you, if you have experience with the, the modules or of the parts of the liberating structures or the methods, it's very easy to make a spontaneous retrospective. And about two years, no, three years ago, I had the great honor in a bar camp that we have had in the north of Germany, the Agile by Nature camp, they asked, who can make a fast retrospective with 60 people? And we have half an hour. And later they said, oh, we made a mistake, we only have 20 minutes. And, and another lady and I, we said, okay, we will try it with liberating structures. And we terminated exactly in the time box of 20 minutes with 60 people. And we used the 1, 2 for all module or I don't remember the name.

[B]

Structure.

[C]

Structure. Yes, the structure. Yeah, you know, it was a very good experience and especially in the times of the Pandemic due to the coronavirus. We had the problem. The challenge in the summer sometimes in the north of Germany, in HAMBURG, we have 30 degrees Celsius. And in this time we didn't prefer to sit inside the building with a face mask. And we had the idea to make the retrospectives outside in the park. And I used the liberating structures too. And we moved from one station in the park to another, to the lake to have some ice cream. And later we returned and it was a very good and constructive retrospective.

[B]

Yeah, absolutely.

[C]

Outside, definitely.

[B]

Liberating structure is something everybody should have in their back pocket. I'll put the link in the show notes for people to go and check it out.

[A]

But Mirko, of course we do this

[B]

retrospectives because we want to succeed and help others succeed. So let's do a reflection on that. Share with us what's your definition of success for yourself as a Scrum Master?

[C]

Yeah, yeah. First, I want to say for new Scrum Masters, I say to everybody who wants to make or to work as a Scrum Master that the people don't have to try to copy another Scrum Master or something. They should be authentic and they should be their self. Every Scrum Master has its own style, I think, and it's not a good idea to. To do a workshop or something if you feel don't feel good with, with the content or something. Therefore I, I. That's my message. Be authentic and be yourself. Yeah. And in my case, for me it's important to, to be successful Scrum Master. For me it means that I, I try to implement the Scrum Guide like the Scrum Guide says from 2020, the scrum values. But this is a long process. But I try to implement the Scrum values, the Scrum events, they are very important for me. Sometimes the people say ah, the retrospective we can cancel or something. But I say no, we have to make the retrospective. And my goal is that the team is making or performing a retrospective even if I'm not working, if I'm having holidays or something. And that means success for me too. If the team is working or continues with the self management. If the Scrum Master is not present, that's success for me. They are working on their own or they are not only doing the ceremonies for the Scrum Master. And the last years the Scrum artifacts became more important for me to ensure that we have a product backlog is clear and a sprint backlog, but the commitments that relate with the product backlog, the product goals. Sometimes I observe that the Teams are working on a product but they don't have a product goal. And that is important for me to ensure that we have a product goal, a Sprint goal, and especially that for the increment we have a definition of done that ensures that we have the same quantity and we are referring to the Scrum guide for, for me it's important that we don't break the feedback loop. There are some pictures from scrumpunk.scrum.org where you see that there's an arrow from the Sprint review to the product backlog. That is one feature loop for me that shouldn't be broken. And another feedback loop is from the Sprint retrospective to ensure that we get a continuous improvement in the team. And therefore I'm asking in every retrospective what happened. To the things that we committed or the tasks that we committed in the last retrospective?

[B]

One thing, Mirko, when you think about the team self managing and kind of this self management has been a topic we discussed several times this week. So obviously it's an important topic. What are kind of the signs you look for, the hints, the behaviors, the things that the team does that tell you that yes indeed they are climbing up on their self management ladder?

[C]

For example, that I don't have to attend every meeting or Scrum event if the planning or the daily Scrum is working without me, without the Scrum Master, I see that the self management is working. These are some examples. And yeah, I sometimes I've not been working for two months because I have a little daughter and it was nice for me to see that they are still working in the same way they didn't cancel the meetings or the Scrum events. Say that was nice for me.

[B]

One thing I would say is that as we step like as we work with the teams, we can step back. Like we can, for example, forget to send the Sprint review invitation or forget to prepare for forget in quotation marks to prepare the retrospective and then see, oh, who would like to facilitate today? Or how about facility, somebody facilitating the retrospective tomorrow. What I'm thinking of here is that this self management starts with very basic steps, right? Like owning the things that are important for us. And what I'm thinking is if we step back, we see what's really important for the team because they will not drop the things that they feel are important for them. Right. So what do you think about that kind of strategy tool approach that would allow us to see is the team really understanding why these ceremonies or these tools or these techniques are there?

[C]

Yeah, in my case I prefer for example in discussions or if there's a problem, not to answer. As the first person, I sometimes are waiting if another person has a good idea and in most cases they have a better idea than I had. And that's my strategy, not to talk too much and only talk if it's necessary, or to send some signals or ask questions. I prefer to ask questions instead of giving commands. I remember that the first time when I was working as a Scrum Master, sometimes the people said, oh Merkob, you have to decide. You are the Scrum master. And it was hard work for me to say no, we decide together. And this is my way of working and. To help the people in self management and not to make micromanagement e.g.

[B]

mirko management in this case, right?

[C]

Yes, yes.

[B]

That's a great kind of technique as well, right? Like no, we decide together what's important for you, what's important for you. Let's discuss the options. So very practical. Thank you for sharing that with us, Mirko.

[C]

Yeah, you're welcome.

[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 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.

[B]

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.