distributed teams Archives - Scrum Master Toolbox Podcast

Arun Parameswaran: The Scrum Master Mistake of Fixing Trust With Process

“Don’t confuse activity with progress.” – Arun Parameswaran

When Arun Parameswaran stepped into one of his first Scrum Master assignments, he joined a distributed team where everything looked normal from the outside. Meetings were happening, Jira was updated, and work appeared to be moving. Underneath that surface, knowledge was unevenly shared, communication between locations was weak, and trust was not yet strong enough for people to speak openly.

Arun’s first instinct was to add more structure: more meetings, more activities, more process. Looking back, he saw the real mistake. He was creating activity, not progress. The shift came when he stopped trying to provide answers and started listening through one-on-one conversations.

He learned where people were struggling, what they expected from him, and what the team needed to own for itself. In this episode, Arun shares why Scrum Masters must understand people before changing the process, and why the best coaching often starts by asking better questions.

Self-reflection Question: Where are you adding process today because the real issue feels harder to talk about?

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 Arun Parameswaran

Arun is an Agile delivery leader at Bosch Global Software Technologies who builds high-performing, data-driven ecosystems. He blends flow metrics, Jira analytics, Power BI, and applied AI to turn delivery into a transparent, predictable system.

You can link with Arun Parameswaran on LinkedIn.

Joshua McDonald: The Distributed Agile Team That Hid Problems Behind Follow-Up Stories

“They started to separate and call each other out, which is definitely not Agile.” – Joshua McDonald

Joshua shares the story of a 17-person distributed team spread across time zones, cultures, and communication styles. Some team members were direct and ready to challenge problems in public. Others preferred quieter, one-on-one conversations.

Over time, those differences created a blame environment where people stopped asking for help and started hiding problems. Long-running work was closed and replaced with follow-up stories, then part two, then part three, until the real issue disappeared under Jira housekeeping.

The result was not better flow, but delayed learning, missed upskilling opportunities, and a stressful team environment where quieter people stopped speaking in standups and retrospectives. Joshua explains what he would do differently now: split the team by communication patterns, listen to what each group needs, act as a mediator, and only bring the whole group together once people feel heard.

In this segment, we talk about different communication styles.

Self-reflection Question: What signals tell you that people are hiding problems because the team environment does not feel safe enough?

Featured Book of the Week: Never Eat Alone by Keith Ferrazzi

Joshua recommends Never Eat Alone by Keith Ferrazzi because it reframed networking as a relationship practice, not a transaction. The book helped him see that staying connected with people creates learning, support, and a safety net over time.

He also mentions the Bible as a daily source for reflecting on respect, peace, and conflict resolution, especially because Scrum Masters often need more than process knowledge to help teams work well together. For Joshua, both recommendations point to the same deeper idea: our work improves when we treat relationships as something to maintain before we urgently need them.

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

About Joshua McDonald

Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he’s already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.

You can link with Joshua McDonald on LinkedIn.

Alf Dobbert-Baums: The Two-Country Scrum Team and the Rapport That Never Showed Up

“It did not quite go as planned. I was really humbled.” – Alf Dobbert-Baums

Alf was new in the company. His boss walked over with a setup that already sounded like a warning: two development teams in two countries, two locations in Germany, a “difficult” Product Owner — and a quick “do you want to take it?” Alf said sure. Everything happened on video chat. Every meeting, every conversation, every attempt to read the room — through a window that closed the moment the call ended.

The rapport never built.

The PO stayed difficult.

Alf eventually got pulled from the team. Looking back, he saw what the video chat had hidden: the crossed arms, the eyes drifting to email, the small in-between moments that turn coworkers into colleagues. The fix wasn’t a tool — it was a flight. Visit the other location. Run a workshop with a real goal (“how do we want to work together?”, “what’s hard about our setup?”). Build a positive anchor before anything goes wrong, not after. And when you do go, don’t lead with the failures — lead with what could be possible together.

In this episode, we refer to the practice of building team working agreements as a way to create rapport without putting people on the defensive.

Self-reflection Question: When was the last time you saw the people you work with face-to-face — and what conversations are you still postponing because they only happen well in person?

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

About Alf Dobbert-Baums

Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At “Verti” he led the agile transformation.

You can link with Alf Dobbert-Baums on LinkedIn.

Maria Skvortsova: Breaking the Factory Mindset — When a 17-Person Scrum Team Treats Development Like an Assembly Line

“They wait for the story to be pushed to them, then they hand it to QAs and say ‘it’s not my business anymore.’ We have not a Scrum team, but a factory.” — Maria Skvortsova

Maria’s current challenge is one that many Scrum Masters will recognize: a large distributed team — 17 people, cameras always off, only four months together — that operates like a factory instead of a collaborative unit. In refinement sessions, only the Tech Lead, BAs, and QA speak. Everyone else stays silent.

When the sprint starts, developers wait for the Tech Lead to assign stories, work on them in isolation, then toss them over the wall to QA with a “not my problem” attitude. Maria and Vasco explored this challenge through a coaching conversation, identifying information loss as the core issue. Every handoff between developer and tester destroys knowledge and slows the process.

Maria had already introduced desk testing — pairing a developer with a QA before deployment to walk through the code on the developer’s machine. It worked well in previous teams, but this team keeps forgetting, and in a recent retrospective they even proposed creating a “handover to QA” subtask — the exact opposite of what Maria is trying to build.

The experiment that emerged: find a few early adopters willing to try a deeper collaboration model where developers participate in testing and testers participate in design — starting small, measuring what changes, and letting results speak louder than process mandates.

Self-reflection Question: Where are the biggest information loss points in your team’s development process, and what experiment could you run this sprint to reduce them?

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

About Maria Skvortsova

Maria is a Delivery Manager and Agile Coach who thrives in complexity, bringing clarity to chaotic environments. With a decade in C++ development and a background in professional opera, she blends technical precision with human empathy, helping enterprise teams move beyond task execution to collaborate seamlessly and perform like a synchronized, high-impact orchestra.

You can link with Maria Skvortsova on LinkedIn.

BONUS: How AI Is Reshaping Software Teams From the Inside — Lessons From Google, Meta, and Snowflake

In this episode, Dwarak Rajagopal — VP of AI Engineering and Research at Snowflake — shares what he’s seeing firsthand as AI agents become part of the software development process. From compressed sprint cycles to automated standups across time zones, Dwarak draws on two decades of building AI infrastructure at Google, Meta, Uber, and Apple to show what’s actually changing inside engineering organizations today.

From Compiler Engineer to AI Leader — The Thread That Connects Two Decades

“In AI, the hardest part isn’t just the models itself, it’s making them work in real environments where data is messy, fragmented, and governed.”

Dwarak started his career as an open-source GCC compiler engineer over two decades ago, optimizing hardware performance. He moved into graphics at Apple, then pivoted to AI when AlexNet started running on GPUs around 2011-2012. From there, he built autonomous driving software at Uber, led Meta’s PyTorch core framework team bridging research and production, and at Google led AI Frameworks including getting Gemini training on TPUs. The common thread: always working at the intersection of research and production, making powerful technology work in the real world. That focus on real-world application is what drew him to Snowflake — where enterprise data meets AI at scale.

AI Is Changing What Engineers Actually Do All Day

“Engineers are spending more time on system design, validation, production reliability — and less time doing the implementation itself, because AI is helping that.” Continue reading BONUS: How AI Is Reshaping Software Teams From the Inside — Lessons From Google, Meta, and Snowflake