change agent 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.

Deborah Colombari: Coordinating Global Agile Teams Around One MVP

“The scope is clear. How we are going to deliver it is not clear.” – Deborah Colombari

Deborah brings a live challenge from a new global project. Her team carries the deadline, but three other teams must contribute, and those teams do not share the same priority or urgency. The question becomes: how do you align teams when only one of them feels the pressure? Deborah has already tried management alignment meetings, but they have not worked as well as needed. Her next experiment is a one-week workshop inspired by Lean Inception, where managers and teams can write down what is needed, when it is needed, and what each team can realistically contribute.

Vasco and Deborah explore three practical moves: define the MVP as a real vertical slice, ask whether a person from each dependent team can join for a Sprint or a few days per week, and reduce dependencies by moving ownership closer to the team that holds the deadline. The coaching conversation ends with a useful image: even vertical slices contain thinner vertical slices. When the deadline is fixed, scope must become flexible.

In this episode, we refer to Lean Inception and Minimum Viable Product.

Self-reflection Question: When your team depends on others, are you managing the dependency or trying to reduce it?

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: Scrum Masters Must Learn by Experimenting When AI Joins the Agile Team

“Never be afraid to admit you don’t know something.” – Sheik Meeajaun

Sheik brings a current challenge that goes beyond one team: the gap between Scrum theory and real work when the context changes faster than the playbook. His example is AI. Scrum Masters are now asked to help teams where AI agents contribute to delivery, but no certification course can fully prepare us for that. Sheik’s starting point is humility: say “I don’t know,” learn the domain, run small experiments, and reflect quickly.

In one team, two human developers worked alongside several AI agents. They could not run a normal standup with Claude, so the team created a status report and reviewed it with the human team members. Sheik framed the agents as junior developers: useful, fast, and still requiring clear instructions, review, and guardrails. That framing helped experienced developers see AI collaboration as coaching and oversight, not as magic productivity. The key lesson is practical empiricism: try, inspect, adapt, and keep learning as the work changes.

In this episode, we refer to Scrumling’s AI Product Owner course and the need to adapt Scrum practice to AI-enabled work.

Self-reflection Question: What new reality is your team facing where the honest Scrum Master answer should start with “I don’t know yet”?

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: Using Scrumban and WIP Limits to Help Agile Teams Find Focus

“The WIP limit helped the developers not context switch.” – Arun Parameswaran

Arun brought a practical challenge to the Wednesday coaching conversation: a team doing both operations and development work needed more visibility and focus than their Scrum board was giving them. The trigger was context switching.

Work stayed “in progress” even when blocked, people picked up new topics before finishing old ones, and stakeholders kept asking what was actually happening. Arun helped the team experiment with Scrumban, keeping useful Scrum events while adding a Kanban-style board and explicit WIP limits. The breakthrough was not just visualizing the work. It was helping the team own the limits.

They created an “operator of the week,” rotating the responsibility for watching WIP and calling out when the team was taking on too much. That small practice made focus a team responsibility instead of a Scrum Master lecture.

Self-reflection Question: Who owns your team’s WIP limits in practice, not just on the board?

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.

Joshua McDonald: Using Cycle Time As A Storyteller, Not A Scorecard In Agile Retrospectives

“Metrics is not about telling people do better. It’s about telling that story.” – Joshua McDonald

Joshua brings cycle time as his biggest current coaching challenge. The problem is familiar: when a Scrum Master points to a story with high cycle time, developers can feel blamed, even when the intent is learning. Joshua reframes the metric as a storyteller.

Instead of asking why someone took too long, he asks what journey the story went through, where it changed hands, where it waited, and what the team now knows that it did not know at the start. He also describes practical tactics: warn people in advance before discussing specific stories, keep the language gentle, avoid forcing people to explain themselves publicly, and sometimes skip the metric conversation entirely when the team needs encouragement more than analysis.

Metrics matter because they move coaching away from gut feeling and toward observable patterns. Used well, cycle time becomes a barometer for stress, bottlenecks, missing product owner review, and places where the team needs support.

Self-reflection Question: How do you introduce metrics so the team becomes curious about the system instead of defensive about individual performance?

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

About Joshua McDonald

Joshua is endlessly curious about better ways of working. He helps teams grow by blending experimentation, creativity, and AI with practical coaching. When a meeting feels routine, he’s already testing a new approach to make it more valuable. Energetic and inventive, he turns everyday collaboration into opportunities for team growth.

You can link with Joshua McDonald on LinkedIn.