When Proactive Help Backfires - A Gen Z Scrum Master's Learning Journey | Irene Castagnotto - Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Summary5 min read

Episode Overview

Theme:
In this episode, Vasco Duarte talks with Irene Castagnotto, a Gen Z Scrum Master from Italy, about the challenges of being proactive as a young Scrum Master—especially when offering help to others backfires. Irene shares her unique journey into Agile, the dynamics of generational perspectives in the workplace, and a powerful fail story illustrating the nuanced role of a Scrum Master in facilitating—not forcing—change.

Key Discussion Points & Insights

1. Irene's Unusual Path to Scrum Mastery

Irene discovered Agile as a teenager through her father's involvement in the community.
As a 15–16-year-old, she attended Agile events out of curiosity and found the fun, collaborative spirit inspiring.
Her experience shaped her desire to help her generation approach work with “confidence and serenity.”
A pivotal internship with Italian Agile coach Marco Calzolari set her on the professional path.

Quote:
"I would see these people that were older than me working but having fun at the same time. So that's what amazed me."
—Irene Castagnotto, [02:26]

2. Backgrounds in Agile—and the Value of Youthful Curiosity

Vasco notes that many join Scrum Master roles from varied backgrounds, but Irene is the first he’s met who started in her teens.
The two discuss how professionals discover Agile, often as a refreshing alternative to older, exhaustion-inducing processes.

Quote:
"I think that you are the first teenager Scrum Master that we've ever had on the podcast. So, kudos to you."
—Vasco Duarte, [04:41]

3. Fail Story: When Proactive Help Backfires

The Situation

Irene, motivated by curiosity and a desire to help, witnessed Product Owners (POs) struggling with role changes. Although not directly asked, she proactively offered facilitation support.

The Misstep

Despite initial acceptance, Irene realized her agenda for change didn’t match the POs’ readiness or priorities.
Her questions pushed the group faster than they were willing or able to go.

Quote:
"I tried to help them understand which changes were good, which changes weren't good...But in the end, when we tried to do this meeting and also when we faced the management, I understood that the changes that I wanted to apply weren't the changes that the PO wanted to apply."
—Irene Castagnotto, [07:28]

The Realization

The POs shut down in meetings, giving minimal responses despite prior informal complaints.
Irene understood that seeing a problem as an outsider doesn’t mean insiders are ready to act.

Quote:
"I did that step that was wrong. Because in the end my help was not helpful. I was just putting questions, asking questions that they didn't want to face at the moment, or they did not feel ready."
—Irene Castagnotto, [08:23]

4. When to Step Back and Facilitate

Vasco highlights how these moments teach Scrum Masters that people won’t adopt change until ready, even if needs are apparent from outside.
Irene recounts shifting her approach—moving from driver to facilitator. Instead of pushing topics, she started the conversation by asking what the POs wanted to discuss.
The resulting conversation produced a small, more relevant change—showing progress happens at the team’s pace.

Quote:
"I did a step back and I said to them, okay, is there something that you would like to speak about? And they started talking about something a little bit different that was connected, but it was a step behind, not a step forward."
—Irene Castagnotto, [10:07]

5. Role of the Scrum Master: Guiding, Not Forcing

Both Irene and Vasco stress that the Scrum Master’s job is to create space for others to lead their change.
Recognizing your perspective is always partial and external—what’s obvious from the outside may not be actionable or welcome to those inside.

Quotes:
"We can't tell others what they need to do. We can help them realize what they need to do, but they need to realize it."
—Vasco Duarte, [11:29]

"I have to realize that some problems, I can see them, but not all the people can at that moment see and actually understand the problem."
—Irene Castagnotto, [12:10]

Notable Quotes & Memorable Moments

"Of course you don't have to push changes. But at the moment I was like, guys, you are not in a good situation, can I help you?"
—Irene Castagnotto, [08:43]
"Not even the people who want to change are always able to change."
—Vasco Duarte, [11:24]
"Dealing with seeing the problem and dealing with the problem."
—Irene Castagnotto, [12:34]

Important Timestamps

01:23 — Irene's introduction and Agile origin story
06:17 — Fail story: When helping isn't helpful
09:32 — Realizing misalignment with team readiness
10:07 — Switching to a facilitative stance: “What do you want to talk about?”
11:01 — Vasco's reflections on facilitation, resistance, and change
12:10 — The outsider’s perspective vs. insider readiness

Summary Table

