refinement Archives - Scrum Master Toolbox Podcast

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

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.

You can link with Sheik Meeajaun on LinkedIn.

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

Danil Chernyshev: Coaching the Outsider In—Helping a Distrustful Team Through Transformation

“Developers and QAs know each other very well, but they don’t trust anybody else.” – Danil Chernyshev

This week’s coaching conversation starts with a hard situation. A subcontractor’s developers—people who had always worked isolated from the business, with no plans and no communication—were brought back inside the “mother firm” as part of a digital transformation. Overnight they faced new teams, Scrum, SDLC, CI/CD, and full transparency.

The developers and QAs trusted each other completely and trusted no one else: not the Scrum Master, not the Product Owner, not the BAs. Forced to estimate with story points, every story came back as a 3 or a 5, with no conversation. When Danil asked why, the answer was always “we’ll discuss internally and tell you tomorrow”—he suspected a second, hidden daily Scrum without him. As he and Vasco unpack it, the real issue is transparency itself: a team used to hiding now feels exposed and doesn’t know the consequences of being open.

Vasco offers an experiment—build a “trio” of the Product Owner, the Scrum Master, and one friendly insider from the team to prepare refinements together. The Product Owner is always the outsider; pairing them with a trusted insider lets ideas and experiments spread faster. Before you can improve the Scrum, you first have to bring the outsiders in.

Self-reflection Question: Where on your team is trust the real bottleneck—and who is the “insider” who could help an outsider earn it?

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

About Danil Chernyshev

Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams’ potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results.

You can link with Danil Chernyshev on LinkedIn.

Olaitan Fashanu: When the New PO Stops Refining—and the Team Starts Self-Destructing

“If we’re actually doing the job of refining this ticket properly, then we will not be creating this tension in the team.” – Olaitan Fashanu

The team was working well. They had a strong PO who came to refinement with the problem clearly framed: this is what we want to solve, here’s the context, here’s the user story, here are the acceptance criteria. The team picked it up, refined it, ran with it. Then change came.

A new PO joined—and the routine collapsed. The new PO cared about one thing: hitting the delivery date. Tickets dropped into Jira with no context, no problem statement, no acceptance criteria. Just “this needs to ship by end of month.” Within weeks, Olaitan saw the symptoms cascade through the team. Developers asked designers what tickets even meant.

QA struggled to maintain quality. Tension built. The diagnosis was clear: refinement had broken. His fix? Bring back the Definition of Ready as a non-negotiable shared standard, and introduce a product trio—business viability, technical feasibility, and design usability collaborating on every story before it reaches the rest of the team.

In this segment, we talk about the Definition of Ready and the product trio collaboration model.

Self-reflection Question: What’s the symptom you’re seeing in your team right now—and could the real source be how stories are getting refined, not how they’re getting built?

Featured Book of the Week: The Secrets of Facilitation by Michael Wilkinson

Olaitan calls out The Secrets of Facilitation by Michael Wilkinson as the book that shaped how he handles difficult moments. The book teaches the power of asking the right question at the right time—clarifying questions, probing questions, the questions that drive a stuck group forward.

“You will understand how, when to ask clarifying questions, ask really powerful questions that will help you drive or probably help you reach your goal in any session you find yourself.” For Olaitan, the biggest payoff was learning to manage group dynamics in real time—what to do when something said in a meeting lands badly, when a comment threatens to derail the room.

As a Scrum Master, you live in those moments. This book hands you a toolkit for them.

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

About Olaitan Fashanu

Olaitan Fashanu is a customer-focused professional with expertise in product management, technology, and coaching. He drives digital and agile transformation, builds collaborative cross-functional teams, and delivers high-quality products across markets. Curious and strategic, he explores AI and data intelligence while balancing technical depth, business goals, culture, structure, and long-term vision.

You can link with Olaitan Fashanu on LinkedIn.

Christian Thordal: The Jazz Duo Effect and The Absent PO — Two Sides of Agile Product Ownership

The Great Product Owner: Clarity, Accountability, and a Partnership That Fills in the Blanks

“We kind of filled in the blanks for each other, and it felt very natural — it’s grown organically into this partnership where we’re extremely aligned on how we see and do things.” – Christian Thordal

Christian describes his best Product Owner as someone he currently works with — a person who combines deep product clarity with genuine leadership. This PO is fully accountable for the backlog, sets clear expectations toward the teams, and isn’t afraid to push them.

What makes this PO stand out is how they use reporting as a communication tool: alongside the backlog, they proactively communicate to the product leader whether things are within or outside scope, always with a plan ready. Christian and this PO hold weekly follow-ups to discuss the team, the backlog, and the product direction.

Over time, their alignment has become so strong that during facilitation sessions they naturally fill in blanks for each other — one picks up where the other leaves off. Vasco compared it to a jazz duo, where each musician picks up on the other’s leads in real time. This kind of organic partnership in leadership direction reflects positively on the entire team, creating a sense of coherence and momentum that everyone can feel.

