The Almost Invisible Scrum Master, Why Team Independence Is the Ultimate Success Metric | Iryna Stelmakh

Summary

---

Podcast Summary: Scrum Master Toolbox Podcast

Episode: The Almost Invisible Scrum Master – Why Team Independence Is the Ultimate Success Metric
Guest: Iryna Stelmakh
Host: Vasco Duarte
Date: March 26, 2026

---

Episode Overview

In this Success Thursday episode, host Vasco Duarte interviews Agile coach and Scrum Master Iryna Stelmakh to explore what genuine success looks like for Scrum Masters. The conversation highlights the value of team independence, the ideal of an "almost invisible" Scrum Master, and effective retrospective formats that focus on both technical and human aspects of team performance. The episode is rich with practical insights, real-world examples, and actionable advice for Scrum Masters striving to empower their teams.

---

Key Discussion Points & Insights

1. Retrospectives: Beyond Technical Tasks

[01:17 – 07:21]

• Iryna’s Favorite Retrospective Format – The Energy Retrospective

  • Instead of focusing only on tasks and technical issues, Iryna emphasizes retrospectives as critical for trust-building and real change.
  • The "energy retrospective" centers on the questions:
    • What gave us energy in this sprint?
    • What drained our energy?
    • What should we start, stop, or continue to maintain our energy?
  • This format surfaces human dynamics and emphasizes overall team well-being, not just work output.

  Quote (Iryna Stelmakh, 02:02):

  “...instead of focusing only on tasks problems... we ask three simple questions: What gave us energy for this sprint? What drained our energy? And what should we start, stop, or continue doing for keeping our energy on the right level? This approach helps teams talk about real human dynamics and not only about technical issues.”

• Adapting Retrospective Formats to Team Needs

  • Iryna describes tailoring approaches depending on team maturity and openness:
    • Established teams: Structured, open conversation with approaches like Lean Coffee or dot voting (online/offline).
    • New or hesitant teams: Use metaphoric approaches, e.g., asking team members to select images (such as expressive monkeys) that represent their feelings or evaluation of the sprint.
  • The metaphor approach makes it easier to surface honest feedback when direct conversation is challenging.
  • The Scrum Master’s responsibility is to create a trust-based environment, adapting facilitation style to team culture and dynamics.

  Quote (Iryna Stelmakh, 06:17):

  “For teams with a high level of resistance... I used a metaphoric approach. I shared pictures and asked them to pick the one they saw as appropriate about their feelings or the process... With a picture of a happy or sad monkey, I was able to get information from them, when it was hard to get it directly.”

2. Defining Success for Scrum Masters

[07:21 – 09:50]

• Success = Team Independence and Ownership

  • Iryna’s definition of a “successful Scrum Master”:
    • “Almost invisible” — not due to absence but because the team is independent and not reliant on the Scrum Master for daily decisions.
    • The process runs well with or without the Scrum Master present, indicating systems and behaviors are deeply integrated.
    • The team:
      1. Takes ownership of delivery
      2. Solves problems collaboratively (especially important for distributed and cross-functional teams)
      3. Continuously improves its processes, with every member empowered to propose changes

  Quote (Iryna Stelmakh, 08:14):

  “A successful Scrum Master is almost invisible... not because the Scrum Master doesn’t contribute, but because the team is no longer dependent on the Scrum Master for every decision. ...The whole system, the whole process will work correctly with or without you.”

  Quote (Iryna Stelmakh, 08:54):

  “When that happens, the Scrum Master becomes more of a system observer and catalyst rather than a daily driver. That’s the point of extension for the Scrum Master as well.”

• Extending the Definition: Looking Beyond the Team

  • Vasco reframes and builds on Iryna’s definition, highlighting the Scrum Master’s central role in connecting team, Product Owner, and stakeholders.
  • Success should be evaluated in terms of interactions, relationships, and overall system health, not just the team’s internal behavior.

  Quote (Vasco Duarte, 09:58):

  “We are not looking at just how we measure it for us, we’re also looking at what are the behaviors around us... it would make sense also to consider that from the Product Owner perspective, for example, from the stakeholder perspective during reviews... Scrum Master role is a role that is at the nexus of many different interactions.”

---

Memorable Moments & Notable Quotes

• Iryna’s perspective on Scrum Master “invisibility”:

  • “A successful Scrum Master is almost invisible... the team is no longer dependent on Scrum Master for every decision.” (08:14)

• Energy Retrospectives focus on human dynamics:

  • “What gave us energy for this sprint? What drained our energy? ...This approach helps team talk about real human dynamics and not only about technical issues.” (02:02)

