Knowledge Hoarding and Team Dependencies | Anamaria Ungureanu

Summary

Detailed Summary of "Knowledge Hoarding and Team Dependencies | Anamaria Ungureanu" Episode

Podcast Title: Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Host: Vasco Duarte, Agile Coach, Certified Scrum Master, Certified Product Owner
Guest: Ana Maria Ungureanu
Release Date: July 29, 2025

---

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Ana Maria Ungureanu, an experienced Scrum Master, to discuss a critical issue plaguing many agile teams: knowledge hoarding and team dependencies. The conversation delves deep into how seemingly minor behaviors within a team can escalate into significant obstacles, ultimately hindering project delivery and team cohesion.

---

Inspirational Book: "Never Split the Difference" by Chris Voss

Ana begins the discussion by sharing a book that profoundly influenced her approach to Scrum Mastery:

Ana Maria Ungureanu [01:52]: "One book which I love a lot and inspired me, I think you'll be surprised, is by Chris Voss. Never Split the Difference. As Scrum Masters, we need negotiation skills, empathy, and trust, which are foundational for team dynamics."

Ana emphasizes the importance of negotiation and empathy in fostering a trusting environment, essential for effective team collaboration. She highlights how the book equips Scrum Masters with techniques to navigate tense situations diplomatically, ensuring that team members feel heard and valued without imposing solutions.

---

The Problem: Knowledge Hoarding and Team Dependency

The core of the episode revolves around a real-life scenario Ana encountered with a software development team:

Ana Maria Ungureanu [06:55]: "I faced a situation with a team of seven members where initially, everyone was engaged and committed. However, one senior member began to disengage, missing sessions and becoming a bottleneck for the team’s progress."

This senior team member's reluctance to share knowledge and collaborate effectively created a dependency that stalled the project's delivery. His absence and lack of engagement underscored a critical anti-pattern: relying heavily on a single individual, which poses significant risks to team performance and project timelines.

---

Retrospective Analysis: Identifying the Bottleneck

During a retrospective meeting, the team grappled with finger-pointing and blaming, a common initial reaction to such challenges:

Ana Maria Ungureanu [09:13]: "We assessed what was happening and realized that having a single point of failure was detrimental. The senior member wasn’t aligned with the principles of code ownership and sharing, which are vital for team success."

The retrospective served as a turning point, allowing the team to step back and objectively analyze the root causes of their dependency issues. They identified the need for T-shaped skills—team members possessing deep expertise in one area while being versatile enough to collaborate across different domains.

---

Implementing Solutions: Sharing Sessions and T-Shaped Skills

To address the identified problems, Ana and her team implemented several strategic actions:

1. Enhancing Knowledge Sharing:

   Ana Maria Ungureanu [09:55]: "We introduced sharing lessons learned and incorporated the importance of a sharing mindset into our working agreements."

2. Peer Programming: They adopted peer programming sessions to facilitate real-time knowledge transfer and collaboration among team members.

3. Dedicated Learning Sessions: Specific sessions were scheduled at the end of planning meetings to focus on knowledge and information sharing, ensuring that all team members were well-versed in different aspects of the project.

4. Engaging Management: Ana worked with management to emphasize the importance of developing T-shaped skills within the team, allowing members to acquire expertise beyond their primary roles.

---

Overcoming Resistance: Building Trust and Motivation

A significant challenge was overcoming the reluctance of the disengaged team member to participate in sharing initiatives:

Ana Maria Ungureanu [12:48]: "Initially, there was intense resistance. The person wanted to maintain their current way of working. However, by proposing small trials and being open to iterative approaches, we were able to gradually shift their mindset."

Ana focused on building trust and demonstrating the personal benefits of knowledge sharing:

Ana Maria Ungureanu [15:34]: "When I ask for someone's help, it increases their trust in me and fosters a healthier, more organic connection within the team. It's not about forcing practices but about collaboratively finding what works."

She highlighted the importance of presenting sharing initiatives in a way that aligns with individual motivations, making it clear how participating benefits each team member personally. This approach not only mitigated resistance but also encouraged a more collaborative and supportive team environment.

---

Key Takeaways and Lessons Learned

• Importance of Negotiation and Empathy: Effective Scrum Masters must hone their negotiation skills and cultivate empathy to navigate team dynamics successfully.

• Avoiding Single Points of Failure: Relying heavily on one team member can jeopardize project delivery. Fostering a culture of knowledge sharing and T-shaped skills is crucial.

• Strategic Retrospectives: Retrospective meetings should focus on identifying root causes rather than assigning blame, enabling teams to implement meaningful changes.

• Building Trust Through Motivation: Understanding and aligning with individual motivations can significantly enhance team collaboration and trust.