Self-reflection Question: How aligned are you with your Product Owner on leadership direction, and what would it take to build the kind of partnership where you naturally fill in the blanks for each other?

The Bad Product Owner: When the PO Disappears and the Scrum Master Becomes the Glue

“You can inspire, you can motivate, but you can’t really do the work for them.” – Christian Thordal

Christian shares an experience from a larger logistics company in Denmark where the Product Owner was a great, likable person — but didn’t understand the role. The backlog was high-level, consisting primarily of Epics with no acceptance criteria. Then the warning signs started: the PO became increasingly hard to get a hold of, started canceling refinement meetings (sometimes on the same day), began working more from home, and became physically more distant from the team.

Christian and the team were left to navigate on their own, breaking down epics into stories and tasks without knowing if they were building the right product. Christian tried setting up weekly one-hour sessions to help the PO work through the backlog, but the fundamental problem remained — you cannot do the PO’s work for them.

Eventually, Christian found himself filling in for the PO, which is itself an anti-pattern: the Scrum Master becoming the glue that holds the product together. The symptoms to watch for are clear: a PO who starts missing meetings, backlog items that remain unrefined, a PO who becomes physically or remotely distant, and — the biggest red flag — a Scrum Master who feels compelled to step in and do the PO’s job.

Self-reflection Question: Are there signs that your Product Owner is drifting away from the team, and have you caught yourself filling in gaps that aren’t yours to fill?

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

About Christian Thordal

Christian Thordal is a former Danish Army officer turned Agile Coach. He works with leaders and teams to create clarity, accountability, and momentum in complex organizations. His approach blends military leadership principles with modern product development, helping organizations move from discussion and strategy to real execution and measurable results.

You can link with Christian Thordal on LinkedIn.

Steve Martin: Coaching Product Owners to Be the Voice of the Customer

In this episode, we refer to Henrik Kniberg’s “Product Ownership in a Nutshell” video and Product Mastery by Geoff Watts.

The Great Product Owner: The Customer Obsessed PO

“The role of the PO really is to help the team empathize with the user, the customer of the product, because that’s how they can develop great solutions.” – Steve Martin

This PO worked at a fintech firm and is now CPO of a major fintech company. Steve describes him as having a brilliant mind and being a real agileist—someone Steve learned a huge amount about Agile from.

This PO’s defining characteristic was his absolute obsession with the user. Everything focused on customer pain points. Working with engineering teams serving military customers, they held regular workshops with those customers to understand their pain firsthand. They were literally the voice of the customer, not theoretically but practically.

This PO pushed and challenged teams to be more innovative, always looking for better ways of providing better software. Their gift was communication—specifically, briefing the team on the problem rather than just reading out stories in refinement sessions.

This is the anti-pattern many Product Owners fall into: going through the motions, reading requirements without context. Real product ownership, as this PO demonstrated, is telling a story that helps the team empathize and understand the pain.

When teams can internalize customer problems, they develop better solutions. This PO’s ability to communicate the problem into the minds of teams enabled them to serve customers more effectively. This is the essence of great Product Ownership: not being a proxy for management, not juggling multiple teams, but being deeply connected to customer pain and translating that pain into context the team can work with.

Self-reflection Question: Do your refinement sessions tell stories that help the team empathize with customer pain, or do you just read out requirements?

The Bad Product Owner: Proxies for Management Instead of Customer Advocates

“They weren’t a team, they were a group of individuals working on multiple different projects.” – Vasco Duarte

Steve emphasizes that Product Owners often have great intentions but struggle due to lack of training and coaching. The anti-patterns are systemic: commercial managers “dressed up” as Product Owners without understanding the role. Project managers transitioning to PO roles—though Steve notes PMs can make really good POs with proper support. The most damaging pattern is Product Owners spread across multiple teams, having very little time to focus on any single team or their customers. These POs become proxies—representing the voice of senior management rather than the voice of the customer. They cascade requirements downward instead of bringing customer insights upward. The solution isn’t to criticize these struggling Product Owners but to help them understand their role and see what good looks like. Steve recommends Henrik Kniberg’s “Product Ownership in a Nutshell” video—15 minutes, 15 years old, still profoundly relevant. He also points to Product Mastery by Geoff Watts and formal training like CSPO or IC Agile Product Ownership courses. The fundamental issue is meeting Product Owners where they are, providing coaching and support to transform them from management proxies into customer advocates. When POs understand their role as empathy builders between customers and teams, everything changes.

Self-reflection Question: Is your Product Owner the voice of senior management or the voice of the customer?

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

About Steve Martin

You can link with Steve Martin on LinkedIn.

Steve is an Agile Coach, mentor, and founder of The Agile Master Academy. After over 14 years leading Agile transformation programmes, he’s on a mission to elevate Scrum Masters—building high-performing teams, measurable impact, and influence—and raising industry standards of Agile mastery through practical, evidence-led coaching. You can also find Steve’s insights on his YouTube channel: Agile Mastery Show.