communication Archives - Scrum Master Toolbox Podcast

Pankaj Kumar: The Agile Team Split Between Seniors and Juniors

“We have to focus not on individual tasks, but the team goals. Shared goals.” – Pankaj Kumar

Pankaj describes a team that had all the ingredients for friction: senior people with deep experience, junior people who needed support, and a Sprint Goal that required everyone to move together. The weak signal showed up in the retrospective. The junior team members were quiet, and the seniors were implicitly treating mentoring as work that did not help them. Pankaj started with one-on-one conversations to understand what was behind the silence. Then he reframed mentoring around the team outcome.

The senior people were not being asked to “lose time” helping juniors. They were being asked to build the capability the whole team needed to deliver. He also pointed out that learning flows both ways: junior team members often bring fresh technical knowledge that experienced people have not yet seen. By pairing senior and junior people on shared tasks, the team started to build trust, empathy, and confidence.

The result was visible outside the team too. Stakeholders could see the difference in sprint reviews when the team showed up with more alignment.

In this segment, we talk about team dynamics, psychological safety, and mentoring.

Self-reflection Question: Where is your team still optimizing for individual tasks when the real need is a shared outcome?

Featured Book of the Week: Straight from the Gut by Jack Welch

Pankaj mentions a leadership book that stayed with him mos: Straight from the Gut by Jack Welch.

What connected the book to his Scrum Master work was the push against bureaucracy and the image of building a speedboat instead of a large, slow ship. For Pankaj, that linked directly to empowered teams, fast learning, and the Scrum Master responsibility to help people move from hierarchy into ownership.

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 Pankaj Kumar

Pankaj Kumar is an experienced Scrum Master and Agile Coach with over 18 years in IT. He helps teams adopt Agile ways of working, improve collaboration, remove impediments, and deliver value consistently. He facilitates Scrum ceremonies, coaches teams and stakeholders, and supports Agile transformation across organizations.

You can link with Pankaj Kumar on LinkedIn.

Deborah Colombari: The Agile Team Destroyed by a Toxic Feedback Loop

“Whenever we almost started to achieve norming, we went back to storming.” – Deborah Colombari

Deborah shares the story of a team of about twelve developers and QA specialists that kept losing people one by one. The early signal was not a technical problem. It was turnover. A toxic direct leader created pressure, blame, and snarky responses whenever the team tried to explain what was happening. Because that leader’s own manager behaved the same way, Deborah saw a reinforced pattern rather than an isolated personality problem. The team could not stabilize.

Every time it moved toward norming, someone left or someone new arrived, sending the team back into storming. Knowledge walked out the door with the people who left, delivery dates slipped, morale dropped, and a fixed-date call center project was eventually canceled. Deborah’s story is a sharp systems thinking reminder for Scrum Masters: sometimes the problem is not inside the team. The team may be showing the symptoms of a system that punishes honesty, overloads people, and teaches them that leaving is safer than speaking.

In this segment, we talk about Russell Ackoff, his systems thinking interview with Haynes Media Works, and the Tuckman model.

Self-reflection Question: What turnover or morale signals are you treating as team problems when they may be system problems?

Featured Book of the Week: Russell Ackoff Interview by Haynes Media Works

Instead of a book, Deborah recommends an old Russell Ackoff interview from Haynes Media Works. She connects Ackoff’s thinking to Donella Meadows and to the practical work of Scrum Masters. Deborah highlights how Ackoff explains that the outcome a system is designed to produce affects how the whole system behaves.

Her example is health care: if the system rewards treating sickness, it becomes a disease-care system instead of a health system. For Scrum Masters, the lesson is direct. Teams are systems, companies are systems, and the incentives around them shape what they do. Deborah uses Ackoff’s work to remind us to look at feedback loops before assuming people are the problem.

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

About Deborah Colombari

Deborah is an Enterprise Agile Coach with a decade of experience championing Agile principles across organizations. Passionate about collaboration and continuous improvement, Deborah genuinely loves what she does—empowering others to work smarter, deliver value, and thrive in dynamic environments.

You can link with Deborah Colombari on LinkedIn.

Sheik Meeajaun: When Spillover Becomes Normal, Scrum Teams Stop Seeing the Cost

“A good Scrum Master makes their Product Owner look like a superstar.” – Sheik Meeajaun

Sheik describes a team pattern many Scrum Masters recognize: spillover had become so normal that finishing the sprint felt like a special event. Refinement was weak, stories were often written during refinement instead of before it, and Product Backlog Items were sometimes little more than one-line titles. The Product Owner was not consistently engaged, standups had become update sessions for the PO, and nobody was connecting non-delivery to business impact. Sheik brought his Product Owner background into the Scrum Master role and started asking a more pragmatic question: what is the cost per sprint when we do not deliver? By making cost of delay visible, he helped the team see that spillover was not just a process issue. It was lost value. The experiments were practical: protect focus, prepare stories before refinement, and tackle the gaps at ground level instead of pretending the organization would fix everything first.

Self-reflection Question: What does your team treat as normal today that is quietly costing the product money every sprint?

Featured Book of the Week: The Scrum Guide by Ken Schwaber and Jeff Sutherland

Sheik does not pretend to have a long reading list. He says experience shaped him more than any single book, because contracting exposed him to many organizations and many versions of Scrum in practice. Still, he points listeners back to The Scrum Guide as the minimum reference every Scrum Master should know.

For Sheik, the guide gives the vocabulary and foundation, but experience teaches the translation work: how those ideas survive contact with real teams, weak refinement, Product Owners who are stretched thin, and organizations that say “Agile” while still behaving like escalation machines.

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

About Sheik Meeajaun

Sheik is a seasoned product and Agile leader with over 20 years of experience scaling innovative, customer-centric digital solutions. A certified Scrum and Agile expert, he bridges strategy and execution, driving high-performance teams at enterprises like Rabobank and citizenM. As a hands-on builder, Sheik created Scrumling—a free, interactive Agile training platform—and ScrumJobs.net, a niche job board for Agile professionals. His passion lies in transforming theory into impactful, real-world results.

You can link with Sheik Meeajaun on LinkedIn.

You can also explore Scrumling, ScrumJobs.net, and Simatech.

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

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.