• Iterative Approach to Change: Introducing changes gradually and being open to feedback can facilitate smoother transitions and higher adoption rates within the team.

---

Conclusion

Ana Maria Ungureanu's experience underscores the critical role of proactive knowledge sharing and the dangers of team dependencies. By implementing strategic actions and fostering a culture of trust and collaboration, Scrum Masters can mitigate risks associated with knowledge hoarding and ensure more resilient and effective teams.

---

Notable Quotes:

• Ana Maria Ungureanu [01:52]: "The foundation for the team is trust, and as Scrum Masters, we need the skills to negotiate with the team and key stakeholders."

• Host [05:36]: "Negotiation is a key skill for Scrum Masters. We need to be aware of patterns that can lead to problems before they escalate."

• Ana Maria Ungureanu [14:41]: "If we build a picture where the benefits are clear for the person, they are more likely to engage and share their knowledge."

---

This episode provides valuable insights for Scrum Masters and Agile Coaches seeking to enhance team collaboration, reduce dependencies, and foster a more resilient and adaptable team environment.

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.

[Host]

Hello everybody. Welcome to our team Tuesday. This week we have with us Ana Maria Unguriano. Hey Ana Maria, welcome back.

[Ana Maria Unguriano]

Welcome. Thank you very much. Thank you for inviting me to this discussion.

[Host]

Absolutely. It's a pleasure to have you. We had a great story about team and product owner engagement yesterday on Monday. So everybody make sure you check that out. Today we're going to talk about how teams sometimes create their own problems. But before we dive into that, Anna Maria, share with us, what was the book that most inspired you in your career as a Scrum Master?

[Ana Maria Unguriano]

So one book which I love a lot and inspired me, I think you'll be surprised, is by Chris Voss. Never split the difference. So I know we are very in touch with, you know, Phoenix Project. There are a lot of plenty available books for our journey as a Scrum Master. But coming to this book, which I love it very much from Chris Voss, an FBI negotiator, I learned a lot about how to negotiate because I think us as a Scrum Master, we need to have the skills to negotiate with the team, with the key stakeholders, but also the empathy and trust. Trust which is the foundation for the team. So how we gain the trust to our interlocutor team, to our external team, when we say okay, we will deliver that request with the team, trust us, this is the planning. So, so from this book, which I highly recommend, we will learn to better communicate, collaborate on tense situation. I would say on or you know, context where we want to drive some result but make them to arrive not to impose this. For example I need, you need to deliver this by the end of this week. I don't care. You know, when someone is pressured and you say you receive this kind of don't care, the team needs to deliver this kind of situation. This release we committed customer ask. This is a panic mode and you need to bring the piece of the team to balance. So you need to know with diplomacy and tact how to install the trust. So it's important knowing tips how to raise some question. How would you suggest to do it? Make them think a bit. Okay, maybe we have some limited situations how we can do it because this capacity is max. We don't have more it's max capacity. Maybe we need to deprioritize something if we need to deliver this request in this iteration. So this book is a key support for helping to seeking understanding, but also conversation to other interlocutor. Because why I'm saying it's extended, it helps a lot for teams, for key stakeholders. If I go in the teams, we have different personalities. Very often we may have the introverted, extroverted. Okay. So that's for sure my experience, at least one from the team will be a bit more, you know, the survival, I could say that member who is never in alignment with the team, who is, you know, never agreeing with the team. So it's good. I'm not saying it has value to the team, but to know how to calibrate the discussion and make sure he's engaged with the team. This book is extremely useful to help our to build our Scrum Master, you know, personality and understand we need to support the team and not force, you know, different practices.

[Host]

An excellent recommendation. Never Split the Difference by Chris Voss. I think it was mentioned in the podcast once, but only once before, if I remember correctly. And I think you, you gave a very clear explanation of why this book would be an important book in our toolbox. Or we could call it our Scrum Master Library because as you said, and I do want to emphasize that negotiation is a key skill for Scrum Masters for sure. And we do this, we learn all of these things. We practice the negotiation, we learn about human psychology because we want to help teams. But sometimes not even we can help them. Sometimes teams just develop these patterns, these behaviors that lead to problems on their own. And that's the story we want to explore today because we want to be aware of those patterns right before they become a big problem. So, Ana Maria, share with us the story of a team, give us a little bit of their context and then walk us through how those small little behaviors kind of maybe started Small, but then grew up and impacted the team negatively.

[Ana Maria Unguriano]

The situation I faced with the team of seven members, it was a software team, a developer, QA tech, lead architect. Okay. Which at the beginning they came to all the session daily sync quite, you know, looked engaged in discussion, committed to the course. And from one day to other situation became that some member of the team starts to be absent and not to sometimes didn't attend of the team. Or when he that person attended, not to or engaged. And what was the situation that that person was a bottleneck? It was.

