One Breakthrough Tip to Improve Each Scrum Meeting

These tips aren’t comprehensive overhauls—just one focused change for each of the Scrum events…that can make a dramatic difference.

One tip. One meeting. Big impact. In this rapid-fire episode, we show how a small change to each Scrum event can eliminate frustration and create flow. If your Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, or Sprint Retrospective has become stale, bureaucratic, or unproductive, we’ve got a simple tweak for each that takes under a minute to explain. Pick one meeting and improve it, or do a pass through all of them, and help your team get much more productive immediately!

Additional Resources

Show Episodes

Go Deeper With Live, Instructor-led and Online Self-Paced Training

Episode Transcript

Peter: Welcome to the Humanizing Work Show. I’m Peter Green. 

Richard: And I’m Richard Lawrence. Today we’re sharing one simple tip for each of your agile meetings that can transform them in under five minutes total. 

Peter: These aren’t comprehensive overhauls, just one focused change for each of the Scrum Events, plus backlog refinement, that can make a dramatic difference. We’ll link to other episodes if you want to go deeper. Our goal is to get through all five tips in less than five minutes, so let’s get going. 

Richard: All right, let’s look at backlog refinement first, since that’s the input to planning our number one tip, stop treating backlog refinement as a big weekly meeting with the whole team. That approach creates either too much detail, too early or too little detail, too late, and it wastes a lot of people’s time. 

Peter: Instead, make refinement continuous and incremental. Every day the Product Owner should identify what items need attention and coordinate with just the right people. The Daily Scrum is a great place for that coordination.

Richard: It might sound like, “Hey, I have a new story about payments and it seems too big. Could two of you spend 20 minutes with me after lunch to split it?” 

Peter: This transforms refinement from a dreaded meeting to a natural sustainable flow of work that happens a little bit every day with just the people who need to be involved.

Richard: For more on this approach, check out our episode on the PO board model, which we’ll link to in the show notes. 

Peter: Okay, next up, Sprint Planning. The single most powerful question for Sprint Planning is simple. Does this Fit? 

Richard: Rather than diving deep into task breakdowns or technical discussions, start with a well refined backlog and just go item by item from the top, asking that one question until the answer is no. 

Peter: This keeps the meetings focused and efficient. You don’t need to pre-assign work or break items into tasks during planning. That’s premature and it wastes time. 

Richard: “Does this Fit?” forces the team to consider their real capacity and prevents overcommitment, which is the number one cause of missed Sprint goals and technical debt.

Peter: This simple change can turn a two hour planning session into a focused 30 minute alignment meeting. 

Richard: The game changer for the Daily Scrum is to have the backlog items talk instead of the people. 

Peter: In typical Daily Scrums, each person reports what they did and what they will do often resulting in: “Yesterday I was busy working on my stuff. Today I’ll be super busy working on my stuff. No blockers.” 

Richard: Instead, start with the highest priority backlog item that was in play yesterday, or will be today and ask: “What happened yesterday to get me closer to done. What’s keeping me from getting done? What’ll happen today to move me forward?”

Peter: This simple shift transforms the meeting from status reporting to collaborative planning. It naturally surfaces opportunities to help each other and keeps the focus on the shared commitment. 

Richard: Teams who make this one change often find their Daily Scrums become energizing rather than tedious. 

Peter: Sprint Reviews become dramatically more effective when you structure them as three clear passes that answer three different questions.

Richard: Rather than just demoing features or diving too deep into implementation details, examine the product at three levels. 

Peter: First, look at major product changes to answer: “Are we going in the right direction?” with senior stakeholders present. 

Richard: Next, you might let some of those stakeholders go and then review more granular user story level progress to answer, “Are we making progress on what we’ve intended to do?” with those closer stakeholders?

Peter: Finally, briefly discuss technical changes that happened in the past Sprint to answer: “How has our foundation evolved? How’s our internal quality and design?” which might just involve the team. 

Richard: This three level approach provides the right information and seeks the right feedback with the right people at the right time, avoiding both superficial demos and technical rabbit holes.

Peter: Now retrospectives. The key to breaking through stagnant retrospectives is simple: start with shared objective data before you jump into interpretation. 

Richard: Too many teams skip straight to opinions about what went well or poorly without first establishing what actually happened during the Sprint. 

Peter: Before discussing what to change, spend time gathering and visualizing concrete data like Sprint metrics, impediments that arose, events that occurred, anything that team can observe together. 

Richard: When everyone starts from the same factual foundation, your interpretations become more insightful and your action items become more targeted. 

Peter: You have more information to work from, giving you more options for what to improve. This one shift prevents teams from repeatedly discussing symptoms instead of addressing root causes. 

Richard: So there you have it. Five focused changes that can transform your agile meetings. 

Peter: Make refinement continuous rather than a big meeting Use “Does this Fit?” as your Sprint Planning mantra. Have the stories talk in Daily Scrums. Structure reviews in three levels. And start Retrospectives with shared data.

Richard: Try implementing just one of these tips in your next meeting cycle, and we’d love to hear how it goes. 

Peter: And for more depth on any of these topics, check the links in our show notes to our dedicated episodes on each meeting type. Thanks for tuning in to another Humanizing Work Show and we’ll see you next time.

Last updated