From Resistance to Effective Change Leadership in Agile Adoption | Florian Georgescu

Summary

Scrum Master Toolbox Podcast: Episode Summary

Title: From Resistance to Effective Change Leadership in Agile Adoption | Florian Georgescu
Host: Vasco Duarte
Guest: Florian Georgescu
Release Date: August 6, 2025

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Florian Georgescu, a seasoned Scrum Master and Chapter Lead, to discuss the intricacies of leading effective change within Agile adoption. Florian shares his personal journey from initial resistance to embracing and implementing standardized Agile practices across a multinational organization.

Florian's Initial Resistance to Standardization

Florian begins by recounting his role within the organization as both a Scrum Master and later as a Chapter Lead. When the leadership team decided to standardize Agile methodologies company-wide, Florian initially felt a strong resistance.

Florian Georgescu [03:02]: "I took pride in continuous improvement and fostering team creativity. Initially, I felt a very strong resistance to this change. My immediate concern was that it would stifle innovation and turn our Agile practice into a rigid process-driven framework."

His apprehensions were not only professional but also personal, as he had invested significant time and energy into cultivating effective Agile practices within his team.

Understanding the Bigger Picture

As Florian transitioned into the Chapter Lead role, his perspective broadened. He began to see the challenges faced by teams in different locations and cultures, each interpreting Agile practices uniquely. This disparity highlighted the necessity for a common framework to ensure cohesive collaboration across the organization.

Florian Georgescu [04:34]: "The organization was spread across multiple locations and cultures. Different teams were speaking different Agile languages. For example, Sprint planning meant something completely different for one team compared to another."

Marsko Duarte, the co-host, emphasizes the importance of a common language in Agile practices:

Marsko Duarte [05:50]: "Collaboration does not emerge if we don't speak the same language, if we don't have a similar way to interact with people outside the team."

Developing a Solution: The 80/20 Principle & Three-Level Framework

To address the fragmentation, Florian and his team adopted the 80/20 principle for standardization, focusing on the 20% of practices that would yield 80% of the cross-team alignment and value. They implemented a three-level framework to balance standardization with team autonomy:

1. Non-Negotiable Standards (Level 1): Essential practices that every team must follow, such as working in sprints and conducting sprint ceremonies.

   Florian Georgescu [08:35]: "Having the same sprint length, consistent ceremony names, and basic reporting metrics were our starting points."

2. Recommended Practices (Level 2): Proven patterns that teams are encouraged to adopt, like specific story-splitting techniques.

   Florian Georgescu [09:57]: "We recommended practices that had shown success, such as our story splitting techniques."

3. Team-Specific Innovations (Level 3): Allowing teams the freedom to experiment and adapt practices that best fit their unique contexts.

   Marsko Duarte [10:00]: "This framework gives space for innovation while maintaining essential standards."

Additionally, the Scrum Master chapter facilitated the sharing of successful innovations among Scrum Masters, promoting organic spread and continuous improvement across teams.

Outcomes and Effective Change Leadership

The implementation of this structured yet flexible framework enabled better alignment across diverse teams, fostering enhanced collaboration and consistent Agile practices. Florian reflects on the transformation:

Florian Georgescu: "We needed to ensure that all teams, regardless of location, could deliver value efficiently and cohesively."

By standardizing key elements while preserving room for innovation, Florian effectively led the organization through a successful Agile transformation, mitigating resistance and enhancing overall productivity.

Key Tools, Tips, and Techniques Florian Applies Today

Throughout the episode, Florian shares several actionable insights and techniques that have been instrumental in his journey:

• 80/20 Standardization: Focus on the most impactful practices to achieve significant alignment.
• Three-Level Framework: Balance mandatory standards with recommended practices and team-specific innovations.
• Cross-Team Communication: Establish a common Agile language to facilitate better collaboration.
• Community of Practice: Utilize the Scrum Master chapter to share knowledge and support continuous learning.

Conclusion

Florian Georgescu's story is a testament to the importance of thoughtful change leadership in Agile adoption. By recognizing and addressing resistance, understanding the broader organizational needs, and implementing a balanced framework for standardization, Florian successfully navigated his teams through effective Agile transformation.

For Scrum Masters and Agile Coaches seeking to enhance their change management strategies, Florian's experiences offer valuable lessons on fostering alignment without compromising team autonomy and creativity.

---

Notable Quotes:

• Florian Georgescu [03:02]: "I felt a very strong resistance to this change. My immediate concern was that it would stifle innovation and turn our Agile practice into a rigid process-driven framework."
• Marsko Duarte [05:50]: "Collaboration does not emerge if we don't speak the same language, if we don't have a similar way to interact with people outside the team."
• Florian Georgescu [08:35]: "Having the same sprint length, consistent ceremony names, and basic reporting metrics were our starting points."
• Florian Georgescu [09:57]: "We recommended practices that had shown success, such as our story splitting techniques."

Transcript

[Vasko]

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.

[Marsko]

Hello everybody. Welcome to our Wednesday the Change Leadership episode this week with Florian Georgesku. Hey Florian, welcome back.

[Florian Georgesku]

Hey Marsko.

[Marsko]

So Wednesday is the change episode. I like to call it Change Leadership because we don't push change, we just help change emerge as we discussed already on the Monday episode. So great story on Monday episode, everybody. Check it out if you want to have another perspective on change. In that case, the impact on Scrum Masters when change doesn't go well. Florian has a great story about that. So take a look at that Monday episode. But let's dive into this Wednesday episode. Florian, tell us the story of a change process and how did that get started? What were the ideas that were behind that change then also how did it progress? What were the key steps, the things that really made a difference in that change process? And as you tell us that story, highlight for us the tools, the tips, the tricks and the techniques you learned back then that you still apply today.