[Host]

And it was just this one person, right? It was not several members, just one member.

[Ana Maria Unguriano]

One member, yes. So from that team, the member who started to be disengaged and not attend in some session, it was the senior member of the team take lead of the team. And what was the issue is he didn't align with the values of principles of sharing. Okay. Not aligned with code ownership, sharing not aligned with, you know, sharing the risk, the information. So it's impacted to deliver that release. In the situation, he took days off for four days more. Exactly. Okay. And we could not progress on delivering. And I finalized that, you know, commitment because he was the only person who could manage that execution code was only responsible for that code.

[Host]

So what you're saying is that this person was absent for four days, but the team could not progress without this person. They were dependent on their presence. And that's why the team could not deliver. Right.

[Ana Maria Unguriano]

That's why the team could not be delivered. And okay, As a step back in the retrospective, we assess what's happening. In the first phase, there was this open Pandora of finger pointing with the issue with the planar essence like this. And we need to discuss step back and understand the facts with the issue of T shaped personality of skills. So the fact that we had in the team someone who took the owner of all the knowledge and the coding and things like this impacting to deliver. Okay, so an anti pattern I saw is to have a bottleneck. Just some person who could execute specific, you know, coding and not sharing. So we took the actions of sharing lessons learned. We need in the working agreements to add the importance of having a mindset of sharing on specific session as supporting the team. It's not enough just saying, guys, tomorrow start sharing because they didn't have in the mindset this kind of practice. So we need to have some specific session. For example, with that implementing the peer programming as supporting the sharing and learning the others from the team. But also we need to discuss to the management in this T Shaped personality. We want to build for our team to give capacity for members to learn from others. If sessions dedicated at the end of the planning, but in specific iteration for sharing the knowledge and also the information.

[Host]

How were these, let's call it sharing sessions or experiences. Experience sharing sessions. How were these organized? So I imagine that in the retrospective you talked about the concept of a T shaped individual, right? Like a specialist in one domain, but can touch many domains and how the team needs to be able to share so that they don't depend on only one person. But how did you actually help the team define these sharing sessions? Because one would assume, at least that's my expectation. As I hear this story, that typically the people who, who are more often the single points of failure or bottlenecks, they tend to want to focus only on that and they really are not motivated to share their knowledge. They might look at it as a waste of time, right? Like they might say things like, oh, I can do this much faster. Why should I train somebody else when I can just do it instead of training somebody else to do it? Right. So how were those conversations in the retrospective and also in the sharing sessions?

[Ana Maria Unguriano]

Honest? In the beginning there was some phase of intense. Of storming, if we call it concretely a storming conversation. Because the like I said that person want to remain in that phase as well as a practice. I agreed with that person. Let's be open in this agile mindset. Let's try how we propose do some tries and if it's not working, we can come back. So we want to buy. If I say this engagement to be open to try different approach to iteration and if not could go back. But I was convinced that with that try at risk open the door. So with that try it, you know, helped the teams. But also he was like, okay for a face and to complement and to support. Yes, with that try we with the context with product owner, we work on giving him challenges, other challenges, commitments. So be able to give up something, you need something else purpose. So we wanted and we worked with the product, of course, part of the goals of the product to slowly engage him more concrete with something regarding AI. Because it's very important this context. So we started to engage him in some other, you know, enhancements challenging for him. We know that he likes to explore, discover and based on his capacity, he was more open to share the other part.

[Host]

I think that's a great reminder that it's easy for people to agree with something if there's something that is there to motivate them. Like in this case, it was the ability to explore new technologies and other functionality, new challenges. As you said, it could be anything else. But it's really important for us to have that in mind that even though people might resist, resist something when we just talk about that, if we build a picture where the picture is more positive for the person, then they will most likely want to take advantage of that. I will gladly share my knowledge so that I can do this other things that I'm also wanting to do. And I think that's a great reminder of that kind of rule of thumb. We always need to think about what's in it for them.

[Ana Maria Unguriano]

Definitely. And from my experience, we need to complement with complete action. We cannot say, trust me, it will work. Yeah, but if I say, you know, I need your help, it increase your trust to me because I ask your help, I need your help to work, to work with this AI new technology to see how we can incorporate to our product. As I show, you know, the trust and I build this connection of trust with you, I think it's more healthy, you know, and develop more organic if we build this than just to require. We cannot require.

[Host]

Absolutely, absolutely. We need to work with the people. Thank you very much for sharing that story. Ana Maria, welcome.

[Vasko]

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.

[Host]

Slack. We really hope you liked our show. And if you did, why not rate.

[Vasko]

This podcast on Stitcher or itunes?

[Host]

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