| Timestamp | Topic | Key Points / Quotes | |-----------|--------------------------------------------|----------------------------------------------------------| | 01:23 | Irene's background and Agile journey | "I was just having fun and discovering new things." | | 06:17 | Fail story: proactive help | "My help was not helpful...they did not feel ready." | | 09:32 | The moment of realization | POs silent; agenda mismatch | | 10:07 | Irene shifts to facilitator | "Is there something that you would like to speak about?" | | 11:01 | Vasco on change & resistance | Not forcing, but enabling team-led change | | 12:10 | Perspectives: inside & outside the team | "I can see them, but not all the people can..." |

Takeaways for Listeners

The Scrum Master’s role is to facilitate rather than direct change—people will change when they’re ready.
Pushing your own agenda, however well-intended, can backfire.
Stepping back and asking what the team wants to discuss builds trust and enables sustainable progress.
An external perspective is valuable, but humility and patience are critical.

This episode offers a candid and insightful look at the learning curve all Scrum Masters face, especially those early in their journey or eager to help. Irene’s story is a relatable lesson on the importance of timing, listening, and genuine facilitation in building effective, autonomous teams.

Loading summary

Transcript17 lines

[00:04]
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.
[01:12]
B
Hello everybody. Welcome to one more week of the Scrum Master Toolbox Podcast. And this week, joining us from beautiful Italy is Irene Castagnotto. Hey Irene, welcome to the show.
[01:23]
C
Hi. Hi, how are you?
[01:26]
B
I'm good, thank you for asking. So let me tell you a little bit about Irene. She's a self titled Gen Z Italian Scrum Master, began her agile journey at a young age with a positive and passionate approach. She aims to help her generation navigate the world of work with confidence and serenity while supporting teams in unlocking their full potential. And that's a job definitely that needs to be done, Irene. So that was a short intro. Tell us a little bit more about yourself and how did you end up becoming a Scrum Master?
[02:00]
C
Well, that's a funny story actually, because it was very natural because I am very young, as you said before, and thank you for the beautiful words that you just said. But when I was younger then now I was a competitive dancer and at some point I stopped because a lot of reason and I was bored. So basically one day I was talking with my dad, which actually works in the Agile world, and he was doing a lot of events in the weekends, connected to the Agile and I was like, okay, dad, I'm bored, can I come with you? And I was like 15, 16 years old. He was like, yes, of course. So that's the first time I met the Agile World actually. And I was very enthusiastic because I would see this people that were older than me working but having fun at the same time. So that's what, what amazed me at the moment. And I started being Go started going with him to the event, starting meeting people and, and that actually led to a lot of meeting a lot of people that actually were then useful in my journey. And I'm very grateful about because then I went to the university and I was doing management. But at that time I didn't know that I wanted to be a Scrum Master. I was just doing weekend with my dad and doing also sometimes daughter and dad bounding moment. So it was basically it I was just having fun and discovering new things. But then when I was in the university I was doing management and I saw like there was this project manager program. So I was like, okay, let's see what it is. And then I discovered that from project management there is Agile connected and also the Scrum Master role. So that's why I understood I wanted to be a Scrum Master and thanks for the events that I was going to. When I was little, I met Marco Calzolari, which is one agile coach that work in Italy and I did an internship with him. So that's basically where it all started.
[04:27]
B
So you started very young, first just as a curiosity, and then decided that hey, maybe this is something for me. And it's interesting how all of us come to this profession with quite different backgrounds, right? Like some people come from engineering, there's a lot of us that come from engineering, some people come from all kinds of other areas and industries and then find out that actually Scrum Master is a calling. And I think that you are the first teenager Scrum Master that we've ever had on the podcast. So kudos to you. And you never know how you find these professions, right? Like the professions we end up being in for many years in our lives. But this is a very interesting story and I'm also interested in how you put together immediately this concept of working hard but having fun at the same time, right? Because a lot of us who have been in the profession for a long time, we noticed that shift. We noticed when software development was painful and filled with problems and impossible to stand with. Long days and even weekends working without stopping. And then the discovery of Agile that for many of us was a little.
[05:42]
A
Bit like you described, the discovery of.
[05:44]
B
Having fun and working at the same time. So I'm interested in here the question, sorry, the answer you have to the next question, which is of course the fail story. Because no matter how old we are, when we start doing something, we end up failing at it. Not because we're bad, but just because we're learning, right? And that's an important step, an important growth step for all of us. So, Irene, tell us that story of a difficult moment you had as a Scrum Master. We'll dive into the takeaways and the tips later, but tell us that story first.
[06:18]
C
So the moment I had was very difficult to stand by. There were actually two moments, but both of them because I was new to the world of work, basically. So I'm always be very curious and very proactive. But this time, wasn't that my favor? It wasn't doing me a favor being very proactive. Because then it was this time that the POS were actually having some changes in their role. And I was looking from behind these kind of changes, but always thinking, but they are not happy. They are struggling with that. But they didn't ask me to help them. And I decided that it was time to ask and offer myself to give them an help to be a facilitator of this story. Which actually ended in. Of course they were very excited about it. They accepted. And I tried to help them understand which changes were good, which changes weren't good. How can we deal with the management, understand if we can propose something different. But in the end, when we tried to do this meeting and also when we face to the management, I understood that the changes that I wanted to apply weren't the changes that the PO wanting to apply, because they were not at the moment that they really realized what, what. What was happening. Because of course I can see from, from an external point of view, but they are living in an internal side of the topic. So that's when I understood that I did that step that was wrong. Because in the end my help was not helpful. I was just putting question asking, asking questions that they didn't want to face at the moment, or they did not feel ready. Maybe they knew that this was the point, but they were not asking me to help them. So this is one story where I actually understood, okay, you don't have to push changes, you have just to guide them. And it's very stupid if I think about it, because of course you don't have to push changes. But at the moment I was like, guys, you were not in a good situation. Can I help you?
[08:49]
B
Actually, that's a very good story for us to explore the real role of the Scrum Master, because as you said, we shouldn't be pushing changes. People will take on the changes that they feel ready to take on, right? And of course we're looking at it from the outside and we see things differently and maybe we also have different priorities. Many of the priorities we have are not necessarily spoken out loud, and that may cause conflict. So I want to concentrate on that moment when you realized that the changes you wanted to happen were not the changes that the POs wanted to happen. When you realized that, how did you react? Like, what was your reaction at that moment?
[09:32]
C
Well, I realized that when we were in this meeting and they were not speaking up, so I was asking question and also I was bringing up topics and they were like, okay, that's fine for me. I don't have anything to add. And I was like, but yesterday I wasn't of course, saying it out loud, but in my mind was like, but yesterday at the coffee, I listened to you. You were saying that you didn't like it. So why you are now saying that for you it's okay. And maybe it was because they were. They didn't want to actually do actual changes because they were not ready to do it. They need some time to understand what was happening. So I did a step back and I said to them, okay, is there something that you would like to speak about? And they started talking about something a little bit different that was connected, but it was a step behind and not a step forward. So that led us to make a small change. But it wasn't the change that I was expecting. But I asked them, what do you want to talk about? Because I'm here for a reason. Because we all agree that these changes could be difficult for you to understand, to deal with. And also, maybe you don't want them, some of them, or you'd like some and some not. So this basically was it. I did a step back.
[11:02]
B
Yeah, that's actually a great point. Because when we do that step back, we allow others to take the lead. And that from a change perspective, that's very important. Because we can't tell others what they need to do. We can help them realize what they need to do, but they need to realize it, right? Like the way I usually put it is that not even the people who want to change are always able to change. So you better start from the perspective that they want to change, because if you don't, then obviously they will resist it. Right? Like what we usually talk about, that change brings resistance is because the people don't want those changes. And I want to highlight that, that kind of solution, if you will, that you applied at that time, which is to step back and ask, okay, but what is it that you want to talk about? Right? And I think that's very important for us as Scrum masters to do that, step back, open the discussion again and let people come up with those topics that are the changes they are ready to take on. Right?
[12:03]
C
Yeah, that's true. Totally true. And sometimes it's this, this is a mistake that I did, but I think it's because sometimes I have to realize that some problems, I can see them, but not all the people can at that moment see and actually understand the problem. And that's because of course, I'm kind of external, because it's not fluid dynamic. I'm external, but I have eyes to look from the outside. So that's the point. Dealing with seeing the problem and dealing with the problem.
[12:38]
B
Yeah, absolutely. And I think that's a very good point. We have to open up the space. They know what they need to change. We have a different perspective. We're not the ones doing their work right. They need to be the ones bringing it up. That was a wonderful story. Thank you for sharing that, Irene.
[12:55]
C
Thank you.
[12:58]
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 talk, 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, 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 details@scrummastertoolbox.org membership because listening is great, it's important. But doing it together, that's next level.
[14:47]
B
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.