The "Painting by Numbers" Scrum Master vs. The Quiet Leader Who Made the Team Self-Sufficient | Njegos Ilic

Summary

---

Podcast Summary:

Scrum Master Toolbox Podcast — Episode: "The 'Painting by Numbers' Scrum Master vs. The Quiet Leader Who Made the Team Self-Sufficient"
Host: Vasco Duarte
Guest: Njegos Ilic (Product Owner)
Date: May 29, 2026

---

Episode Theme

This episode explores the contrasting Scrum Master archetypes from the perspective of a seasoned Product Owner: the disengaged “by the book” Scrum Master versus the self-effacing, facilitative leader who enables deep team ownership. Through candid storytelling, Njegos Ilic illustrates actionable lessons, anti-patterns, and best practices that shape team dynamics, engagement, and value delivery.

---

Key Discussion Points & Insights

1. The “Painting by Numbers” Scrum Master: An Anti-Pattern

[01:27 – 06:34]

• Symptoms of the Anti-Pattern:

  • Scrum Masters who go through the motions—dailies, planning, reviews, retros—mechanically, with little understanding of Agile’s purpose.
  • Meetings feel like “reporting cycles”: team members merely answer scripted questions, with no real interaction, challenge, or engagement.
  • Lack of proactive facilitation leads to disengagement: “It's just reporting and capturing discussion points and action points, following up on that, which is totally fine and I think it's really important. But at the end of the day, that's really… bad.” (Njegos, 02:52)

• Consequences:

  • Product Owners (“POs”) experience isolation, left to define everything alone and lacking team feedback: “You basically feel totally alone... you have to do it, but it's much, much easier if you have that kind of connection with the team.” (Njegos, 04:11)
  • Lack of open discussion means issues and ambiguities go unaddressed until it’s too late: “Once the feature is developed, you can see there is a lot of things that could be addressed before, if there was this kind of really open culture discussions.” (Njegos, 04:27)
  • Risk of over-defining: “You're then overthinking, you're trying to define too many things because you know that's what expected. And this is also an anti-pattern.” (Njegos, 05:48)

2. Cultivating Engagement & Healthy Team Dynamics

[04:11 – 06:34]

• Feedback Loops:
  • Vital for POs and teams: “It's much easier to define things, it's much easier to work together with the team if you have that feedback. If you don't, it's really hard.” (Njegos, 04:26)
  • Workshops, experiments, and interactive approaches (with Scrum Master support) break passive cycles and help “squeeze a little bit of feedback from their head.” (Njegos, 06:00)

---

3. The Hallmarks of a Great Scrum Master

[06:34 – 09:43]

• The “Invisible” or Quiet Leader:

  • “The best Scrum Master I worked with… was invisible, kind of, you know? They knew always when to speak. They didn’t… be afraid to jump in… but they also knew when to step back.” (Njegos, 06:53)
  • Maintains meeting discipline—knows when to encourage taking discussions “offline” to keep focus.
  • Consistently “feels the pulse” of the team, experimenting with approaches and adapting to team needs.

• Keys to Credibility & Influence:

  • Deep product knowledge bolsters respect and influence: “…they really knew the product and they were respected by the team. That's probably for Scrum Masters to figure out—how to get that respect.” (Njegos, 07:26)
  • Many effective Scrum Masters were previously developers on the team, easing their transition into respected facilitation roles.

• Enabling Team Ownership:

  • Innovative practice: distributed facilitation among team members (“round-robin Scrum Mastering”), especially during onboarding periods.
    • “He basically tried to put a little bit responsibility for everyone in the team for every sprint to… facilitate some of the meetings.” (Njegos, 08:09)
  • Outcomes: Team-wide learning, resilience, awareness of the challenges in facilitation.
    • “At the end of the day, he was guiding all that, but it really helped the team.” (Njegos, 08:27)
    • “Having a Scrum Master that gives the role to the team also allows team members to actually feel how hard the role is.” (Vasco, 09:02)

---

Notable Quotes & Memorable Moments

• On the anti-pattern:

  “I've seen that... they use Scrum just as a title... They have everything from dailies, refinements, plannings, retros, reviews... but at the end of the day... they didn't understand what is the purpose of Agile Scrum.”
  — Njegos Ilic [02:01]

