distributed teams Archives - Page 2 of 10 - Scrum Master Toolbox Podcast

Nate Amidon: The Hidden Cost of Distributed Agile Teams — When Time Zones and Misaligned Incentives Silently Kill Value Delivery

“User stories are getting done, velocity is fine, people are fairly predictable — but features, epics, and value isn’t getting delivered.” – Nate Amidon

Since the COVID shift to remote work, Nate has been seeing the same challenge across multiple clients: organizations spinning up engineering teams in opposite time zones, shrinking the overlap window from eight hours to barely one or two. But the time zone gap is only the surface problem. The real issue runs deeper — misaligned incentives between internal teams focused on value delivery and third-party vendors measured on output metrics like story completion counts. On the surface, everything looks fine: stories get done, velocity is stable, predictability is there. But zoom out and you see that features, epics, and actual customer value aren’t being delivered.

Nate shares a striking example: offshore QA testers incentivized by the number of bugs they found were creating Russian-doll ticket structures — bugs within bugs within bugs — flooding the system with noise while adding no value. His approach starts with making everyone feel like they’re on one team — cameras on, real conversations about who people are, what they like, where they live. Then he works to expose the constraint: how is each group actually measured and incentivized? You can’t always change the enterprise contract, but you can mitigate. In the QA case, he got leadership to communicate directly with the vendor that the new, leaner process wouldn’t penalize their people.

Self-reflection Question: Do you know how every member of your team — including vendors and contractors — is measured and incentivized, and have you checked whether those incentives are aligned with the value your team is trying to deliver?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Nate Amidon

Nate, founder of Form100 Consulting, and a former Air Force officer and combat pilot turned servant leader in software development. Nate has taken the high-stakes world of military aviation and brought its core leadership principles—clarity, accountability, and execution—into his work with Agile teams.

You can link with Nate Amidon on LinkedIn. Learn more at Form100 Consulting.

Carmela Then: When Remote Teams Stop Listening—The Silent Killer of Agile Collaboration

“Two minutes into it, my mind’s starting to wander and I started to do my own thing.” – Carmela Then

Carmela paints a vivid picture of a distributed team stretched across Sydney, New Zealand, India, and beyond—a team where communication had quietly become the enemy of progress. The warning signs were subtle at first: in meetings with 20 people on the call, only two or three would speak for the entire hour or two, with no visual aids, no PowerPoints, no drawings. The result? Within minutes, attention drifted, and everyone assumed someone else understood the message.

The speakers believed their ideas had landed; the listeners had already tuned out. This miscommunication compounded sprint after sprint until, just two months before go-live, the team was still discussing proof of concept. Trust eroded completely, and the Product Owner resorted to micromanagement—tracking developers by the hour, turning what was supposed to be an Agile team into a waterfall nightmare. Carmela points to a critical missing element: the Scrum Master had been assigned delivery management duties, leaving no one to address the communication dysfunction.

The lesson is clear—in remote, cross-cultural teams, you cannot simply talk your way through complex ideas; you need visual anchors, shared artifacts, and constant verification that understanding has truly been achieved.

In this segment, we talk about the importance of visual communication in remote teams and psychological safety.

Self-reflection Question: How do you verify that your message has truly landed with every team member, especially when working across time zones and cultures?

Featured Book of the Week: How to Win Friends and Influence People by Dale Carnegie

Carmela recommends How to Win Friends and Influence People by Dale Carnegie, a timeless classic that remains essential reading for every Scrum Master. As Carmela explains, “We work with people—customers are people, and our team, they are human beings as well. Whether we want it or not, we are leaders, we are coaches, and sometimes we could even be mentors.” Written during the Great Depression and predating software entirely, this book emphasizes that relationships and understanding people are the foundation of personal and professional success. Carmela was first introduced to the book by a successful person outside of work who advised her not just to read it once, but to revisit it every year. For Scrum Masters navigating team dynamics, stakeholder relationships, and the human side of Agile, Carnegie’s principles remain as relevant today as they were nearly a century ago.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Carmela Then

Carmela is a Senior Business Analyst with 15+ years in financial and mining sectors. A Certified and Advanced ScrumMaster, she excels in leading agile initiatives, delivering business value, and aligning technical outcomes with strategic goals.

You can link with Carmela Then on LinkedIn.

Steve Martin: When a Distributed Team’s Energy Vanishes into the Virtual Void

“They weren’t a team, they were a group of individuals working on multiple different projects.” – Vasco Duarte (describing Steve’s team situation)

The infrastructure team looked promising on paper: Product Owner in Italy, hardware engineers in Budapest, software engineers in Bucharest, designers in the UK.

The team started with energy and enthusiasm, but within a month, something shifted. People stopped showing up for daily stand-ups. Cameras went dark during meetings. Engagement in retrospectives withered. This wasn’t just about being distributed—plenty of teams work across time zones successfully. The problem ran deeper. The Scrum Master had a conflict of interest, serving dual roles as both facilitator and engineer.

Team members were simultaneously juggling three or four other projects, treating this work as just another item on an impossibly long list. Steve spent a couple of months watching the deterioration before recognizing the root cause: there was no leadership sponsorship or buy-in. Stakeholders weren’t invested. The team wasn’t actually a team—they were individuals happening to work on the same project. Steve considers this a failure because he couldn’t solve it. Sometimes, the absence of organizational support creates an unsolvable puzzle. Without leadership commitment, even the most skilled Scrum Master can’t manufacture the conditions for team success.

