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

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

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes .

 

"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.

 

[The Scrum Master Toolbox Podcast Recommends]

<span style= "font-size: 13.999999999999998pt; font-family: Arial,sans-serif; color: #434343; b