[Florian Georgesku]

Yes. So I will tell you a story in which I was involved. So a change process again for me.

[Marsko]

With which in what role were you in that change process?

[Florian Georgesku]

I was in a Scrum Master role and then the Scrum Master chapter lead role. It was when the leadership team of our company decided to standardize the agile ways of working in the entire company.

[Marsko]

Oh my God. Standardized. I already see how that is going. But let's see, let's see. Maybe this is a good story. Tell us the story, Florian.

[Florian Georgesku]

Well, as a Scrum Master, that I was dedicated to my craft, right? And I took pride in continuous improvement and fostering team creativity. Initially I felt a Very strong resistance to this change. And my immediate concern was that it would stifle innovation and turn our Agile practice into a rigid process driven framework. And this is the very opposite of what Agile should be. I remember I was thinking, how can I maintain team autonomy and creativity if we are all forced to do the same thing? And it wasn't just a professional concern, it was also deeply personal because I invested a lot of time and energy into developing those effective practices in my team. However, once I became created a Scrum Master chapter and I started also to look at the bigger picture in our.

[Marsko]

Work, what does that bigger picture mean? Now that you are in this story.

[Vasko]

In the Scrum Master chapter lead role.

[Marsko]

What did the big picture mean for you?

[Florian Georgesku]

At that time, the organization was spread in multiple locations, multiple countries, multiple working cultures. We were in that chapter, I think 12 Scrum Masters. Then is when I saw or I began to understand the leadership's point of view. There were teams in the organization that were struggling with agile ways of working. They were struggling even with basic Agile implementation. We were working or the structure of the organization was in a way that we had to work together to deliver something valuable, end to end to customers. There was cross tribe, because we were splitting in tribes, there was needed cross tribe collaboration. We had different teams even speaking different Agile languages. What meant for one team, Sprint planning meant something completely different for another one. So I understood then that yes, we needed somehow to have a common ground.

[Marsko]

This is actually a great point that you're making because one of the things we don't often talk about here on the Change episode is the importance of having a common language. For example, if we talk about Sprint planning, Sprint review, daily retrospective, those are standard terms. Now you can implement this in many different ways. There's not only one way to do a Sprint planning, but the sprint planning as a term has a meaning, right? Like from a process perspective, you have inputs, you have the actual event, and then you have outputs, right? And that language needs to be understood similarly, not exactly the same, but similarly across the whole organization. And so I totally understand your change of mind because when you start seeing the reality that one team has sprint planning, the other team doesn't have Sprint planning. One team has a sprint review, the other team doesn't even have sprints. Like when you see that diversity, you start to understand, hey, we're not even speaking the same language, right? Especially in a remote, well, not a remote international setting. You know, the importance of always speaking the same language, whatever that is, French, Italian, German, English, Portuguese, whatever That language is. But can you imagine teams speaking Italian, Chinese, German, English and never really translating that? It would be impossible to get anything done in an organization like that. And I think that your point is really important. When you see that the language isn't even the same, then you have something to solve for.

[Florian Georgesku]

Exactly, exactly. And this is what happened because I only saw my tribe in my location and there things were going well and also received the feedback for it. But then when I've learned how things are done in other locations, right then I realized that hey, we need to do this together. It's not about having only good teams or teams that work in a way in one location. The other teams also need this. The other teams also need to grow and have this satisfaction.

[Marsko]

How did you start that move, let's say towards a closer, perhaps not exactly the same, but a closer way of working for all of these teams.

[Florian Georgesku]

So we started with some principles in mind and the first One was this 8020 principle for standardization. So we started to standardize 20% of the practices that create that 80% of cross team alignment. Yeah. Value.

[Marsko]

So you mean 20% of the practices that create 80% of the alignment.

[Florian Georgesku]

Exactly. Yes. Oh, it's different. Okay, no worries. So this mean for us, meant for us in the beginning having the same spring length, having the same, having consistent ceremony names, having some basic reporting metrics. Then we've implemented a three level framework. It was level one where the non negotiable standards, these are the essential practices that every team should follow. These were mainly working in sprints. So working in sprints, having these sprint ceremonies. So those things that are essential for every squad. Then the level 2 were the recommended practices, meaning that had proven patterns teams are encouraged to adopt. For example in the creation of the backlog, use this story splitting technique.

[Marsko]

Splicing. Yeah.

[Florian Georgesku]

Then we had the level three, the team specific innovations. We still gave space for the teams to experiment and adapt. And then we used the Scrum Master chapter to share these innovations between the Scrum Masters first so that we can learn from each other, but also support in spreading organically these practices that have proven to be successful for some teams.

[Marsko]

Absolutely. I really love that 3 level of standardization. Of course it supports this 8020, but it also gives people an understanding. Hey, these things you must have, like if you're using Scrum, you must have a sprint, you must have a sprint planning, you must have a product or, or whatever that is. Right. And that creates the commonality that enables the collaboration. Because that's one of the things we don't often talk about, right, like collaboration does not emerge if we don't speak the same language, if we don't have a similar way to interact with people outside the team. Right. So it's a great framework of these three levels, the non negotiables, the encouraged practices, and then the space for innovation. Great stuff. Thank you for sharing that with us, Florian.

[Florian Georgesku]

Thank you so.

[Vasko]

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.

[Marsko]

Dive interviews as well.

[Vasko]

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.

[Marsko]

I'll see you in the community. Slack.

[Vasko]

We really hope you liked our show.

[Marsko]

And if you did, why not rate.

[Vasko]

This podcast on Stitcher or itunes.

[Marsko]

Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.

[Florian Georgesku]

Sam.