In this episode, we refer to The Phoenix Project by Gene Kim, a book about organizational culture disguised as a DevOps novel.

Self-reflection Question: Is your team truly dedicated to one mission, or are they a collection of individuals spread across competing priorities?

Featured Book of the Week: The Phoenix Project by Gene Kim

“There’s a lot of good lightning bulb moments that go off.” – Steve Martin

Steve describes The Phoenix Project as a book about culture, not just DevOps. Written like a novel following a mock company, it creates continuous light bulb moments for readers. The book resonated deeply with Steve because it exposed patterns he’d experienced firsthand—particularly the anti-pattern of single points of failure. Steve had worked with an engineer who would spend entire weekends doing releases, holding everything in his head, then burning out and taking three days off to recover. This engineer was the bottleneck, the single point of failure that put the entire system at risk. The Phoenix Project illuminates how knowledge hoarding and dependency on individuals creates organizational fragility. The solution isn’t just technical—it’s cultural. Teams need to share knowledge and understanding, deliberately de-risking the concentration of expertise in one person’s mind. Steve recommends this book for anyone trying to understand why organizational transformation requires more than process changes—it demands a fundamental shift in how teams think about knowledge, risk, and collaboration.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Steve Martin

You can link with Steve Martin on LinkedIn.

Steve is an Agile Coach, mentor, and founder of The Agile Master Academy. After over 14 years leading Agile transformation programmes, he’s on a mission to elevate Scrum Masters—building high-performing teams, measurable impact, and influence—and raising industry standards of Agile mastery through practical, evidence-led coaching. You can also find Steve’s insights on his YouTube channel: Agile Mastery Show.

Karim Harbott: Why System Design Beats Individual Coaching Every Time

“You can’t change people, but you can change the system. Change the environment, not the people.” – Karim Harbott

Karim was coaching a distributed team that was struggling with defects appearing constantly during sprints. The developers and testers were at different sites, and communication seemed fractured. But Karim knew from experience that when teams are underperforming, the problem usually isn’t the people—it’s the system they’re working in. He stepped back to examine the broader context, implementing behavior-driven development(BDD) and specification by example to improve clarity through BDD scenarios.

But the defects persisted.

Then, almost by accident, Karim discovered the root cause: the developers and testers were employed by different companies. They had competing interests, different incentives, and fundamentally misaligned goals. No amount of coaching the individuals would fix a structural problem like that.

It took months, but eventually the system changed—developers and testers were reorganized into unified teams from the same organization. Suddenly, the defects dropped dramatically. As Jocko Willink writes in Extreme Ownership, when something isn’t working, look at the system first. Karim’s experience proves that sometimes the most compassionate thing you can do is stop trying to fix people and start fixing the environment they work in.

Self-reflection Question: When your team struggles, do you look at the people or at the system they’re embedded in?

Featured Book of the Week: Scaling Lean and Agile Development by Craig Larman and Bas Vodde

“This book was absolute gold. The way it is written, and the tools they talk about went beyond what I was talking about back then. They introduced many concepts that I now use.” – Karim Harbott

Karim discovered Scaling Lean and Agile Development by accident, but it resonated with him immediately. The concepts Craig Larman and Bas Vodde introduced—particularly around LeSS (Large-Scale Scrum)—went far beyond the basics Karim had been working with. The book opened his eyes to system-level thinking at scale, showing how to maintain agility even as organizations grow.

It’s packed with practical tools and frameworks that Karim still uses today. For anyone working beyond a single team, this book provides the depth and nuance that most scaling frameworks gloss over. Also worth reading: User Stories Applied by Mike Cohn, another foundational text that shaped Karim’s approach to working with teams.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Karim Harbott

Karim is a consultant, trainer, and non-executive director. He bridges the gap between strategy, business agility, digital transformation, innovation, AI, and board governance. He is a Certified Scrum Trainer, and is the author of The 6 Enablers of Business Agility.

You can link with Karim Harbott on LinkedIn.

BONUS: What the UK COVID App Project Taught Us About Remote Agile Collaboration: A Conversation with Giovanni Asproni

NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!

In this special BONUS episode, Giovanni Asproni, CTO and co-founder of Launch Ventures, takes us behind the scenes of his work on the UK government’s COVID-19 app project. Giovanni shares insights into the rapid development process, the adoption of remote pairing and ensemble programming, and valuable lessons on leadership in large-scale, high-stakes projects. Giovanni also offers practical advice for teams embracing remote collaboration and agile methodologies.

The Start of a Crucial Project

“When we got the call from the UK government, we knew this was a mission to help stop the spread of the virus.” Giovanni kicks off the episode by recounting how his team at Zühlke Engineering got involved in the development of the UK’s COVID-19 app. Tasked with the challenge of building a solution that could help prevent the spread of the virus, they were under immense pressure to deliver quickly. Giovanni explains how they tackled technical hurdles, such as using Bluetooth technology to assess contagion risks, despite the lack of existing APIs on iOS and Android at the time.

“Speed was essential, but we also needed a robust design—Bluetooth was key to evaluating contagion risks, even though we didn’t have the APIs we needed.”

Overcoming Rapid Release Challenges

Continue reading BONUS: What the UK COVID App Project Taught Us About Remote Agile Collaboration: A Conversation with Giovanni Asproni