When Teams Embody Agility Without Having To Thinking About It | Florian Georgescu

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches

Episode: When Teams Embody Agility Without Having To Thinking About It | Florian Georgescu
Host: Vasco Duarte
Guest: Florian Georgescu, Agile Coach and Certified Scrum Master
Release Date: August 7, 2025

---

Introduction

In this compelling episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in a profound conversation with Florian Georgescu, an experienced Agile Coach and Certified Scrum Master. The episode delves into the nuances of fostering true agility within teams, emphasizing the transformative impact of effective retrospectives and the broader definition of success for Scrum Masters.

---

Favorite Retrospective Format: The Naikan Retrospective

At the core of Florian’s insights is his favored retrospective format—the Naikan Retrospective. This Japanese self-reflection tool plays a pivotal role in his approach to team dynamics and continuous improvement.

[01:35] Florian Georgescu:
"I will tell a story about one of the retros that had the biggest impact in the teams I was working with..."

Florian recounts a critical incident where a sports betting company's system crashed during a high-stakes Champions League game, leading to significant financial repercussions. The aftermath was tense, but Florian adeptly navigated the team through the storm without assigning blame. Recognizing the unspoken tension lingering post-incident, he introduced the Naikan Retrospective to facilitate open dialogue and emotional release.

Key Elements of the Naikan Retrospective:

1. Self-Reflection Questions:

   • What have I done successfully for my team?
   • What have I received from the team?
   • How have I supported my team during difficult times?

2. Adaptation to Team Context: Florian tailored the traditional Naikan format to suit his team’s specific needs, fostering a structured yet empathetic environment.

The retrospective spanned over two and a half hours, providing a safe space for team members to express their frustrations and support needs. This exercise not only addressed the immediate issues related to the system crash but also laid the foundation for improved collaboration and quality emphasis within the team.

[03:27] Florian Georgescu:
"Naikan. It's a Japanese self reflection tool... It was a strong self reflection exercise and I was a little bit concerned that I was also new to the team and I was a little bit concerned whether the team will actually accept having this self reflection exercise. And luckily it was successful."

The long-term impact was profound, with team members reflecting on the session years later, highlighting its significance in building strong, trust-based relationships. The retrospective empowered the team to handle future challenges with resilience and mutual support.

---

Defining Success as a Scrum Master

Transitioning from retrospectives, the conversation shifts to Florian's perspective on measuring success in his role.

[07:26] Florian Georgescu:
"I know that I'm successful as a Scrum master when my team embodies agile values and principles so naturally that they barely notice they're doing it."

For Florian, success isn't about overt milestones but the seamless integration of Agile principles into the team's daily operations. He observes several key behaviors indicative of this success:

1. Autonomous Decision-Making: Teams facilitate their own discussions, understanding when and how to make decisions without constant facilitation.

2. Constructive Conflict: Members engage in healthy debates over technical solutions, ensuring that disagreements are resolved constructively, fostering innovation and teamwork.

3. Effective Communication During Reviews: Florian highlights an instance where the team’s ability to communicate effectively with leadership during a Sprint Review showcased their matured Agile practices.

[09:55] Podcast Host:
"Those behaviors are great examples of a team taking ownership of their agility, their ability to get feedback, their ability to go through problems together and come out the other hand the other end with a potential solution."

Florian’s approach underscores the importance of nurturing an environment where Agile practices flourish organically, leading to sustained team success and cohesion.

---

Host’s Reflections on Feedback and Scrum Mastery

The host, Vasco Duarte, emphasizes the often-overlooked aspect of feedback in the Scrum Master’s journey. He acknowledges that tangible feedback can be scarce, making it crucial to interpret team behaviors as indirect indicators of success or areas needing improvement.

[10:51] Podcast Host:
"We never know if it works, but we try it and then we learn. And that's the spirit we want to see."

Vasco encourages Scrum Masters to celebrate visible successes while remaining vigilant about areas that may require attention, fostering a culture of continuous growth and acknowledgment.

---

Conclusion

This episode of the Scrum Master Toolbox Podcast offers invaluable insights into the subtle yet powerful ways Scrum Masters like Florian Georgescu can cultivate agile teams that not only perform efficiently but also thrive on mutual respect and continuous improvement. Through effective retrospective practices and a nuanced understanding of success, Florian exemplifies the profound impact a dedicated Scrum Master can have on team dynamics and overall organizational agility.

For Scrum Masters and Agile practitioners seeking deeper engagement and practical tools, this episode serves as both inspiration and a practical guide to embodying true agility within their teams.

---

Notable Quotes:

• Florian Georgescu ([01:35]):
  "I need to do something so that I allow my team members to speak up to get the steam off."

• Florian Georgescu ([07:26]):
  "When my team embodies agile values and principles so naturally that they barely notice they're doing it."

• Podcast Host ([09:55]):
  "Those behaviors are great examples of a team taking ownership of their agility..."

• Podcast Host ([10:51]):
  "We never know if it works, but we try it and then we learn. And that's the spirit we want to see."

---

This detailed exploration not only captures the essence of Florian Georgescu’s experiences and methodologies but also provides actionable insights for Scrum Masters aiming to elevate their teams to embody agility inherently.

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.

