scope management Archives - Scrum Master Toolbox Podcast

Maria Skvortsova: The Yes-Man Product Owner and the Scrum Master Who Became a Proxy for the Proxy

In this episode, we refer to User Story Mapping and the MoSCoW prioritization method.

The Great Product Owner: Structure Over Gut Feeling — When a Well-Shaped Backlog Speaks for Itself

“The indicator of a good product owner is a well-shaped backlog — with priorities, with values, with efforts. You definitely know that you pull from the top, and it is the most valuable thing you should work on.” — Maria Skvortsova

For Maria, the best product owners she’s worked with share one trait: they bring structure. Not rigidity — structure. They use techniques like user story mapping to make priorities visual for everyone. They use value-effort matrices instead of gut feelings.

They apply methods like MoSCoW to give the backlog a clear, unambiguous order. The result? A developer never has to ask “what should I work on next?” — the answer is always at the top of the backlog. Maria, drawing on her decade as a C++ developer, knows firsthand how frustrating it is to chase down a BA or PO just to figure out what to build next.

A well-ordered backlog doesn’t just help the team move faster — it also makes it easier for the product owner to communicate with the business, because every decision has data behind it, not just intuition.

Self-reflection Question: Could a new team member look at your product backlog right now and immediately know what to work on next — and why that item is the most valuable?

The Bad Product Owner: The Yes-Man Who Sank the Ship — When Saying Yes to Everything Means Delivering Nothing

“He was always saying yes. And this led to the scope that grew and grew, until we realized we were not capable of delivering what we committed to.” — Maria Skvortsova

Maria returns to her SAP migration experience for this anti-pattern. The team had a team lead acting as product owner — someone technical who saw everything as important.

Every new requirement got a “yes.” The scope ballooned while the iron triangle held firm: fixed cost, fixed time, no room to breathe. The team reached a breaking point where they had to admit, to each other and to the client, that delivery was impossible. Maria stepped in as what Vasco called “a proxy for the proxy” — she helped the team lead build a user story map on Miro, then facilitated a workshop with the business.

Her question was disarmingly simple: “If we don’t deliver this by go-live, will your product still function? If yes, it goes to release two.” That reframing — not “no” but “yes, later” — gave the client clarity without triggering defensiveness. The team lead learned that business stakeholders aren’t the enemy; they just need someone to help them make honest trade-offs. And saying “not now” is infinitely more useful than saying “yes” to everything and delivering nothing on time.

Self-reflection Question: When was the last time you or your product owner said “not now” to a stakeholder — and did it feel like a failure or a strategic decision?

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 Maria Skvortsova

Maria is a Delivery Manager and Agile Coach who thrives in complexity, bringing clarity to chaotic environments. With a decade in C++ development and a background in professional opera, she blends technical precision with human empathy, helping enterprise teams move beyond task execution to collaborate seamlessly and perform like a synchronized, high-impact orchestra.

You can link with Maria Skvortsova on LinkedIn.

BONUS: Why Your Plan Is Lying to You — #NoEstimates, Throughput, and the Superstition of Project Management

This episode is a cross-post from The EBFC Show, Felipe Engineer-Manriquez’s podcast exploring Lean and Agile in construction. In this conversation, Felipe interviews Vasco about the #NoEstimates movement, throughput-based planning, and why traditional project management is still stuck in the middle ages of managing creative work.

The Human Side of Scrum That the Scrum Guide Doesn’t Cover

“When you go into a daily meeting and you start looking at the people in that room, maybe they are the exact same people that were there yesterday, but the team is totally different. Somebody might have had a bad night’s sleep, somebody might have had an argument with their spouse. These are human beings. These are not machines that you can just distribute work to.”

Vasco’s path to agile coaching started with a realization that most practitioners eventually reach: the problems in software development aren’t technological. They’re about people — getting agreements, sharing information at the right time, making the collective brain of a team actually function.

The Scrum Guide gives you organizing principles — how many meetings, who’s in them — but it says almost nothing about the real-time feedback cycle between humans that makes or breaks a team. That’s why the Scrum Master role exists: to be the lubricant for human interactions, to break down complex ideas into items the collective mind can process. It’s the piece that makes Scrum work, and it’s the piece that’s hardest to teach.

