Pod Insights The Agile Daily Standup - AgileDad Scrum The Toyota Way About this episode Scrum The Toyota Way
Scrum is everywhere.
Most Product Owners understand the framework well. We manage backlogs, prioritize items, attend ceremonies, and track progress sprint after sprint.
And still, many products struggle.
Value takes too long to reach customers. Teams deliver features that are rarely used. Defects appear late. Dependencies and waiting time quietly erode delivery speed.
This is not because Scrum is broken.
It’s because Scrum alone does not address flow and waste deeply enough. That’s where Scrum the Toyota Way (STW) fundamentally changes how Product Ownership works.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Scrum is now finally considered widely adopted, yet many product owners still struggle to deliver value quickly and consistently. Some people mentioned an article to me that discussed Scrum the Toyota Way. So I thought I would explore that a little bit. So Scrum the Toyota Way extends Scrum with Lean and Toyota Way principles, shifting the focus from ceremonies and outputs of low quality and waste reduction. It actually makes sense when you think about it. It's almost like the world of Scrum BON meeting the world of extended Scrum, if you will. I mean, it's the easiest way for me to think of it. So I want to talk a little bit about how Scrum the Toyota Way
1:00 Speaker 00 has reshaped product ownership through better metrics, visualization, quality ownership, and leadership. It's a practical and opinionated reflection for product owners who want to do more than just say they're doing Scrum. I think contextually, it makes a lot of sense. Let's face reality. Scrum is everywhere. The problem is there's good Scrum, bad Scrum, and then there's a lot of stuff in the middle. It's kind of like an event when somebody recalls what happened. There's your side of the story, their side of the story, and what really happened, right? Most product owners understand the framework well. We manage backlogs, prioritize items, attend ceremonies, track progress after sprints, and still, most product owners struggle, just the way it is.
1:45 Speaker 00 Value takes too long to reach customers. Teams deliver features that are rarely used. Defects appear late. Dependencies and wait time quietly rode delivery speed. This is not because Scrum is broken, I want to be clear. It's because Scrum alone doesn't address flow and waste deeply enough. It lives kind of in that delivery category, and it doesn't push through to things that we would hope that it would do. It gives you the baseline, but it doesn't give you the answers. It's because Scrum alone is just...
2:18 Speaker 00 A fundamental way of doing output. I often say that Scrum is an agile delivery framework that focuses on that focuses on giving output, it focuses on streamlining, making it more efficient, greasiness skids, if you will, so that you can more effectively deliver products and services. But it is focused on delivery. So how does Scrum to Toyota way change how product ownership looks or works to reflection? In Scrum, the product owner is accountable for maximizing value, they're focused on value. In Scrum to Toyota way, that accountability becomes much more concrete. The product owner is literally responsible for minimizing waste. Waste shows up in many, many forms.
3:03 Speaker 00 Unnecessary features, rework, delays, excessive handoffs. Scrum to Toyota way makes these visionable and actionable. I would almost argue that Scrum to Toyota way is a lot like Stable framework. Just throwing it out there, because Stable has a lot of these things built in. Backlog ordering is no longer a periodic refinement ritual. It becomes continuous conversation with the customer, focused on answering one key question. What is the smallest, most valuable thing that we can deliver next? For product owners, that means saying no more often and saying it earlier in the process. If everything becomes a priority, then nothing is a priority. So one of the most important shifts in Scrum to Toyota way is how quality is handled. In many Scrum teams, the product owner acts as the final quality gate.
3:48 Speaker 00 In Scrum to Toyota way, that's considered a not so good thing. Quality is built into the process. Developers identify defects early, code is reviewed and analyzed continually. QA validates increments before product owner acceptance. And any role can reject work early. By the time the work reaches the product owner, it's already a pretty high quality. It's pretty decent. This allows the PO to focus on value and outcomes instead of negotiating incomplete or unstable work at the end of the sprints. Traditional scrum boards often oversimplify what's really happening. With to do, in progress, done, it hides wait times, bottlenecks, and rework. Scrum of Toyota Way insists on visual management that reflects how work really flows.
4:32 Speaker 00 Conboard boards are designed by team and represent real stages for what they actually do, like analysis, ready for development, development, code review, ready for testing, testing, ready for acceptance. This sounds like overkill, but if you think of it from a team member's perspective and from a WIP limit perspective, this can also give you a very good look into cumulative flow so you can see where things are getting stuck. In those ready for stages, for example, those are waiting times crucial for identifying where bottlenecks exist, and that's why they belong on a board. But many times they aren't there because we try to oversimplify combo boards to just get the three columns. If you can see the work, you can optimize it. If you can't see it, good luck.
5:14 Speaker 00 It's going to be hard for you to get optimized reality. A lot of people also confuse the whole metric of velocity when it comes to this. Velocity's become popular because it feels reassuring. It feels like you're giving some type of value. In Scrum of Toyota Way, that comfort that you feel with velocity is replaced with honesty around what's actually going to be delivered. So instead of focusing on internal productivity metrics, Scrum of Toyota Way emphasizes end-to-end customer lead time, the time from a customer request to a usable increment that sits in their hands. For product owners, this metric highlights delays outside of development, encourages smaller batches, and aligns everyone around a real customer impact.
5:59 Speaker 00 If velocity improves but customers still wait, the system's not getting better. You're just cranking out stuff. Another core principle borrowed from Toyota Way is GEMBA. Going to where the work actually happens. In Scrum and Toyota Way, product owners don't wait passively for questions or problems to surface. They actively observe, listen, and engage with the team. Gamble walks are not about control, they're about understanding the context of what's happening. Product owners who stay close, as close as they can actually, to the work, make better prioritization decisions, remove obstacles earlier, and build stronger trust with their teams. So Scrum and Toyota Way doesn't replace Scrum as its true sense. It just refines it.
6:41 Speaker 00 If you think that Scrum is just the one silver bullet solution, you have a hard awakening coming soon. Scrum and Toyota Way shifts product ownership away from managing artifacts and ceremonies, and more towards optimizing flow, quality, and customer value. It replaces comfortable metrics with meaningful ones, late feedback with early learning, and distance with presence. For product owners, it's demanding. It exposes waste, it forces difficult decisions, and it requires leadership beyond just what's in the backlog. But for those who truly care about delivering value as much as they say they do, and not just doing Scrum, this method offers a more honest, more effective way to practice product ownership,
7:24 Speaker 00 and it gets you in line for what you could do to make life easier for you and for your stakeholders. That's going to do it for this article. I hope that you enjoyed it. It was a decent article review, and I've been lying with most of what it said. If you have a topic or an article you want us to review, reach out to us, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous A Single Act of Kindness.. Next 5 Ways High Performers Disrupt Team Harmony Page updated November 6, 2026 · transcript and summary are machine-generated