[Podcast Host]

Hello everybody. Welcome to our success Thursday here on the podcast this week with Florian Giorgesku. Hey Florian, welcome back.

[Florian Giorgesku]

Hello. Hello everyone.

[Podcast Host]

So Thursday is success day and we'll talk about success in a minute. But before we go there, Florian, share with us what's your favorite retrospective format and why?

[Florian Giorgesku]

I will tell a story about one of the retros that had the biggest impact in the teams I was working with. So we were a young team. Our company created a new technology hub and obviously we were also building the team there. We also had to deliver on our roadmap and the team was young and I remember in our beginnings we messed it up really with a release. It was a sports betting company and the system crashed exactly at the beginning of a Champions League game. So it was a big financial impact. Luckily we solved it fast. I also appreciate the fact that there was no blaming involved. So it was, it went really good from, from this perspective. We had also a short postmortem discussion after, after the incident, but still, we started a new sprint afterwards. And as a Scrum Master, I could still, still cut the tension with, with, with the knife. There was something there, there was something that was not, was not spoken. And I immediately was thinking, hey, I need to do something so that I allow my team members to speak up to get the steam off. And I chose a retrospective format. I used it back then for the first time. It's the Naican retrospective.

[Podcast Host]

Repeat that. What was the name?

[Florian Giorgesku]

Naikan. It's a Japanese self reflection tool. I've adapted it a little bit to our context, but in Gerald, you Answered three questions, what have I done? Or what have I done successfully or positive for my team? How did I. What was the second question? What did I get back from the team? And how did I support my team in difficult moments? Something like this. I don't remember exactly the three questions but it was a strong self reflection exercise and I was a little bit concerned that I was also new to the team and I was a little bit concerned whether the team will actually accept having this self reflection exercise. And luckily it was successful. We had I think two hours and a half discussion. It was a relief on one side, it was successful because it allowed us to talk about what happened in that release and it allowed us to talk about kicking off test automation and making quality as a concern of the entire team, not only of the testers, but I think the biggest impact was on the human side. And this is what I also wanted in the end, on the human side because it allowed us to let the steam off to have a structured conversation around conflicts and it allow every team member to say, hey, this is where I needed your support and you didn't provide it to me. And this is how I felt. Because this didn't happen. For example, testers mentioned this because they felt pressured to release, although they received, they started to test quite late in the sprint and it was, it was super impactful for the team. And I remember that we had conversations also years after and they reminded me about this retro and how much this meant for them. It was important also because that team, starting from that moment, that team literally could, could have done everything. It managed to build so strong relationships between those team members because they were showing vulnerability, they were opening up and they appreciated this.

[Podcast Host]

That's such a beautiful story because as you said, it's not just what we talk about, it's also the consequences over time on the team. And when you have team members coming to you even years later saying how important that retro was, you know you've done something right. And maybe it wasn't the format, maybe it was the intention, it doesn't matter. At the end of the day, that's what we need to keep in mind, that a retrospective should deliver in the end an item for improvement, but also a better team. And that's an important aspect. And of course we do all of this, Florian, because we want the teams to succeed and we want to succeed as Scrum masters in helping them. So when you think about success for yourself as a Scrum master and now as an agile coach, how do you see it? How do you define success for yourself, Florian.

[Florian Giorgesku]

Very short. I would say that I know that I'm successful as a Scrum master when my team embodies agile values and principles so naturally that they are barely. That they barely notice they're doing it. In short, this is how I measure my success. So behaviors that I've seen even in this team that we were talking about is, for example, they don't need someone to facilitate their discussions when they know which are the areas where they are allowed to take decisions and what do they need in order to take decisions. I think this is one example. Then I remember also how they were arguing and how they were having conflicting discussions when they were debating technical solutions inside the team. They were really arguing about on their point of view, but this was done in a constructive way and they knew when they can let go things. And I appreciated this a lot at them. Another one was when I remember we had a leadership team joining our tribe for a Sprint review, and we did a marketplace Sprint review. And I remember very nicely how developers talked to leadership team members and to business stakeholders on their own language. I found this fascinating because there was a dialogue between technology and business, and they talked the same language. And it was really, really fascinating to see this. This is where basically I told myself, hey, Florian, you also did a good job. I realize it's not only my success here, but I know that I also have contributed to this and I was really proud about myself.

[Podcast Host]

Absolutely. And those behaviors are great examples of a team taking ownership of their agility, their ability to get feedback, their ability to go through problems together and come out the other hand the other end with a potential solution. We never know if it works, but we try it and then we learn. And that's the spirit we want to see. And I think that the last thing that you said is actually very important for us as Scrum Masters, we don't often get feedback about the work that we do. Unfortunately, that is the case. I mean, we can do a lot better there, right? Like, we can request feedback, but even if we don't, it's very important to realize that these behaviors, how people react and what we observe are feedback for us. And we want to see these behaviors. And if we don't, we know that we need to do something, but when we do, it's important to stop and say, hey, Florian, you did a wonderful job. Congrats.

[Florian Giorgesku]

Thank you.

[Podcast Host]

Thank you for sharing that, Florian.

[Vasko]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast, Agile 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.

[Podcast Host]

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.