coaching Archives - Scrum Master Toolbox Podcast

Arun Parameswaran: Success for Scrum Masters Means Teams Ask Better Questions Without You

“My goal isn’t to become indispensable. My goal is to create a team that doesn’t depend on me.” – Arun Parameswaran

For Arun, Scrum Master success is not measured by how many meetings he runs or how often the team asks him for help. It is measured by the team’s ability to solve problems without depending on him. If he has to remind everyone to update Jira, facilitate every difficult conversation, or resolve every obstacle, he is creating dependency.

A healthier signal is when team members talk directly to each other: “This is blocked. Who can help me?” or “Let’s finish this before starting something else.” Arun compares the Scrum Master to a football coach watching the match from the side.

The team needs space to play, make decisions, and learn. The Scrum Master still observes and coaches, but the goal is to intervene less often and more intentionally. As Vasco summarizes, this requires learning to wait before stepping in.

Self-reflection Question: What would your team do differently if you waited one more minute before intervening?

Featured Retrospective Format for the Week: What? So What? Now What?

Arun’s favorite retrospective format is “What? So What? Now What?” because it moves the team from facts to meaning to action. “What happened?” helps the team describe reality. “So what?” asks why it matters. “Now what?” turns the discussion into a small experiment for the next sprint. Arun also avoids using the same format every time.

He often shares the board two or three days before the retrospective so people can reflect before the meeting, add observations, and appreciate teammates. That preparation saves time in the session and makes space for a short fun activity before the team works through the real topics. His goal is simple: every retrospective should produce learning and at least one concrete experiment.

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.

Junaid Shaikh: Product Owner Anti-Patterns, From Team Owner to Product Owner, And The PO Who Got It Right

The Great Product Owner: Building Impactful Relationships That Get Things Done

The best PO Junaid has worked with had four qualities: clear, concise communication; an open mindset willing to be coached; courage to say “no” when needed; and the discipline to define the “what” and leave the “how” to the team. This PO started with five sources of truth — Excel tabs, whiteboards, JIRA, and other tools. When Junaid pointed out that five sources of truth is the opposite of transparency (one of Scrum’s three pillars), the PO asked for help. Junaid’s response: “I can’t do the push-ups for you.” Together, they consolidated everything into one tool. The team was happier, and the PO managed the backlog much better.

The key lesson: great product owners trust their team, communicate clearly, prioritize ruthlessly, and have the courage to say no. And they don’t try to own the team.

The Bad Product Owner: Unclear Decision Rights

Junaid opens with a line that cuts straight to the most common PO anti-pattern: “You are the product owner, not the team owner.” When he sees a PO slipping into command-and-control mode, he asks them one question: “What is your role?” They say “Product Owner.” He says: “Exactly. You own the product, not the team. If you were meant to own the team, we’d call you a project manager.”

The worst case he witnessed: a PO who was so possessive of “his” team that he required approval on everything — processes, tools, even holiday requests. In sprint planning, he would assign stories to individual team members (“Mr. X, you take this one”). He’d estimate the work himself, and when developers pushed back, he’d override them: “I was a developer, I know how long this takes.”

For approaching PO anti-patterns, Junaid has a deliberate style: he doesn’t confront upfront. He observes, takes notes, and starts by solving a smaller impediment to demonstrate he’s there to help. Once trust is built, he brings in coaching tools — first teaching the basics (“this is what the PO role is in Scrum”), then gradually coaching on specific anti-patterns observed in practice. He targets 10-15% improvement at a time. Six months later, you’ve already achieved 30-40% improvement.

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

About Junaid Shaikh

Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: Managing Uncertainty As A Scrum Master, How Scrum’s Rhythm Creates Stability In Unstable Times

For this week’s coaching conversation, Junaid brings a challenge that resonates well beyond any single team: dealing with uncertainty. He references the World Uncertainty Index report from February 2026, which showed the highest levels of global uncertainty ever recorded — surpassing both the COVID pandemic and the 2008 financial crisis.

This uncertainty doesn’t stay at the geopolitical level. It seeps into teams. People show up stressed, unsure about what the next month or three months will bring. As Scrum Masters, we need to be cognizant of where our team members are coming from.

