communication Archives - Page 2 of 55 - Scrum Master Toolbox Podcast

Arun Parameswaran: How Powerful Questions Help Scrum Teams Handle Stakeholder Conflict

“Sometimes the best thing a Scrum Master can give the team isn’t the answer. It’s a question.” – Arun Parameswaran

Arun describes a team pattern many Scrum Masters recognize: stakeholders bypassing the Product Owner and going straight to developers with new requests after the sprint had already started. The developers wanted to help, so they accepted the interruptions.

The result was context switching, broken priorities, and a quiet loss of focus. Arun worked with the customer team, Product Owner, and developers to create a simple agreement: new work had to come through the PO, be clarified, and be prioritized before it reached the team. That agreement gave developers permission to protect the sprint without turning every conversation into a personal conflict.

Arun also shares how he handled the classic misunderstanding that “being Agile” means accepting every change immediately. For him, adaptability still needs timing, clarity, and shared agreements.

In this segment, we talk about the coaching stance and how Scrum Masters can use questions to help teams think together.

Self-reflection Question: What agreement would help your team protect focus without shutting stakeholders out?

Featured Book of the Week: Coaching Agile Teams by Lyssa Adkins

Arun recommends Coaching Agile Teams by Lyssa Adkins because it helped him move beyond ceremony facilitation. The book gave him a clearer picture of the Scrum Master as a coach for individuals, the team, and the wider organization. One question stayed with him: am I solving the problem for the team, or helping the team learn to solve it themselves?

That shift changed how Arun worked. Instead of telling teams what to do, he began asking questions such as “What do you think is causing this?”, “What options do we have?”, and “What are we not seeing?” For Arun, the book is a practical reminder that coaching is not about leading people to your answer. It is about helping people think.

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.

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

About Arun Parameswaran

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.

Wasim Osman: When a Scrum Team’s Silence Becomes a Self-Fulfilling Prophecy

“No team is interested in deliberately destroying their outcome or their team. Nobody does that on purpose.” – Wasim Osman

Wasim’s team was building a SaaS product with real potential. They followed Scrum, shipped features fast—and quietly let the bugs pile up. When customers finally pushed back (“you built five features, four of them have bugs”), the team made a confident bet: one quarter for new features, then one month to fix everything. It didn’t work.

The bug-bashing month revealed deeper, structural problems that demanded refactoring, and the roadmap was already packed. Then the fixes got handed to a single team, who felt demoted from the “prestigious” work of building features. Resentment grew between the teams.

At the height of that tension, the company was acquired by a waterfall-driven parent company. The head of engineering left, the chief architect and two senior engineers followed, and it became chaos. Wasim’s hardest lesson wasn’t about the acquisition—it was about voice.

The engineers assumed waterfall was being forced on them and stopped pushing back; leadership assumed the engineers were fine with it. Nobody said what they actually thought, and the fear became reality. As Wasim puts it, there was “no captain on the ship.”

In this segment, we talk about how even conversations need to be iterative, and how a Scrum Master has to balance speaking up (so the team isn’t rudderless) without speaking so much that the team stops voicing their own opinions.

Self-reflection Question: Where on your team is an unspoken assumption quietly hardening into reality, and what would it take for you to name it out loud first?

Featured Book of the Week: Difficult Conversations by Douglas Stone, Bruce Patton, and Sheila Heen

Wasim’s most-recommended book is Difficult Conversations: How to Discuss What Matters Most. What stuck with him is a deceptively simple model: every hard conversation is really made of three conversations—the “what happened” conversation (the content), the feelings conversation, and the identity conversation (what the situation says about whether you’re competent, good, or lovable). “When I first read it, I thought there can’t be only three types of conversations,” Wasim admits.

“But once you’ve gone through the book, you can put any conversation into one of those funnels.” He found it especially powerful in retrospectives: when the same issue keeps resurfacing, the real conversation is often about feelings, not action items—someone was never okay with an earlier decision, and that’s why the follow-ups never happened.

Self-reflection Question: In your last tense retrospective, which of the three conversations—content, feelings, or identity—was really driving the room?

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

About Wasim Osman

Wasim Osman is a seasoned Agile Coach and a Product Owner at Orkestra SCS. He launched his agile career at a Silicon Valley startup based in New York, then spent years coaching teams across Canada, helping organizations transform how they deliver value. Wasim brings a rare blend of agile discipline and product thinking. He’s passionate about building technology that drives real business impact.

You can link with Wasim Osman on LinkedIn.

Havva Sevay: The Car Configuration Team That Spiraled Into Silence—and the Workshop That Saved It

“First they tell you their opinion. Then they start shouting, getting emotional. And the third one is silence—and resignation. That’s the worst part.” – Havva Sevay

Havva remembers a highly motivated development team working on a car configuration system so complex it began to wear them down. They asked for training.

The Product Owner waved it off—they’ve had enough training, they should understand it. What followed was a three-stage spiral Havva now recognizes anywhere: first the team shares opinions and solutions, then frustration turns to emotion and shouting, and finally comes silence and resignation. The team even kicked the Product Owner out of their daily—a low point Havva calls the worst she has seen in her career.

The turning point was a LEGO Serious Play workshop. By getting both sides to build how they wanted to work together, the Product Owner did active listening for the first time, recognized the team needed an experienced developer to guide them, and the relationship transformed. The lesson: Scrum Masters are the facilitators of those moments of coming together—and there need to be many, at every level.

Self-reflection Question: Is a team you support moving through opinion → emotion → silence right now? What moment of coming-together could you facilitate before they reach resignation?

Featured Book of the Week: The Unfair Advantage by Ash Ali and Hasan Kubba

Havva discovered The Unfair Advantage and it reshaped how she thinks about her own style as a Scrum Master. The book argues that every person has advantages others don’t—and the skill is recognizing and using them. Havva took that idea literally: she had trained in LEGO Serious Play, a method many dismiss as “for kids,” and decided to make it her unfair advantage, promoting it inside her company until even upper management asked to use it. “I got the knowledge, so I used it internally,” she says. The lesson for Scrum Masters: own your style, embrace what makes you different, and don’t be discouraged when not every team responds to it.

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

About Havva Sevay

Havva is a people-focused organizational development expert with a Master’s in Business Administration and certification as a Scrum Master. She empowers teams and leaders through agile methodologies, modern leadership, and a strong feedback culture, fostering psychological safety and collaboration. Passionate about HR initiatives, Havva shapes people strategies, enhances employee experience, and drives inclusive, high-performing workplaces built on trust and engagement.

You can link with Havva Sevay on LinkedIn.