Bhavin Shukla Archives - Scrum Master Toolbox Podcast

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

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

Bhavin Shukla: Why Scrum Master Success Means Confronting the Ugly Truth With Data

“Success is not always good vibes, good environment for us as Scrum Masters. For me, it’s about confronting the reality, the ugly truth, which takes the team to tougher conversations, more constructive challenges.” – Bhavin Shukla

Bhavin shares a pivotal moment in his career that redefined what success means for a Scrum Master. He was working with a fantastic team — great culture, people who believed in quality, knowledge sharing, strong bonds. But sprint goals weren’t being met, and stakeholders were constantly chasing the Product Owner and Scrum Master for answers.

Bhavin got his hands dirty with the data: lack of clarity on work, context switching, patterns emerging. When he presented the data to the team, he was met with silence — a confronting kind of silence. The team was essentially saying, “We were happy. Why would you do this to us?” Bhavin’s response was direct: going for coffees and laughing together isn’t the whole job. If he wasn’t showing them reality, he couldn’t look at himself in the mirror.

The team eventually used that data to raise their own voice, pointing out systemic issues with external vendors and organizational constraints. The data gave them a platform to speak truth — not as blame, but as discovery.

Self-reflection Question: What conversations did you avoid this week that could have unlocked progress for your team? Are you bringing data to those conversations, or relying on vibes?

Featured Retrospective Format for the Week: Newspaper Headline Retrospective

Bhavin shares an unconventional use of the newspaper headline technique — typically used for roadmaps and vision — as a retrospective format. The idea is simple but powerful: ask the team to write the newspaper headline they want to see about themselves. What would the story say when they succeed?

By authoring their own headline, the team takes ownership of the narrative — they define what success looks like, what must go right, and what risks could derail them. “Putting them in that newspaper headline, they authored the story. They own the accountability to make it successful,” Bhavin explains.

He also shares a second technique for Kanban teams under pressure: a rolling two-column whiteboard — “Frustration of the Day” and “Success of the Day” — with no meetings required, just real-time data capture that becomes a continuous retrospective, reviewed every 2-3 weeks.

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

About Bhavin Shukla

You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: De-Scaling an Agile Organization — Removing Bureaucracy Without Losing Consistency

“Before people understand what needs to change, and how they need to adopt, what it means to them in their day-to-day work, and how it’s going to help and add value — those conversations are missing.” – Bhavin Shukla

Bhavin brings a challenge many organizations face but few talk about openly: de-scaling. He’s working with an organization that adopted a scaling framework for consistency — shared language, standardized tooling, uniform processes across business units. It worked for alignment, but it also created bureaucracy. Now leadership wants to become leaner and more nimble. The problem? The de-scaling itself is happening cookie-cutter style. Changes are being rolled out — new framework versions, new tools, flow metrics — without explaining the “why” to the people affected.

The result is burnout and two parallel ecosystems running simultaneously: the old meeting structures people never abandoned, and the new Scrum events layered on top. Bhavin and his coaching peers ran a “Million Meeting Minutes” workshop, collecting data on how much time teams spend in meetings, what decisions get made (or don’t), and who dominates conversations. The data revealed the overlap and waste. The experiment now is mapping those parallel systems and working with teams to understand which problems each structure actually solves — consolidating where possible while maintaining the consistency of language the organization genuinely needs.

Self-reflection Question: In your organization, are there parallel meeting structures addressing the same problems? What would it take to map them and start a conversation about consolidation?

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

About Bhavin Shukla

You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: The Hidden Cost of Always Saying Yes — How a Helpful Scrum Team Nearly Self-Destructed

“It was sort of making me feel as a Scrum Master, like it’s a slow self-destruction mode they are in. Good intentions, but it wasn’t helping them, and that’s something that they were not able to notice.” – Bhavin Shukla

Bhavin tells the story of a banking team that looked like every Scrum Master’s dream on day one — humming, cracking jokes, in the zone. But underneath the positive energy, the data told a different story. Sprint commitments kept overflowing, tech debt was rising, P1 and P2 production issues were climbing, and decision latency was immense. The root cause? This team of genuinely helpful people couldn’t say no. They wanted to help everyone who came to them, and that desire was slowly drowning them.

No one was giving them feedback about the consequences — missed sprint goals were met with “that’s okay, we’ll do it next sprint.” Bhavin introduced two simple tools: an anonymous happiness meter on the wall (rate 1-5, leave a note if below 3) and a gratitude wall. The data revealed the truth — the team was burning out, handling weekend incidents with no escalation path. Armed with this data, Bhavin coached the team on negotiation techniques: you don’t have to be rude to say no, you can negotiate the yes, you can negotiate the no.

In this segment, we talk about the importance of collecting regular data to surface hidden patterns, and the anti-pattern of teams operating without feedback on the consequences of their decisions.

Self-reflection Question: Is your team’s positive energy masking underlying problems? What data would help you discover whether good vibes are hiding unsustainable patterns?

Featured Book of the Week: Make Work Visible by Dominica DeGrandis

Bhavin recommends Make Work Visible by Dominica DeGrandis because it goes beyond values and principles to put them into practice in a grounded, system-focused way. “One clear message I get from that book is it’s not the people who are the problem, it’s the system that we need to work on to improve ways of working,” Bhavin shares.

The book introduces concepts like the five thieves of time, visualizing work, dependencies, and bottlenecks — connecting lean thinking, Kanban principles, and behavioral patterns into a practical guide for any Scrum Master looking to understand the systems their teams operate in.

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

About Bhavin Shukla

You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: When Protecting Your Agile Team Becomes the Barrier to Their Growth

“The perception I had was safe space means insulation from creating that transparency. It was not about protecting the teams. It was actually about giving them the voice, giving them the platform.” – Bhavin Shukla

Bhavin shares a story from early in his Scrum Master journey, working with two teams building a BI and regulatory platform in Australia. When he arrived, team morale was low — people buried in their screens, going for coffee alone, no healthy debates happening. His natural instinct kicked in: protect the team, help them gel, get the best out of them. But his coach asked a question that changed everything: “What’s the balance between protecting the team and creating visibility and transparency?”

Bhavin realized he’d been shielding the team from stakeholders, keeping ceremonies closed and conversations siloed. When the team opened up their reviews to stakeholders with clear expectations, something shifted. The backlog started changing based on real feedback, healthy tension built up, and the team started humming. The lesson was profound — creating a safe space doesn’t mean insulating the team from reality. Psychological safety isn’t the absence of difficult emotions; it’s the freedom to have them without destructive patterns. By isolating the team, Bhavin had actually been undermining their trust and growth.

Self-reflection Question: Are you protecting your team in ways that might actually be preventing them from building the stakeholder relationships and transparency they need to grow?

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

About Bhavin Shukla

You can link with Bhavin Shukla on LinkedIn.