• On facilitating trust and adapting formats:

  • “For the other teams, new teams, or the teams with a high level of resistance... I used a metaphoric approach.” (06:17)

• Vasco on broadening Scrum Master success:

  • “It might be really about the relationship between the PO and the team, or like you mentioned, specific team behaviors and so on.” (10:14)

---

Timestamps for Important Segments

• [01:17] – Iryna introduces the “energy retrospective”
• [04:12] – Discussion about adapting retrospective formats depending on team culture and maturity
• [07:54] – Iryna defines her view of Scrum Master success: “almost invisible,” team independence
• [08:54] – The Scrum Master as a system observer and catalyst
• [09:50] – Vasco’s reflections on broadening the definition of Scrum Master success

---

Episode Takeaways

• Retrospectives should prioritize both technical progress and team well-being.
• The hallmark of Scrum Master success is when the team thrives independently, making collaborative decisions and driving its own improvements.
• Adjusting facilitation and fostering trust are key to healthy dynamics, especially in new, resistant, or complex teams.
• True Scrum Master success encompasses not just the team, but also positive relationships with Product Owners and stakeholders, acting as a catalyst and observer rather than a controller.

---

Listen to This Episode If…

• You want practical ideas to design retrospectives that energize your team
• You’re looking for an inspiring benchmark of Scrum Master success
• You care about team autonomy and building a lasting agile culture
• You want to hear real wisdom from a Scrum Master “in the trenches”

---

Quotes are attributed to Irina Stelmakh (B) and Vasco Duarte (A) with corresponding timestamps for authenticity and context.

Transcript

[A]

Hello everyone. Quick heads up before we start today's episode. The Global Agile Summit is happening on May 4th. Yes, May 4th. And even with a big blowout Star wars party, you have to join. It will be online and it's like always free to attend. We have four tracks this year that I'm really excited about and I think you will too. Stick around to the end of the episode to know what they are. If you want to check it out already now you can check it out at bit ly globalagile 26. That's the numerals 2 and 6 at the end. So one more time, that's bit ly globalagile 2, 6, all one word, all lowercase and 2 and 6 are the numerals 2 and 6. So stick around till the end of the episode and I'll tell you what's in store. But for now, on to today's episode. Hello everybody. Welcome to our Thursday success Thursday that is. And this week we have with us Irina Stellmak. Hey, Irina.

[B]

Hi guys.

[A]

Welcome back.

[B]

Thank you, Bosco.

[A]

So Thursday is of course success Thursday. So we'll talk about success for Scrum Masters in a minute. But before that, Irina, share with us what's your favorite agile retrospective format and why?

[B]

Oh, I'm in love with retrospectives because this is the place where you could bring everything, everything for the improvement and if you know how to set up, might be the most, you know, the most important probably place for the trust building and for the change, for the change management, let's say like that. And here I'm talking about the facilitation on the retrospectives. And one of my favorite retrospective format is something that I call energy retrospective. Because each of one knows that if you're a Scrum master, you have like questions for the retrospective, like what went good, what went not so good and what we should improve, right? And instead of focusing only on tasks problems, because yes, that's important, but still we have something else. We ask three simple questions. What gave us energy for this sprint? What grained our energy? And what should we start, stop or continue doing for keeping our energy on the right level? This approach helps team talk about real human dynamics and not only about technical issues. Because you know, yes, to close the technical tasks, to resolve the technical issues is important, but also it is important a human being and the wellness of your team. And this is something that you could check within the retrospective format and peer to peer meetings.

[A]

So tell us a little bit more about that. So one of the reasons why we asked this question is because very often what happens that we have learned that a certain retrospective format has an impact on the teams that we work with. It could be because it's just who they are, personality or temperament issue. It could be because in that context, right, like in the type of conversations or narratives, that retrospective format works better. A very simple example is some people prefer very structured and always the same retrospective format, while other people prefer very open and always different retrospective formats. Why does this format work well in your mind?

[B]

