PeopleOps Archives - Scrum Master Toolbox Podcast

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

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 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: Scrum Masters Must Learn by Experimenting When AI Joins the Agile Team

“Never be afraid to admit you don’t know something.” – Sheik Meeajaun

Sheik brings a current challenge that goes beyond one team: the gap between Scrum theory and real work when the context changes faster than the playbook. His example is AI. Scrum Masters are now asked to help teams where AI agents contribute to delivery, but no certification course can fully prepare us for that. Sheik’s starting point is humility: say “I don’t know,” learn the domain, run small experiments, and reflect quickly.

In one team, two human developers worked alongside several AI agents. They could not run a normal standup with Claude, so the team created a status report and reviewed it with the human team members. Sheik framed the agents as junior developers: useful, fast, and still requiring clear instructions, review, and guardrails. That framing helped experienced developers see AI collaboration as coaching and oversight, not as magic productivity. The key lesson is practical empiricism: try, inspect, adapt, and keep learning as the work changes.

In this episode, we refer to Scrumling’s AI Product Owner course and the need to adapt Scrum practice to AI-enabled work.

Self-reflection Question: What new reality is your team facing where the honest Scrum Master answer should start with “I don’t know yet”?

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: Using Scrumban and WIP Limits to Help Agile Teams Find Focus

“The WIP limit helped the developers not context switch.” – Arun Parameswaran

Arun brought a practical challenge to the Wednesday coaching conversation: a team doing both operations and development work needed more visibility and focus than their Scrum board was giving them. The trigger was context switching.

Work stayed “in progress” even when blocked, people picked up new topics before finishing old ones, and stakeholders kept asking what was actually happening. Arun helped the team experiment with Scrumban, keeping useful Scrum events while adding a Kanban-style board and explicit WIP limits. The breakthrough was not just visualizing the work. It was helping the team own the limits.

They created an “operator of the week,” rotating the responsibility for watching WIP and calling out when the team was taking on too much. That small practice made focus a team responsibility instead of a Scrum Master lecture.

Self-reflection Question: Who owns your team’s WIP limits in practice, not just on the board?

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: Scrum Master Success Means People Feel Heard, Respected, And Safe To Speak Up

“I hope you can feel heard and respected at the end of the day.” – Joshua McDonald

Joshua defines Scrum Master success through the team’s comfort with self-organization, respectful pushback, and asking for help when they do not know what they do not know. For him, a successful team is not drama-free because nothing hard happens.

It is low-drama because people can raise problems without fear, communicate openly, and keep moving forward even on bumpy roads. Joshua keeps himself honest by reviewing retrospective notes, one-on-one notes, and the commitments he made to follow up. He keeps a running to-do list from Slack messages, meetings, and team conversations so feedback does not disappear after someone shares it.

Periodically, he brings past retrospectives back to the team and asks what they accomplished, what changed, and whether anything fell through. That ledger matters because Scrum Masters work through people. If people feel heard and respected, they are more likely to keep working with you, regardless of your title.

Self-reflection Question: What system do you use to make sure team feedback turns into visible follow-up?

Featured Retrospective Format for the Week: Personalized AI-Themed Retrospectives

Joshua’s favorite retrospective format is never using the same format twice. He noticed teams getting bored and agitated when the same sailboat or standard board appeared every sprint. His answer was to personalize retrospectives around team members’ interests: a BMW theme for a developer who liked cars, a beach theme after someone’s vacation, or a TV-show theme tied to a person’s hobby.

He uses tools like Mural, Zoom whiteboards, Microsoft Teams, and AI-generated visual themes to make each retro feel like it was designed for someone in the team. The point is not decoration. The point is listening. When people recognize their interests in the retro, they feel seen as people before they reflect on the work.

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.