prioritization Archives - Scrum Master Toolbox Podcast

Pankaj Kumar: Using Agile Prioritization to Handle Competing Roles

“Who am I going to deliver to, and how urgent is this task for them?” – Pankaj Kumar

Pankaj’s current challenge will sound familiar to many Scrum Masters and Product Owners: too many important demands, all arriving at once. He runs his consultancy, Test2Deploy, works with a startup, serves as a board member in Agile Finland, and is also building a healthcare app. The problem is not motivation.

The problem is deciding what deserves attention when everything looks valuable. Pankaj uses a simple prioritization matrix built around value and importance, then adds practical filters: deadline, effort, risk, impact, stakeholder, and the stage of the work. Is it still planning? Is it in execution? Can it be delegated? Can it be removed?

Vasco connects this personal challenge back to product work, because teams face the same question every sprint. Prioritization is not just a private calculation. The stakeholder matters because they understand urgency, tradeoffs, and business consequences. Pankaj’s approach gives Scrum Masters a useful coaching angle: help teams make the decision criteria visible before the pressure hits.

In this episode, we refer to prioritization, stakeholder management, and Product Ownership.

Self-reflection Question: What criteria does your team use when two pieces of work both look urgent?

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.

Aliu Adewale: When Everything Is a “Must-Have,” Nothing Is—Prioritization for Real-World Teams

“Every yes to something unimportant is a no to what matters.” – Aliu Adewale

Aliu’s current challenge isn’t from his day job—it’s from a volunteer project for his local Parent-Teacher Association. The group wants to build a centralized app for school announcements, PTA updates, volunteer coordination, event reminders.

The first meeting produced 250 ideas, all of them framed as must-haves, all of them needed before school resumes. The window: three months. Vasco names two traps that most Scrum Masters fall into. First, MoSCoW and similar frameworks aren’t prioritization—they’re categorization.

The moment everything ends up in the “must” bucket, you’re still stuck. Second, prioritizing a feature list assumes features are independent. They almost never are: a login blocks a dozen things downstream; front-end depends on back-end; dependencies decide the order more than desirability does. Aliu’s experiment with the PTA group is a focusing constraint: stop asking “what do we need this year?” and start asking “what do we need in the first three months when school resumes?”

The 50-item must-have list collapsed to five or six features. Vasco pushes it further with his own favorite question: “What’s preventing us from releasing tomorrow?” That’s the question that exposes what really matters—and it almost never returns a list of features.

Self-reflection Question: If your team had to release tomorrow, which of your “must-haves” would you actually need?

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

About Aliu Adewale

Aliu is an Agile Delivery Lead with over 10 years of experience empowering teams to unlock their potential and deliver meaningful value. As an author, Aliu simplifies Agile principles through real-life experiences, providing practical insights for professionals to apply Agile methodologies effectively in work and everyday life.

You can link with Aliu Adewale on LinkedIn.

You can also find Aliu and his book on agileinplainsight.com.

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

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.

Bhavin Shukla: The Adaptable Product Owner — How Progress Over Perfection Drives Real Value in Scrum

In this episode, we refer to story mapping as a key tool for maintaining focus and alignment.

The Great Product Owner: Embedding Prioritization as a Daily Discipline

“She had this section called ‘Not Required Anymore.’ Every time, it was a very subtle and a very respectful way of saying to the team: great idea, but the goals changed. We don’t need it anymore.” – Bhavin Shukla

Bhavin describes a Product Owner who turned prioritization into a living discipline. She built a culture of co-creation where everyone contributed ideas to the backlog, but she also saw the biggest risk coming early: misalignment from siloed ideas. Her approach was to use story maps extensively in refinements and planning, communicating weekly with customers to collect feedback.

When the direction changed — and it regularly did — she articulated the shift clearly: “Goals changed, here’s what we’re doing now.” Her stroke of genius was a section on the story map called “Not Required Anymore,” where deprioritized ideas landed respectfully. Nobody felt offended; they understood customers’ needs had shifted.

This created a culture where people kept contributing ideas courageously, knowing that even if priorities changed, their input was valued. The result was a team that could adapt without chaos, maintaining focus while embracing change.

Self-reflection Question: How does your Product Owner communicate changes in direction? Is there a respectful, transparent mechanism for showing the team what’s no longer needed — and why?

The Bad Product Owner: The No-Feedback Product Owner

“I was looking for those keywords — a change in priorities, a change in the roadmap. Those conversations were missing. And when I asked about the roadmap, I got crickets.” – Bhavin Shukla

Bhavin shares the story of a Product Owner who was brilliant at articulating value in the backlog — customer-centric stories, well-structured work. On the surface, everything looked great: goals were being met, the team was delivering. But something subtle was wrong. The roadmap never changed. Priorities never shifted.

There were no conversations about customer feedback changing direction. When Bhavin got curious and asked to see the roadmap, he realized it was a static delivery plan, not a living document. The Product Owner wasn’t collecting feedback from customers, so there was never a reason to adapt.

The team was essentially building in a vacuum — shipping features nobody was validating. It’s an anti-pattern that’s easy to miss when the team is performing well on internal metrics but disconnected from real customer value.

Self-reflection Question: Is your team’s roadmap a living document that changes based on customer feedback, or has it become a static delivery plan? When was the last time a priority genuinely shifted based on what you learned from users?

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

About Bhavin Shukla

Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others.

You can link with Bhavin Shukla on LinkedIn.

Junaid Shaikh: Product Owner Anti-Patterns, From Team Owner to Product Owner, And The PO Who Got It Right

The Great Product Owner: Building Impactful Relationships That Get Things Done

The best PO Junaid has worked with had four qualities: clear, concise communication; an open mindset willing to be coached; courage to say “no” when needed; and the discipline to define the “what” and leave the “how” to the team. This PO started with five sources of truth — Excel tabs, whiteboards, JIRA, and other tools. When Junaid pointed out that five sources of truth is the opposite of transparency (one of Scrum’s three pillars), the PO asked for help. Junaid’s response: “I can’t do the push-ups for you.” Together, they consolidated everything into one tool. The team was happier, and the PO managed the backlog much better.

The key lesson: great product owners trust their team, communicate clearly, prioritize ruthlessly, and have the courage to say no. And they don’t try to own the team.

The Bad Product Owner: Unclear Decision Rights

Junaid opens with a line that cuts straight to the most common PO anti-pattern: “You are the product owner, not the team owner.” When he sees a PO slipping into command-and-control mode, he asks them one question: “What is your role?” They say “Product Owner.” He says: “Exactly. You own the product, not the team. If you were meant to own the team, we’d call you a project manager.”

The worst case he witnessed: a PO who was so possessive of “his” team that he required approval on everything — processes, tools, even holiday requests. In sprint planning, he would assign stories to individual team members (“Mr. X, you take this one”). He’d estimate the work himself, and when developers pushed back, he’d override them: “I was a developer, I know how long this takes.”

For approaching PO anti-patterns, Junaid has a deliberate style: he doesn’t confront upfront. He observes, takes notes, and starts by solving a smaller impediment to demonstrate he’s there to help. Once trust is built, he brings in coaching tools — first teaching the basics (“this is what the PO role is in Scrum”), then gradually coaching on specific anti-patterns observed in practice. He targets 10-15% improvement at a time. Six months later, you’ve already achieved 30-40% improvement.

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

About Junaid Shaikh

Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.