From Project Manager to #NoEstimates — The Bet That Changed Everything

“The PM wanted 15 items per sprint, and the team said ‘yeah, we can do 15.’ I said, this is not gonna happen. The team had been delivering between five and eight items per sprint. I said, I’m gonna be positive — I’m gonna say seven. And no surprise, by the end of the sprint, they delivered seven.” Continue reading BONUS: Why Your Plan Is Lying to You — #NoEstimates, Throughput, and the Superstition of Project Management

Alex Sloley: The Sprint Planning That Wouldn’t End – A Timeboxing Failure

“Although I knew about the steps of sprint planning, what I didn’t really understand was the box of time versus the box of scope.” – Alex Sloley

Alex shares a critical learning moment from his first team as a Scrum Master. After six months in the role, during an eight-hour sprint planning session for a four-week sprint, he successfully completed the “what” portion but ran out of time before addressing “how.” Rather than respecting the timebox, Alex forced the team to continue planning for another four hours the next day—blowing the timebox by 50%. This experience taught him a fundamental lesson: the difference between scope-boxing and timeboxing. In waterfall, we try to control scope while time slips away. In Scrum, we fix time and let scope adjust. Alex emphasizes that timeboxing isn’t just about keeping meetings short—it’s about limiting work in process and maintaining focus. His practical tip: use visible timers to train yourself and your teams to respect timeboxes. This mindset shift from controlling scope to respecting time remains one of the most important lessons for Scrum Masters.

Self-reflection Question: How often do you prioritize completing a planned agenda over respecting the timebox? What message does this send to your team about the values you’re reinforcing?

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

About Alex Sloley

Alex believes that a great Scrum Master can have a long and lasting impact on people and teams. He is a global agile and product management evangelist, author of The Agile Community, and frequent international speaker. A former Microsoft leader with 15 years’ experience, he now trains, coaches, and drives transformations worldwide. Certified across Scrum, ICAgile, and Kanban, Alex energizes communities, guides leaders, and—yes—enjoys good beer.

You can link with Alex Sloley on LinkedIn.

Jaques Smit: How to Help Product Owners Manage Many Stakeholders

The Great Product Owner: How Saying “No” Helps PO’s Succeed

What makes a Product Owner successful in managing large teams? In this episode, Jaques shares an example of a Product Owner who managed a large team successfully by setting clear boundaries and saying “no” unless convinced otherwise. This approach led to a well-functioning team and better innovation. Jaques emphasizes the importance of clear communication and structured leadership.

The Bad Product Owner: Helping Product Owners Manage Many Stakeholders

How can Product Owners manage stakeholder expectations effectively? Jaques shares his experience with a Product Owner (PO) working with an unmanageable number of stakeholders and communication lines. The PO’s habit of saying “yes” to everyone led to overwhelming challenges. Jaques shares insights on effective PO practices, including setting boundaries and creating smaller, more productive teams.

The Ultimate Guide to Supporting Product Owners as a Scrum Master

Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Jaques Smit

Jaques is a seasoned Agile coach and Scrum Master with extensive experience in leading and transforming teams in the game development industry. His expertise lies in fostering team collaboration, resolving conflicts, and facilitating effective retrospectives. Jaques is passionate about continuous learning and empowering teams to achieve their full potential.

You can link with Jaques Smit on LinkedIn and connect with Jaques Smit through his website.

BONUS: Achieving Agility and Exploring the Product Owner’s Impact in DevOps with Zhenya Balyasin

We start this episode by highlighting the challenges that Product Owners (POs) face when working with DevOps teams. Zhenya explains that DevOps work is unique and comes with a variety of incoming tasks and requests on a daily basis. Additionally, DevOps teams also require time to invest in improving their operations, which adds to the workload. The constant interruptions and chaotic nature of the work make it challenging for the PO to manage effectively. Unlike traditional backlogs where POs are used to prioritize tasks, in DevOps teams, the backlog may not always be the main focus. Zhenya identifies a common anti-pattern where DevOps teams have a strong willingness to help others, which can further complicate the role of the PO.

From Chaos to Clarity: Addressing Anti-Patterns in DevOps Workflows

Continue reading BONUS: Achieving Agility and Exploring the Product Owner’s Impact in DevOps with Zhenya Balyasin