Vasco adds an important layer: uncertainty operates at multiple levels within organizations. A colleague you depend on might be out sick for two weeks. A supplier might not deliver on time. Every dependency is a source of uncertainty. The question becomes: what in our processes is designed to accept and adapt to that uncertainty?

Junaid’s answer is powerful in its simplicity: Scrum’s rhythm. The sprint, the planning, the daily, the retrospective — these events at a defined cadence create internal predictability. “When you have a rhythm, when you have a known sequence of events in front of you, that takes away a lot of uncertainty.”

Vasco builds on this: Scrum creates a boundary — the sprint — that accepts uncertainty outside while reducing it inside. Internal versus external predictability. Inside the sprint, the team can fail in small ways without exposing every failure to the outside. Compare that with traditional project planning, where every task on the critical path has external visibility and impact.

For practical tools, Junaid shares how he used the Eisenhower matrix with a team to convert uncertainty into actionable priorities. They listed all activities from recent sprints, plotted them on the matrix, and found they could delegate or deprioritize 20-25% of their work. That freed them to focus with certainty on the remaining 75%. Combined with timeboxing as an uncertainty management mechanism, teams can create pockets of predictability even in turbulent times.

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

About Junaid Shaikh

You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: The Eager Scrum Master Trap, Why Proposing Solutions Too Early Can Backfire

In this episode, Junaid shares a story from his early days as a Scrum Master when enthusiasm got ahead of experience. Fresh from a CSM certification and full of ideas, he walked into teams and started proposing solutions — “No, this is not how you should do it.” It felt obvious. It wasn’t.

The wake-up call came when he proposed working agreements to a team that had been collaborating well for two years. The pushback was immediate: “Why do we need this?” He realized he was bringing a tool he’d seen elsewhere without first understanding whether the team actually had the problem that tool was meant to solve.

This led to a key shift in his approach: stop assuming. Instead of going in with answers, Junaid started creating small tiger teams with the affected people, facilitating sessions where they owned the solution. The result? Much higher acceptance and genuine continuous improvement.

These days, Junaid tests his ideas before bringing them to the full team. He connects with individual team members first — his “closer allies” — to validate whether his analysis matches reality. Only when a few people confirm “yes, this is a real problem” does he bring the proposal to the group.

As Vasco puts it: not all tools are appropriate at all times for all people. The same working agreements that were wrong for one team at one moment might be exactly right for a different team, or the same team at a different moment.

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

About Junaid Shaikh

You can link with Junaid Shaikh on LinkedIn.

Prabhleen Kaur: Letting Teams Own Their Process Through Working Agreements

“It’s about coaching the team, not teaching them.” – Prabhleen Kaur

Prabhleen shares a powerful lesson about the dangers of being too directive with a forming team. When she joined a new team, her enthusiasm and experience led her to immediately introduce best practices, believing she was setting the team up for success. Instead, the team felt burdened by rules they didn’t understand the purpose of. The process became about following instructions rather than solving problems together.

It wasn’t until her one-on-one conversations with team members that Prabhleen realized the disconnect. She discovered that the team viewed the practices as mandates rather than tools for their benefit. The turning point came when she brought this observation to the retrospective, and together they unlearned what had been imposed.

Now, when Prabhleen joins a new team, she takes a different approach. She first seeks to understand how the team has been functioning, then presents situations as problems to be solved collectively. By asking “How do you want to take this up?” instead of prescribing solutions, she invites team ownership. This shift from teaching to coaching means the team creates their own working agreements, their own definitions of ready and done, and their own communication norms. When people voice solutions themselves, they follow through because they own the outcome.

In this episode, we refer to working agreements and their importance in team formation.

Self-reflection Question: When you join a new team, do you first seek to understand their current ways of working, or do you immediately start suggesting improvements based on your past experience?

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

About Prabhleen Kaur

Prabhleen is a Certified Scrum Master with 7+ years of experience helping teams succeed with SAFe, Scrum and Kanban. Passionate about clean backlogs, powerful metrics, and dashboards that actually mean something. She is also known for making JIRA behave, driving Agile transformations, and helping teams ship value consistently and confidently.

You can link with Prabhleen Kaur on LinkedIn.