• On the importance of engagement:

  “It's much easier to define things, it's much easier to work together with the team if you have that feedback. If you don't have that feedback, for me, it's really hard actually.”
  — Njegos Ilic [04:26]

• On real leadership:

  “The best Scrum Master… was invisible… They knew always when to speak. They didn’t… be afraid to jump in… but they also knew when to step back.”
  — Njegos Ilic [06:53]

• On team learning:

  “He was doing this round-robin for the Scrum Masters... everyone in the team for every sprint... facilitate some of the meetings... In my personal opinion, that helped a lot.”
  — Njegos Ilic [08:07]

• On walking in the Scrum Master’s shoes:

  “Having a Scrum Master that gives the role to the teams also allows the team members to actually feel how hard the role is… It's definitely not as easy as when I only participate.”
  — Vasco Duarte [09:02]

---

Timestamps for Key Segments

| Timestamp | Segment | |-----------|---------| | 01:27 | Njegos describes the “painting by numbers” Scrum Master anti-pattern | | 03:57 | Impact on the Product Owner: isolation, lack of feedback | | 06:34 | The best Scrum Master: characteristics & impact | | 08:07 | Round-robin Scrum Mastering: team-empowering practice | | 09:02 | Reflection on learning by doing (team members facilitating) |

---

Takeaways & Toolbox Tips

• Mechanical adherence to Scrum ceremonies without focusing on engagement and purpose undermines Agile values and collaboration.
• Product Owners thrive on real feedback and shared ownership—Scrum Masters must foster open culture.
• The most effective Scrum Masters expertly balance visibility and restraint, leveraging deep understanding of the product and championing gradual team autonomy.
• Sharing facilitation roles deepens empathy, awareness, and collective responsibility within the team.

---

Where to Find Njegos Ilic

• LinkedIn: Njegos is active primarily on LinkedIn, engaging with a close professional network. (Link in episode show notes.)

---

This episode offers an unvarnished look at what truly distinguishes effective Scrum Masters—insightful for Scrum Masters, Agile Coaches, and Product Owners alike seeking to boost their practice and team outcomes.

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 rtgif. And because this is Product Owner week, this is not the PO episode, it's the Scrum Master episode. Because we have with us product owner Niegos Illich. Hey Niegos, welcome back.

[B]

Hey Vasco, thanks for having me.

[A]

Absolutely. So today is Scrum Master day on the podcast. So Scrum Masters out there, pay attention. This one is for you. So Niegos, from your perspective as a product owner, I'm sure you have some amazing Scrum Masters you've worked with. But before we dive into that, do share with us potentially the worst Scrum Master anti pattern you've witnessed in your career.

[B]

So you have really tough questions. But yeah, I think like the worst pattern that I've seen is basically, and I've seen that like I work in some companies where basically they use Scrum just as a title, you know, for, for, for some process that are working and they, they have everything like from dailies, refinements, plannings, retros, reviews, every, you know, every meeting and every, every, everything from the Scrum. But then at the end of the day you see that for example, these people who are also titled with the Scrum Master role, they're really, at least in my opinion, you know, they didn't understand what is the purpose of Agile Scrum. And basically they were just doing those different meetings just for doing those meetings, you know, and it was really, and I think it's a common pattern, I would say with, with many things. It was just reporting, you know, reporting cycle from meeting to meeting and it was just, hey, what did you, what did you do yesterday for the daily, on, I don't know, refinement. Hey, do we have questions without any, any interaction and, and you know, challenging each other. That's, that's at least for me, at least from the product owner perspective. The, the worst case scenario where you need, you know, you come to the, these different meetings and it's just like people are not engaged, you know, and Scrum Master is not working to, you know, to address this. It's more like just reporting and, you know, capturing what was the, you know, discussion points, action points, following up on that, which is totally fine and I think it's really important. But at the end of the day, that's, that's really challenging. That, that's really something that's really, I think from my perspective, really bad. It's challenging for me working in that kind of environment. I'm pretty sure there is a lot of, you know, different examples, but, you

[A]

know, so tell us a little bit more, Niegos. Why is that challenging for you as the product owner? So you were talking about the lack of engagement. What does that look like in practice and how does it affect the work of the product owner?

[B]

