The Product Owner View of Great Scrum Masters in Agile Teams | Marcin Klimaszewski

Marcin Klimaszewski: The Product Owner View of Great Scrum Masters in Agile Teams

In this episode, we refer to Design Thinking, Product Build Day, and The Mom Test by Rob Fitzpatrick.

The Great Product Owner: A Scrum Master Who Knows When to Step Into Product Work

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.

"The skill of a great Scrum Master is being flexible with the role." - Marcin Klimaszewski

Because this is a Product Owner week, Marcin closes the week by describing what great Scrum Masters look like from the product side. The key word is flexibility. A great Scrum Master protects team rhythm and alignment, but also understands when the team needs something outside the textbook process. Marcin shares the example of a product or epic kickoff where the Scrum Master worked with the Product Owner and Product Designer to create a useful workshop. The team did not only hear what was expected. They clarified assumptions, named missing data, discussed whether discovery was needed, and identified risks early. That kind of kickoff can save weeks later because it gives the whole team a shared understanding of what they are trying to deliver and how they need to deliver it. For Product Owners, that Scrum Master is not a process guardian standing aside. They are a partner who notices when product clarity, team alignment, and delivery confidence need help.

Self-reflection Question: Where could you step in this week to help the team clarify product assumptions before sprint execution begins?

The Bad Product Owner: The Scrum Master Anti-Pattern of Staying Inside the Role Description

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.

"Scrum Masters could go to someone else to get inspiration. This flexibility can come from different directions." - Marcin Klimaszewski

The anti-pattern in Marcin's story is the Scrum Master who treats the role description as a boundary instead of a starting point. Product work often contains uncertainty: outdated data, missing discovery, technical blockers, stakeholder tension, or unclear decisions. A Scrum Master does not need to be a product expert, designer, architect, or developer to help. They need to sense the tension and know how to inquire. Vasco gives a simple example: hear tension in a meeting, ask the architect for coffee, and learn what is really blocking the team. Marcin adds that Scrum Masters can learn from their own background and from other specialists, just as therapists use supervisors to think through difficult situations. The lesson for Scrum Masters is practical: flexibility is not improvising randomly. It is knowing when the process is not enough, asking better questions, and helping the team find the conversation that needs to happen.

Self-reflection Question: Are you using the Scrum Master role to create clarity, or to avoid stepping into unclear conversations?

[The Scrum Master Toolbox Podcast Recommends]

🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥

Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.

🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

[The Scrum Master Toolbox Podcast Recommends]

About Marcin Klimaszewski

Marcin Klimaszewski runs Product Build Days. One day to validate a business idea. Teams build the app themselves with AI tools, use synthetic users to sort out the usability, and design the sharpest test they can run the next day with real users. For founders, PMs, designers and other non-coders. An idea that cannot survive one day is not worth a quarter.

You can link with Marcin Klimaszewski on LinkedIn.

You can also learn more at Product Build Day.