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.
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
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.
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
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.
Everybody talks about AI in theory. In this BONUS episode, Dave Westgarth talks about it in practice — the boring, everyday ways a Scrum Master and Agile Coach actually puts AI to work. From t-shirt sizing to sprint reports to a self-coded Monte Carlo forecaster, Dave shares what works, what doesn’t, and the one mindset shift that separates people who get value from AI from those who just generate more noise.
From “Magic Answer Box” to Personalised Partner
“Instead of taking it as a magic answer box, using it as a personalised partner to work through problems, look at your ideas, and really hold them in the cold light of day before proposing things.”
Dave came into agile from a development background, moved through project delivery, and had already worked at AI and ML companies long before ChatGPT made the technology personal and accessible. Like most people, he first met these tools as a “magic answer box” — ask a question, get an answer, run with it.
The real shift came when he stopped optimizing for output and started using AI to drive better outcomes: ping the model, get a response, then interrogate it, refine the thinking, and go around again. The value isn’t the first answer. It’s the conversation that sharpens your own reasoning.
These Tools Aren’t Neutral — So Corner Them Into Being a Critic
“If you ask it to be punishing, negative, and brutal, it gives you a lot more relevant feedback.”
One of Dave’s sharpest points: AI tools are not neutral guides. Because of their system prompts and the incentives baked in by the providers, they’re relentlessly positive — they want to affirm you and keep you around, a little like social media.
That makes them weak for anything where you need honest pushback: personas, user stories, feedback on ideas. Dave’s fix is to flip it on its head. Rather than asking “is this any good?” (which reliably earns an “8 out of 10, but to make it a 10…”), he tells the model to be as harsh and brutal as it can and really try to punish the idea. You don’t want a partner that always agrees with you — you want one that pinpoints the areas you haven’t thought about.
The First Real Time-Saver: Reports, and the Themes You Missed
“Are there any themes that have emerged over the last 4 weeks that I might have missed in this latest deck?”
The first thing that stopped feeling like a party trick was the one we all know: project documentation and reporting — sprint reports, status updates, review decks. Instead of letting AI invent the structure, Dave feeds it his own structure plus Teams recordings, notes, and existing docs, and lets it populate the format he already uses.
The trick that goes a level deeper: after several sprints, feed all the AI-assisted reports back in and ask what themes have emerged across the last four weeks that this latest deck might have missed. Again, it stops being an answer box and becomes a partner and critic.
AI Is Part of the Job Now — Like Spreadsheets Once Were
“The way to get ahead now is figure out how to use it as effectively as you can in your role.”
Dave sees the early resistance movement against AI as a false economy. For delivery professionals — project managers, Scrum Masters, agile coaches — knowing how to use these tools well is fast becoming a core expectation, not a nice-to-have.
Vasco draws the parallel to spreadsheets: once dismissed as too complicated and “not my kind of thing,” until people started building real forecasting and capacity models with them and the work changed. AI is on the same arc — still a little mystical today, genuinely useful tomorrow, and eventually just another tool in the box.
A Week With AI in the Loop
“The power that these prompt-to-product tools give you to create these hyper-personalized tools that make you more effective is, in a lot of ways, magic.”
Dave walked through what his week actually looks like with AI in the loop:
Monday primer: a scheduled ChatGPT task emails him a scene-set every Monday — last week’s plan and top priorities — so he isn’t spending the first half hour reconstructing where things stood.
Priority calls: which items are the toughest, where the quick wins are, where he can get early traction, and where risks might be emerging that he can squash early.
Everyday comms: drafting the bones of emails, pings, and project updates so he spends almost no time formatting.
Prompt-to-product tools: using Base44, Lovable, and Replit to build his own tools — including a Monte Carlo forecaster that takes his team’s sprint throughput and projects the remaining backlog, replacing an ugly spreadsheet with a clean web app. He also builds AI-powered widgets in Miro for retrospectives, mood check-ins, and planning poker.
The theme running through all of it: hyper-personalized tooling, shaped by your team and your own skills, rather than one-size-fits-all software.
The Myth That AI Makes Scrum Masters Worse
“I can’t see any role of a knowledge worker where having an LLM at your disposal makes you less capable, less knowledgeable, less skilled than someone that doesn’t.”
Dave sees the same adoption spectrum among developers and Scrum Masters — from “I’ll never touch it” to “I’ll never write code by hand again.” And he pushes back hard on an emerging prejudice that echoes the old “technical Scrum Masters are worse” debate: the idea that Scrum Masters who use AI are somehow weaker.
Used well, AI lets you elevate your strengths and cover your gaps — a people-centered Scrum Master can become far more technical, and a technical one far more people-centered, each with a trusted teaching guide right there. The key competency isn’t avoidance; it’s discernment about when to reach for the tool and when not to.
From More Output to Better Outcomes
“The bottleneck has never really been typing code. The bottleneck has been understanding the problems and the customers well enough to define a solution that fixes them.”
Dave’s clearest reframe: AI is driving the price of output down. When volume is easy — more features, more emails, more documents on demand — churning out more of it stops being a differentiator, because everyone can do it. What matters is deciding which problems are worth solving and finding the most effective solution.
Experienced agile professionals have always known the real bottleneck was understanding the customer well enough to define the right solution, not the typing. AI just exposes that in a much starker way: there’s nowhere left to hide behind sheer volume.
What to Pay Attention To — and a Monday Experiment
“It can do a lot of that manual, low-thinking, high-effort work to free you up to do more of the really impactful stuff.”
For Scrum Masters being told to “adopt AI,” Dave’s advice is to let it take the joyless work — the end-of-sprint collateral, the Jira monitoring, the reports and charts — so you can spend your time on the coaching, the strategic thinking, and the organizational-level impact that’s harder to reach when you’re buried in tactical chores.
His concrete Monday-morning experiment: take the two or three prioritized actions from your next retrospective, bring them to ChatGPT or Claude, and ask, “which of these could you really help me with, and how could you help me move the needle?” Start a conversation. You don’t have to accept its answers — the point is to sharpen your own thinking about where you can add the most value next sprint.
Developing “Taste” With AI
“One element of taste is being able to judge it fairly harshly — getting through the beige as quickly as you can to find the little nuggets and gems.”
Both Dave and Vasco land on the same skill for the year ahead: taste. These tools produce a lot of text, and not all of it is useful. Vasco shares his own aha moment — asking for ideas, getting the obvious ones, then repeating “give me more, don’t repeat any” until the model finally surfaced something genuinely unexpected. That simple move turns AI into an engine for exploring the solution space until something clicks. The competency to build is the ability to move through the beige quickly and recognize the gems that materially change what you do next.
Recommended Resources
In this episode, Dave has the following recommendations for those wanting to learn, and take advantage of AI at work:
Dave Westgarth is a product and Agile practitioner exploring how AI transforms product development, experimentation, and team workflows. He shares practical insights on leveraging tools to accelerate value delivery and innovation.
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
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 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.
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and
TRANSFORM
The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and
TRANSFORM
The way your team works
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Access three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners.
Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
FREE! Audiobook Chapters: Overcome Team Resistance and Gain Leadership Buy-In
Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Your FREE ticket is on the way!
Check your inbox for details.
Email us at
ProductOwnerSummit.org if you have questions
Check Your Inbox For Details
Email us if you have questions:
ProductOwnerSummit@oikosofy.com