Pod Insights The Agile Daily Standup - AgileDad ScrumBan... Is it real? Or just Camouflage? About this episode ScrumBan... Is it real? Or just Camouflage? Let’s get this straight. Every time someone tells me they’re doing Scrumban, I raise an eyebrow. Not because I doubt hybrids. Hybrids can be powerful. But because in my experience, Scrumban is rarely a sign of maturity — it’s usually a cry for help. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 Let's have a conversation, a conversation today about ScrumBan. I hear people all the time who get confused about Scrum, Kanban, is it real? Is there such a thing as ScrumBan? I just want to set the record straight today. Every time someone tells me, "Hey, we're doing ScrumBan," I always raise an eyebrow. Not because I doubt that they're doing it, or I doubt in the power of hybrids. Hybrids can be powerful if they're used correctly, but because of my experience, ScrumBan is rare. And too many people chalk it up as a sign of maturity, when in actuality, it's an excuse, dare I say it, or even sometimes, a cry for help. I know that sounds weird, because in my classes, I talk about the power of ScrumBan
1:00 Speaker 00 in my advanced courses. But if you're trying to do this too early on the onset, or if you're trying to do it incorrectly, I see certain things in ScrumBan setups that raise the flag for me. So let me tell you what I see behind most setups. A product team wants the stickers and whiteboards of Scrum, without the actual commitment. So they say, "Ah, we're going to do ScrumBan." Or, the product owner just can't say no. If you have a product owner that can't say no, everything can just keep being added as a ticket in ScrumBan, right? Or a Scrum Master that lets the word "flexible," air quotes, become an excuse for chaos. That's not agile. In fact, if I had to dive in, I'd even call it camouflage.
1:44 Speaker 00 This is deflection. There's more to it. People love saying, "Well, we tried Scrum, and well, you know, it didn't work for us. So now we're doing ScrumBan." Translation? "We couldn't handle doing Scrum properly because it forced us to focus on delivery only. So we downgraded and slapped a new name on it." Ouch, I went there. Let's unpack the most common flavors of scrum bun. I've seen them all. And most of the time they taste like confusion. In the end, I promise I'll tell you what works. Here we go. How about the whole dynamic sprint length? This is my favorite, right? Sprints change depending on what we feel like today. We didn't finish it, so let's just extend it.
2:29 Speaker 00 Or let's just make, the client asks for something new. Let's add it halfway through because we can, because we're scrum bun. If you keep changing the goal, if you keep changing the finish line, are you ever going to end the race? Do you even have a sprint? Is there even a race at all? If you're adding new scope every two days, or every three days, or four days, is it still a time box, or is it just a box at that point? And if the sprint has no clear ending, how is this different from any kind of just unstructured combo? And it's not. It's not adaptive. It's not adaptive. It's more like undisciplined. A real sprint has a goal, a purpose. It ends when it ends. Otherwise, you're not doing scrum at all. And whoever shouts the loudest is who wins. And that's not where you want to be.
3:14 Speaker 00 How about this? This is my second form I see. We have a backlog, but no vision scrum. This one is subtle. On the surface, you still have two weeks' sprints, but you look closer and you'll find the backlog is a Frankenstein or whatever got thrown in the slack last night. No prioritization, no narrative, just noise. They're all small things, but they're all noise. This happens when a product doesn't relax product sense, and the team is reduced to feature delivery units and focused on, once again, strictly focused on delivery, not focused on any vision, strategy, ideation, discovery, not focused on any way to get there. When the backlog is made of whatever things you have lying around in a refrigerator, you don't have scrum, you have shuffle bun. Every day I'm shuffling.
4:00 Speaker 00 If you didn't see the video, you just missed me doing a shuffle. How about number three, the glorious combo, chaos squared. This one is the one that deserves a trophy. No stable backlog, no consistent sprint length, no clear goal, just a storm of Trello cards flying in all directions. Toto, I don't think we're in Kansas anymore. It usually happens when both the scrum master and the product owner are missing in action or worse. They're present, but not present, not competent. The team is just moving fantastic tasks with no true rhythm, no purpose, no definition of done. And someone somewhere dares to call this scrum run? It's not a hybrid. It's, it's a parody or a bad cliche. Look, I'm not just throwing rocks from the sidelines.
4:44 Speaker 00 Here we go, facts, ready? I've done scrum bond successfully with clients several times. And guess what? It was my thought, it was my initiative, and I'll say it straight. It requires maturity. What do I mean by that? If you've got a team that has tickets inbound and they also have certain work they have to do to keep the lights on. It is possible to create a hybrid version that works, but it requires focus. It requires maturity and it requires some type of high level coach to be able to get the teams to function properly. Because you don't just start with a scrum bond mentality.
5:27 Speaker 00 People often come in and think, we're just trying to make things lighter, easier and more adaptive. But in reality, they're cutting away at the structure and not realizing that replacing it with just buy one, get one free. You know, you can't always have a group on, wasn't solving anything. So for all the things and all the teams that got burned from doing this incorrectly, I'm sorry. We live, we learn, we're lucky, we learn from our failures. Is scrum bond ever legit? Of course it is. I just brought it to you. And I want to make sure I emphasize they're not necessarily edge cases, right? If we're talking about scrum bond, it has to be someone who has mature, high trust teams.
6:11 Speaker 00 Working in some type of continuous delivery model who combine predictability of scrum with flow based combo. And know how to handle inbound work for a percentage of the time. And then how to handle the rest of the work to keep the lights on with the other percentage of the time. It is definitely required to be mature. But you need to realize it's not just mashing things together or running from accountability or trying to figure out how to do things differently and trying to make it look agile. If a team says they want to do Scrum on, ask them the question, is it by design or by accident? Are we trying to avoid structure or are we refining it in a way that's going to work for us? Do we have that mental maturity? And do we have fewer rules because we've mastered what we were doing before or because we've never understood what was right in the first place?
6:55 Speaker 00 And I'm telling you now, if you learn how to do these things, you can make agile work using Scrum on, you can. But you have to have the right guidance, you have to have the right training, you have to have the right coaching, and it's not a shameless pitch for Agile Dad. It's a shameless pitch for if you're gonna do something you don't understand, get someone in who does understand to help you learn the ropes so that you can apply it successfully. Don't try to do it on your own. You see it all the time when people are doing a stunts, "Kids, don't try this at home." It's another one of those things. That's gonna do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learnmoreatagiledad.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 Is Scrum Dying? Or Are We Just Doing It Wrong? Next Scrum Has Become a Nice Term to Hide Bad Management Page updated November 6, 2026 · transcript and summary are machine-generated