You, you basically feel totally alone, you know, because you are trying to deliver some value. Because at the end of the day, at least how I see it, you or you work as a team with different hats to deliver the value to work on some product, you know, and if you need, you know, to have, you know, to work everything through alone, to, you know, to define everything without anyone asking anything, then you really, in the delivery, during development and basically once the feature is developed, you can see there is a lot of, you know, things that could be addressed before if there was this kind of really open culture discussions, you know, and it can, to be perfectly fair, it can be going both ways. Because me as a product owner, you know, I don't miss a lot of things because it's much easier to define things. It's much easier to, you know, to work together with the team if you have that feedback. If you don't have that feedback. For me, it's, it's really hard actually. It's not impossible. You have to do it. But I think it's much, much easier if you have that kind of connection with the team.

[A]

Yeah, absolutely. I can imagine that. For example, the lack of engagement also creates doubt like, will this actually work? Are there problems that they are not telling me about?

[B]

Exactly, exactly, exactly. And then, you know, you're constantly trying. And I think it's also like a part of who we are. Like you're then you're overthinking, you're trying to, to define too much, too much things because you know, that's what expected. And this is also anti pattern and that's why I think that the smartest way is trying to engage people, trying to challenge them, to invite. We spoke, we spoke about that in previous episodes but basically just trying to change a little bit the focus maybe to do with them also with the help and support of the Scrum Master to do some kind of, you know, workshops, different approaches, experiments just to basically try to squeeze a little bit feedback from their head because it will be easier at the end of the day for the whole team, you know.

[A]

Absolutely, absolutely. But there aren't only bad examples. Some Scrum Masters do an amazing job and we definitely should give them a shout out here. So share with us Niegos, the best Scrum Master you've ever worked with. How did they work?

[B]

So the best Scrum Master that I worked with, basically they were invisible kind of, you know, they knew always when to speak. They didn't, they didn't, they didn't, you know, be afraid to jump in, you know, to say hey, we are on time, can we do this offline or we will do it on some another meeting. You know, this is just a small example then basically they were always trying to feel the pulse. But what we spoke also like and to basically experiment with different approaches and suggestions with the team. They were also really knowledgeable, I have to admit. They really knew the product and they were because of that, I think partially they were really respected by the team and that's the part probably for the Scrum Masters to figure it out how to get that respect, you know. But, but that was actually the best from us that I worked with. And I have to admit some of them were really before that part of the team working maybe as a, as a developers in that team. But at the end of the day they were really, you know, I use word invisible but really trying not to be, you know, there when they are not needed. But they basically try to also delegate some things to the team. I know that in one team basically we actually lose a couple of developers in one team. And basically as a part of onboarding also for the new developers, he was doing this around robbing for the Scrum Masters and he basically tried to put a little bit responsibility for everyone in the team for every sprint to get into that sho, you know, to facilitate some of the meetings to try to, you know, have different approaches to different problems. And in my personal opinion, that helped a lot. You know, at the end of the day, he was, you know, guiding all of that, but it really helped the team.

[A]

Yeah, yeah, absolutely. And when you think about it, having a scrum master that kind of gives the role to the teams, also allows the team members to actually feel how hard the role is Right when I need to facilitate the retrospective. It's definitely not as easy as when I only participate.

[B]

I don't know if this is by the guide and by the book, but at least in my humble opinion, this was really impactful in that particular team that I was working with.

[A]

Yeah, definitely a tool for our toolbox. If you ask me not to speak about wrangling this difficult product owner, sometimes, you know.

[B]

Exactly.

[A]

All right, Diego, it's been a wonderful week. We've learned a lot from the stories you've shared with us. But before we go, where can people find out more about you and the work that you're doing?

[B]

I'm really not into the social media, so I don't know. At the moment I only use LinkedIn, so I don't know. I was writing before a little bit, but lately I don't have time, to be honest. So I think people cannot actually, you know, follow my. My work that much, except from the, you know, circle that I'm, you know, with my friends and people, which I'm hanging. But that's it. Just linking for now. And then if I. If I use something else, I will let you know so you can share with the audience.

[A]

Absolutely. But we'll put the LinkedIn page in the show notes so that people can go and interact with you. Niegos, thank you very much for being here and for being so generous with your time and your knowledge.

[B]

Thank you, Vasco, for having me and inviting me. As I've said, this was really spontaneous and sorry if I couldn't provide any more examples. It was a hard week also for me. So this was really a wonderful week, though.

[A]

Hard, but wonderful. Thank you. Thank you, Niegot. 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.