product management Archives - Scrum Master Toolbox Podcast

Pankaj Kumar: Product Owners Who Prepare the Ground for Agile Teams

The Great Product Owner: Proactive Preparation Before the Team Asks

“Before the team asks, you know that this is the prerequisite for this user story.” – Pankaj Kumar

Pankaj’s example of a great Product Owner is someone who did the homework before meeting the team. This PO understood what the team needed to deliver, prepared the acceptance criteria, talked to UX early, and made sure design inputs were available before developers were blocked.

Vasco describes this as “preparing the ground” for the team. The PO was not just pushing features into a sprint. He was listening to what the team could achieve, translating stakeholder needs into clearer work, and reducing waiting time so the team could focus on execution.

For Scrum Masters, this is a useful pattern to notice: great Product Owners protect the team’s flow by handling communication and dependency work early.

Self-reflection Question: What does your Product Owner prepare before the team discovers it needs help?

The Bad Product Owner: Pushing Urgent Work Into an Already Full Sprint

“The team was already having everything on the plate, and they can’t take any more.” – Pankaj Kumar

The anti-pattern Pankaj highlights is a Product Owner who treats urgency as permission to ignore capacity. In one sprint, a PO arrived with an important customer case and insisted that it had to enter the current sprint backlog. The team was already overloaded, but the PO was not ready to hear the tradeoff. Pankaj’s advice is to slow the conversation enough to make the real decision visible.

Why is this urgent?

Who is the stakeholder?

What is the risk?

What is the impact?

Can it wait until the next sprint? If it cannot wait, what will be adjusted?

Agile welcomes change, but change still has a cost. A Product Owner who says yes without making the tradeoff visible risks damaging trust with the team.

Self-reflection Question: When urgent work enters the sprint, what does your team explicitly remove or renegotiate?

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 Pankaj Kumar

Pankaj Kumar is an experienced Scrum Master and Agile Coach with over 18 years in IT. He helps teams adopt Agile ways of working, improve collaboration, remove impediments, and deliver value consistently. He facilitates Scrum ceremonies, coaches teams and stakeholders, and supports Agile transformation across organizations.

You can link with Pankaj Kumar on LinkedIn.

BONUS: How Scrum Masters Can Use AI Without Losing the Human in the Loop with Mike Lyons and Greg Pfister

AI makes it easier than ever to build software, prototypes, courses, and coaching tools. In this BONUS episode, Mike Lyons and Greg Pfister share what that speed changes for Scrum Masters, why product judgment becomes more important, and how coaches can start using AI without outsourcing the conversations their teams still need.

The Moment AI Changed For Greg and Mike

“It’s not that the work is wrong or not needed, it is needed. That’s an important step. Retrospectives are critical.”

Greg’s first practical AI moment came while trying to build an “Ask Mike” capability for self-paced courses. After a frustrating outsourcing attempt, he started using ChatGPT to help him rebuild the tool himself, eventually moving into Cursor, Claude Code, and the Superpowers plugin for Claude Code. Mike’s moment was less technical: using AI inside Mural to affinity-map retrospective notes. The lesson for Scrum Masters is not that AI removes the work, but that it can remove enough friction to let facilitators spend more time on judgment, listening, and follow-through.

The Bottleneck Moves From Building Fast to Building the Right Thing

Continue reading BONUS: How Scrum Masters Can Use AI Without Losing the Human in the Loop with Mike Lyons and Greg Pfister

Deborah Colombari: Product Owners Who Protect Focus and Enable Ownership

In this episode, we refer to INVEST criteria and Behavior Driven Development.

The Great Product Owner: Clear Outcomes, Strong Refinement, and Space for the Team

“He doesn’t say how. That allows the team to own the solution.” – Deborah Colombari

Deborah describes a great Product Owner who came from project management, but learned to work deeply with upstream discovery and refinement. This PO uses INVEST criteria, Behavior Driven Development-style acceptance criteria, and explicit policies so that developers understand what needs to be done and why. He writes down expected outcomes at the epic and feature level, not only at the story level.

Because he does not have a developer background, he depends on the tech lead, and Deborah sees that as a strength when the collaboration works. The PO brings business outcomes and clarity. The team brings technical options and owns the solution. That split creates room for trust.

Self-reflection Question: Does your Product Owner make the outcome clear while still leaving the solution to the team?

The Bad Product Owner: Adding Work Without Understanding the Consequences

“He was doing whatever he wanted without thinking of the consequences.” – Deborah Colombari

Deborah’s Product Owner anti-pattern is a cross-team PO who accepted incoming requests and simply added them to the Sprint. There was no clear requirement discussion, no Definition of Done check, no Definition of Ready conversation, and no technical refinement with someone who could expose complexity. The PO treated every request as urgent, even when it was not, and told developers to stop their current work to pick up the new item.

The result was more parallel work, broken Sprint Goals, less predictability, and a destabilized team system. Deborah eventually had to step partly into the Product Owner space to limit WIP and protect delivery. The lesson is blunt: Product Owners who ignore consequences turn priority into chaos.

Self-reflection Question: What is the cost of every “small urgent request” your team accepts mid-Sprint?

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

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.

Arun Parameswaran: Product Owners Who Create Better Product Conversations in Scrum

In this episode, we refer to Arun’s AI prompt library for Scrum Masters and project managers.

The Great Product Owner: Curiosity, Clear Direction, and Outcome Focus

“A great PO doesn’t only ask, did we deliver? They ask, do people communicate openly?” – Arun Parameswaran

Arun describes great Product Owners as collaborative, curious, and close enough to the team to understand how delivery really works. The best POs he worked with did more than check whether items were delivered. They asked whether knowledge was distributed, whether people communicated openly, and whether everyone had a chance to contribute.

They gave the team clear product direction, supported prioritization, managed stakeholders, and stayed available when the team needed context. Arun emphasizes outcome focus: value for the customer expressed in a way the team can understand. A strong PO becomes the bridge in both directions, helping stakeholders understand the team and helping the team understand the customer.

Self-reflection Question: Does your Product Owner help the team understand customer value, or only the next ticket?

The Bad Product Owner: Turning the Team Into a Ticket Factory

“The Scrum Master shouldn’t just help the PO write better tickets. We should help create better product conversations.” – Arun Parameswaran

The anti-pattern Arun warns about is the Product Owner as ticket distributor. Stakeholders ask for something, the PO turns it into a ticket, and the team delivers without understanding the problem, the outcome, or why the work matters. Over time, the team becomes a delivery factory, and Scrum starts to look like waterfall with smaller batches.

Arun’s coaching move is to shift the conversation away from “better tickets” and toward better product thinking. What problem are we solving for customers? What outcome do we expect? What should we prioritize? What can we say no to? For Scrum Masters, this means coaching the PO and the team to bring customer context, stakeholder feedback, and prioritization into the same conversation.

Self-reflection Question: What product conversation is your team avoiding by hiding behind ticket writing?

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.

You can also explore Arun’s AI prompt library for Scrum Masters and project managers.