Episode Overview

Title: When Lack of Trust Turns Teams Into Isolated Individuals
Host: Vasco Duarte
Guest: Prabhleen Kaur
Podcast: Scrum Master Toolbox Podcast
Air Date: February 10, 2026

This Team Tuesday episode features Agile Coach and Scrum Master Prabhleen Kaur discussing a critical challenge in Scrum teams: how a lack of trust can erode collaboration, turning effective teams into isolated individuals. Prabhleen shares a real-world example, unpacks underlying causes, and offers actionable strategies for Scrum Masters to rebuild trust and re-establish team cohesion.

Key Discussion Points & Insights

1. Influential Books for Scrum Masters

[01:23–03:14]

• Prabhleen highlights two cornerstone books that shaped her Agile journey:

  • "Scrum" by Jeff Sutherland: She emphasizes it's not just about rules and ceremonies, but "a structure which is helping you do better." The book helped her transcend rote process and instead focus on collective goals ([01:36]).
  • "Turn the Ship Around" by David Marquet: Prabhleen distills its essence: “Leaders lead leaders.” She stresses empowering teams so members feel ownership and agency ([02:30]).

  “If you bring them to a position where they feel leaders in themselves, that's how they collaborate with you. Otherwise it'll be just a group of people following the rules... and we will never grow together as a team.” — Prabhleen [02:47]

2. Context: Team Dynamics Breaking Down

[04:28–06:03]

• Prabhleen recounts shadowing a Scrum Team where the standups felt like status updates rather than genuine collaboration.

• Key Issue: No one mentioned the Sprint Goal or asked for help; team members only described their individual task status.

• She observed that the collective "we" was missing, replaced by isolated "I" updates.

  “It was not even at a place where people were talking about the challenges they are facing or the help they need. It was just about, this is what I’m doing and this is the status of that piece of work.” — Prabhleen [04:54]

3. The Root Cause: Lack of Trust & Transparency

[06:03–07:30]

• Trigger Event: A failed PR (Pull Request) blocked a critical delivery. The team missed the deadline but avoided discussing the incident.

• Result: No open conversation in retrospectives; members addressed only their piece of the puzzle.

• The team fell into siloed work modes, leading to a breakdown in transparency and mutual support.

  “The team members were working in silos and that was the point where I understood that teams self-destruct despite best efforts when they lack trust.” — Prabhleen [06:54]

4. Consequences of Broken Trust

[07:30–09:27]

• Conflict avoidance: Failures were ignored rather than explored; there was no collective accountability or reflection.

• Deteriorating quality and delivery: Without open dialogue, both delivery timelines and product quality suffered.

• Accumulation of unresolved issues: Problems “collect and collect and collect... when it comes out, it is generally the worst point” ([08:34]).

  “It’s never one action. When opinions are not voiced out, when the discomfort is not shared, it just collects... and when it comes out, it is generally the worst point...” — Prabhleen [08:24]

5. Rebuilding Trust: Step-by-Step Strategies

[10:04–13:22]

• Go Slow and Focus on Relationships: Change and trust-building require patience; avoid forcing immediate fixes.

• Peer Reviews for Collaboration: Initiate peer reviews not as mandates, but as opportunities to help, making knowledge-sharing and feedback natural.

• Vocal Scrum Mastering: Be openly communicative in ceremonies about both big and small issues—modeling openness encourages team participation.

• Anonymous Feedback & Surveys: Use these tools for teams too closed-off to speak up in group settings. Capture honest sentiment and start conversations.

• 1-on-1 Meetings: Build trust through regular, organic check-ins that go beyond work topics. Quarterly 1-on-1s recommended for continuous relationship building.

• Create a Safe Space: The ultimate goal is for team members to feel “I’ll be heard, I’ll be understood, but I’ll not be judged for it.” ([12:40])

  “Any kind of feedback is good feedback when nobody is speaking. We can decide our space... It’s about having that conversation wherein people realize that I’ll be heard, but I’ll not be judged for it. Once that is established, the trust comes back.” — Prabhleen [12:40]

6. Patience and Persistence

[13:22–13:33]

• Trust-building is a gradual process; quick fixes are rarely effective.

  “It is a process that takes its time and we should be patient about it.” — Vasco [13:22]

Notable Quotes & Timestamps

• “It's not about following rules... it's a collective. It's not that I'm going to just facilitate the ceremonies... it's about making sure that the team... understands we are solving the same thing.” — Prabhleen [02:01]
• “Leaders lead leaders. If you bring them to a position where they feel leaders in themselves... we will grow together as a team.” — Prabhleen [02:30]
• “It was not even at a place where people were talking about the challenges they are facing or the help they need. It was just about, this is what I’m doing...” — Prabhleen [04:54]
• “The team members were working in silos... teams self-destruct despite best efforts when they lack trust.” — Prabhleen [06:54]
• “If there’s no openness to discuss it, of course there’s then no ability, no content, no input to improving it.” — Vasco [09:27]
• “Any kind of feedback is good feedback when nobody is speaking.” — Prabhleen [12:18]

Key Timestamps

• [01:23–03:14] — Influential books for Scrum Masters
• [04:28–06:03] — Team standup dysfunction: isolation and lack of shared goals
• [06:03–07:30] — The PR conflict: missed deadlines and its effects
• [07:30–09:27] — How avoidance and lack of trust compound over time
• [10:04–13:22] — Practical advice for restoring trust in teams
• [13:22–13:33] — Patience and persistence in building trust

Summary

In this episode, Prabhleen Kaur and Vasco Duarte delve deeply into how the absence of trust can fracture Scrum teams. Prabhleen’s case study vividly demonstrates how clandestine conflict and a lack of collective ownership convert teamwork into individual task management—undermining delivery, quality, and improvement. She provides a robust toolkit for Scrum Masters—including fostering open communication, peer reviews, anonymous feedback, and genuine 1-on-1 engagement—to gently restore trust and team resilience over time. The message is clear: building trust is foundational, requires patience and intention, and without it, genuine agility is impossible.

This is a must-listen (and reread) for anyone committed to nurturing healthy, high-performing Agile teams.