scrum master tools Archives - Scrum Master Toolbox Podcast

Deborah Colombari: When Agile Principles Became a Fight With the System

“I was trying to go against the system, but you cannot go against the system.” – Deborah Colombari

Deborah Colombari’s Scrum Master journey started with a sense that Agile gave her permission to work differently. After early project management work, a year in Canada exposed her to Agile, and the Scrum Master role soon “felt like a glove.” But her failure story starts when a supportive leader left and a more command-driven manager arrived. Deborah pushed back hard, trying to protect the Agile practices she believed were right: dailies, burn-down and burn-up charts, transparency, and team focus.

The problem was that she was fighting the manager instead of first understanding the system around him. That conflict spilled into the team and damaged morale. Looking back, Deborah says she would now sit down with the manager first, understand the goals and pressures behind the change, and look for compromise before escalating into resistance. Her key learning was pragmatic: Scrum Masters need principles, but they also need diplomacy. The work is not only helping the team inside the Agile bubble, but also translating between that bubble and the wider organization.

In this episode, we refer to ITIL, the Dunning-Kruger effect, and Thinking in Systems by Donella Meadows.

Self-reflection Question: Where are you fighting the system before you have understood the pressure it is trying to respond to?

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 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: Scrum Master Success Starts With Trust and Ends With Teams Delivering

“I try to build trust before I build anything else.” – Sheik Meeajaun

For Sheik, Scrum Master success is simple to describe and hard to earn: the team delivers what it committed to, demos happen, customers are impressed, and the Scrum Master has protected the team from avoidable disruption. He sees himself as a shield, pushing back when stakeholders bypass the team or when a Product Owner wants to interrupt the sprint without acknowledging the cost. But when he joins a new team, Sheik does not start with burndown charts or velocity. He starts with one-on-one conversations. He tells people his job is to make their work easier, then asks what help they need.

Those conversations reveal the real blockers that charts often hide. Trust comes first because teams deliver through people, not dashboards. When people know each other, help each other, and pick up work when someone is away, they become more than a collection of roles. They become a team with a shared future.

Self-reflection Question: What do your first conversations with a new team tell people about the kind of Scrum Master you intend to be?

Featured Retrospective Format for the Week: Three Words to Sum Up the Sprint

Sheik starts retrospectives by asking each person for three words that sum up the sprint. The words can be simple: productive, boring, repetitive. The value comes from asking people to explain what sits behind those words.

Instead of stopping at “I could not finish my story,” Sheik wants the team to walk back through what happened: who was unavailable, what help was missing, where the Product Owner did not clarify, and which impediment stayed hidden too long. For him, a good retrospective creates a safe place to talk honestly about the details before the failure. The format is intentionally plain. The goal is not novelty. The goal is a conversation that finds the friction early enough for the team to do something about it.

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.

Sheik Meeajaun: The Scrum Master Who Let Standups Stay Silent Until the Team Took Ownership

“You can’t fix something until it breaks.” – Sheik Meeajaun

Sheik Meeajaun’s Monday story, is a story about silence, escalation, and the uncomfortable work of helping a team own its own communication. He stepped into a hybrid team where the previous Scrum Master had led the Daily Scrum like a status meeting. When Sheik stopped driving the conversation, the team simply stopped speaking.

For two weeks, the standups were painfully quiet. The Product Owner tried to take over, managers escalated complaints, and Sheik had to explain that the silence was exposing the real problem: the team had learned to wait for someone else to lead.

The breakthrough came when one quiet team member finally spoke up and said what she was working on. Sheik asked her to pass the conversation to the next person, and the team slowly built the habit of talking to each other. His lesson is clear: sometimes the Scrum Master must resist rescuing the team long enough for the team to see what needs to change.

Self-reflection Question: Where are you stepping in so quickly that your team never has to build the muscle of ownership?

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

About Sheik Meeajaun

You can link with Sheik Meeajaun on LinkedIn.

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

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

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.