You know, I guess this is actually the approach depends on the Scrum Master and on the team's that Scrum Master has to serve. You know, because then I had many teams with different needs and few teams were just very easygoing. For us, retrospectives were the place where we could come, we could talk. And I didn't have any borders with those people. I could just ask them their opinion, like what was bad, what was good, what you want to improve. Let's discuss this. Usually I use the lean coffee approach or the dots voting using miro or mural depends, right? So it was very easy or having the offline work doing this dot voting on the board with stickers or with something else with markers. But depends on team because sometimes I had the team whom it was pretty hard to talk about and the new teams, for example, on the stage of forming where you are not the trust like trusted person for them, not yet. So you have to ask them from different perspectives to receive this answer. Because like we were talking on our previous podcast, part transparency is about everything, right? So it's important for the Scrum Master to create the right environment with a trust based like trust based environment. So as a Scrum Master you could know, you could get those answers for your from your team to be able to manage that answers and to convert them somehow to the right actions or, or changes, whatever else. That's why for the other teams, new teams, or the teams with a high level of the resistance or with the high level of complexity, talking about some negative, let's say things, I did another approach. I used them again, the mirror board or the mural or the whiteboard, but I was using them. Metaphoric approach. And I shared with them like some kind of pictures and I asked them to pick the correct picture they see as the appropriate one about their feelings or about the process evaluation during the current sprint. And within the picture with a happy monkey or with a sad monkey or with a tired monkey or with another way of characteristic monkey, I was able to get the information from them. You know, in case if it was hard to get it directly.

[A]

Yeah, I like that focus on adjusting the format to the teams and also the situation that the team is in. So really important. Also because of the next question. Because we want to be successful by helping these teams and we need to be able to adapt as one. But there are many ways to look at success as Scrum Master. So Irina, we're interested in your way. How do you define for yourself success in the Scrum Master role?

[B]

This is one of my favorite question. Vask. I have one phrase in Ukrainian, but now it's not even a joke due to the war. It's pretty hard to say that Scrum Master is good when he is like a dad. Scrum Master because the context is not the correct one. But that's why I would like to say a successful Scrum Master is almost invisible. Not because the Scrum Master don't contribute, but because the team is no longer dependent on Scrum Master for every decision. As a Scrum Master, you have to set up and to monitor, control and serve. But being almost invisible means that the whole system, the whole process will work correctly with you or without. This is the result of the great work of the Scrum Master. And for the team, success means like, takes ownership of delivery, solves problems collaboratively. Because we have distributed team, we have cross functional team. Right. And continuously improves its own process. Each one from the team, each team member could say, could vote, could propose something. And this is very important again to build the right environment with a high level of trust so your teammates could execute those three points listed before. And when that happens, the Scrum Master becomes more of a system observer and catalyst rather than a daily driver. And this is the point of the extension for the Scrum Master as well.

[A]

Yeah, absolutely. What I really like about this say this perspective, right, Is that we are not looking at just how we measure it for us, we're also looking at how we, what are the behaviors around us. And you mentioned the team and I would think that it would make sense also to consider that from the product owner perspective, for example, from the stakeholder perspective during the reviews. I really like that approach because Scrum Master role is a role that is at the nexus of many different interactions, right? Like there's many interactions that are facilitated by the work that we do. And just as you described, it's so important to have that perspective that as Scrum Masters we need to be looking at all of these directions and assessing what are the gaps, of course, but also how do we look at this in A way that defines our interaction with them, our success in helping them. For example, it might be really relationship between the PO and the team or like you mentioned, specific team behaviors and so on. So thank you for sharing that.

[B]

Welcome, Vaskun.

[A]

Hi there friends. Thanks for sticking around till the end of the episode. So let me tell you what's coming on May 4th. We're running the Global Agile Summit. It will be online and I want you there this year. We have four tracks and each one is built around real conversations with practitioners. No slides, no keynote theater, just honest interviews with people doing the work, just like you. The first track is AI in Organizations where practitioners show what actually works. No hype, just AI that makes your Monday better. Happy Monday, everybody. And then we have the people track honest conversations about putting humans at the center of how we work and keeping them there. And third is Agile in Construction. And yes, I really mean brick and mortar construction. Lean and agile. Actual job sites. Field leaders removing waste. Teams transforming how buildings get built. Stay tuned for what I think will be a super track on Agile in construction. And the fourth track is Agile in Gaming. How game Studios Ship without Burning out Agile Inside the Creative Pressure Cooker. Over the years, we've had more than 12,000 participants since 2017, the time of the first summit organized with the podcast. And this year we're making it easier than ever to join. You can register for free and get access to the summit sessions live during the event week. That's May 4th to May 6th. Or you can grab the Practitioner Pass and get immediate access to last year's keynotes from Jurgen Apollo Gojkoadi and Mirete Kangas right now, even before the Summit starts. So grab your Practitioner Pass and start learning today. Head on over to Bitly GlobalAgile 26. That's 2, 6. The numerals 2 and 6 sign up and I'll see you on May 4th. And one more time, here we go. Bit Ly. GlobalAgile 26. All lowercase, all one word and 26. That's the numeral 2 and the numeral 6. I'll see you on the conference floor.