Vasco Duarte, Author at 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: Product Owners Need the Justified No to Protect Customer Value

In this episode, we refer to Vasco’s Product Owner episodes, where Product Owners share their own lessons from the role.

The Great Product Owner: Owning the Product and Practicing the Justified No

“No, you cannot have this, but this is why.” – Sheik Meeajaun

Sheik’s model for a great Product Owner came from a mentor he worked with early in his career. That PO owned his slice of the product, delivered consistently, and taught Sheik the power of the “justified no.” A strong PO does not simply reject stakeholder requests.

They explain the trade-off, ask what should be removed from the sprint, and make business value visible. If a stakeholder wants urgent work, the PO can ask them to get agreement from the person whose work would be displaced. That shifts the conversation from pressure to prioritization. For Sheik, great Product Owners understand that their job is to bring value to the business and delight customers.

They care deeply enough about the product to protect it from random requests, HiPPO decisions, and backlog noise. They know success is not only delivery. It is the visible appreciation that comes when people recognize a product decision created real value.

Self-reflection Question: Does your Product Owner have a practical way to say no that protects value without turning every request into conflict?

The Bad Product Owner: The Executor Who Cannot Say No

“A Product Owner’s primary job is to bring value.” – Sheik Meeajaun

The anti-pattern Sheik warns about is the Product Owner as executor. This PO does not own the product, does not know the customers deeply enough, and does not push back when leadership changes direction. They become a project manager with a backlog, accepting whatever the highest-paid person in the room asks for next. The team then loses coherence, the product loses a clear direction, and the Scrum Master is left helping the team manage the consequences of weak ownership. Sheik is careful not to blame only the individual.

Many POs are placed in the role without mentoring, without a clear understanding of product ownership, and without the organizational support to say no. The result is predictable: a mountain of requests, no clear value conversation, and a team delivering work without a strong product story behind it.

Self-reflection Question: Where is your Product Owner being treated as an order taker instead of the person accountable for product value?

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: 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

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.

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

You can link with Sheik Meeajaun on LinkedIn.

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