Pod Insights The Agile Daily Standup - AgileDad Is Scrum Dying? Or Are We Just Doing It Wrong? About this episode Is Scrum Dying? Or Are We Just Doing It Wrong? Scrum used to be king. Now people don’t even want it on their CV. Remember when being a Product Owner was cool? When Scrum Masters were change agents, not glorified note-takers? When saying “we use Scrum” signalled progressive, Agile thinking? Fast forward to now, and you’ll find Product Owners ashamed of the title, Scrum Masters sidelined, and developers stuck in factory-mode delivery. Teams are jumping ship to SAFe, Kanban, or “whatever Spotify did,” chasing results Scrum couldn’t deliver. 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 We haven't had one in a few weeks. I guess it's about that time, right? Is Scrum dying? Are we just doing it wrong? It's another one of those. People constantly send me these articles and I think they do it, you know, partially with good intent, but I think sometimes they're doing it just to, just to rattle the chains a little more because they know that this has been something that I probably talked about eight, 10, 20, 100 times. And, uh, you know, it's just, there's so many people who have the attitude. So I thought I'd go through this article with you and see maybe if we can find someone collectively who knows what's going on, or if this is just another one of those rage bait panic episodes. So here we go.
0:57 Speaker 00 Scrum used to be king. Now people don't even want it on their resume. Remember when being a product owner was cool? Still is. When Scrum masters were real change agents? Uh, they are. When they were not glorified note takers? If you're a glorified note taker, you need to find another position. This, so far, right out of the gate, this is just, it's, it's yuck so far. When saying we use Scrum signal progressive agile thinking? Okay, let's pause. I have a feeling before I go any further that this person is going to misdefine Scrum, call out how we're not following a prescriptive set of rules, and talk about how we lack,
1:40 Speaker 00 how we're falling back into waterfall, how we lack creativity and we're going, and I've never read this article before, but I just think that's the direction this is going to go based on those first lines. Fast forward to now and you'll find product owners ashamed of their title. Scrum masters sidelined and developers stuck in factory mode delivery. Teams are jumping the ship to safe, come on, or whatever Spotify did their Spotify agile model. Chasing results Scrum couldn't ever deliver.
2:11 Speaker 00 They wanted to be clear that this isn't intended to be safe bashing either. I still think it has its place, but it's anything but agile. It's more like a flexible waterfall. Okay, let's pause. So fast forward till now, and what you're really finding is that organizations are tired of having people say they're going to do things and not deliver. People are tired of not understanding what the Scrum Master role does, and they're trying to have it focus more on change management so that certain things can be tracked, so that the validity of what a Scrum Master does makes sense. Organizations are tired of product owners honing in on one product and wanting to be spoon-fed what they need to do from the upper echelons, and they want to focus more, less
2:56 Speaker 00 on the delivery aspect of it and more on the whole framework of it with ideation initiation and discovery of the MVP and identification of the stakeholders. They're trying to ask product owners to behave more like product managers, which makes total sense as well. And then with regard to developers, they're not trying to say developers bad. And we all know without developers, and you don't have a software product, right? Without developers, you don't have a product, period. So what they're trying to say is that development needs to focus more on quality management and less on actual code build, which makes total sense with the advent of AI and with all the help assists that are given to all these different roles to do their jobs. Now, they did bring up safe.
3:42 Speaker 00 I am a safe SPC, and I love safe just like the next person does. But what I can tell you is more times than not, safe is not applied correctly. And if you're not applying safe correctly, you're going to wind up in this rut that we're discussing right now, this, this hole in the ground. And what's going to happen is whether it's safe or a Kanban approach, he called it flexible waterfall. I don't know if I'd go that far. I think it's more of a dictatorial process to satisfy leadership needs to have a heavy loaded upfront planning done by a higher prescriptive level of people that is then fed down to team units to be able to deliver. It makes sense organizationally at the top, but the further down the chain it gets, the
4:23 Speaker 00 more convoluted it becomes. And that's just how safe is designed or combined where it's all focused at the bottom and very little focus at the top. What we're trying to say is we need balance and we need change management. So he continues, so what happened? Was scrum the problem all along? Or do we just totally miss the point? Before I go any further, I'm going to tell you what the problem is. Scrum is a perfect agile delivery framework. I am a certified scrum trainer and I am telling you, if you were focused on delivery and you were using scrum practices to deliver all day long, you're going to be in good shape. But if you ask yourself, how does scrum tie into product
5:02 Speaker 00 creation, ideation, initiation, discovery, MVP, vision and strategy? There's just not a lot for scrum to chew on over there, right? They're not focused on those things. They're focused on delivering a high quality product service. It's aimed to help teams be successful. Let's see where he takes it. Let's talk about why scrum is on the ropes and what actually went wrong and whether it deserves a second chance.
5:33 Speaker 00 This is just, it's becoming comical. I'm going to try to continue and if it gets just too far off the rails, I'm just going to bring us back to what I think. So scrum was never the problem, but we treated it like a process. Let's clear this up early. Scrum is not a process. Hey, it's the first thing I've heard that I agree with. It is a framework, a lightweight scaffolding designed to expose dysfunctions and not mask them with meetings and rituals. Let's pause. It's not just there to highlight dysfunctions. I hear so many people say, scrum's here to show us everything we're doing wrong so we can fix it.
6:08 Speaker 00 That's good if you want somebody pointing out everything you're doing wrong, but I can't remember the last time, you know, I went to the doctor and said, oh, boy, I am so excited to be here today. I get to learn about everything I'm doing wrong.
6:22 Speaker 00 It just sounds so, so awkward, so, so weird, so quirky. It's none of those things. Okay, let's continue.
6:33 Speaker 00 Most companies didn't want that. They wanted a neat framework or process to make software faster. Something with steps, predictability, and timelines. Sounds a lot like waterfall to me. They took scrum, skipped the hard bits, the mindset, values, leadership transformation, etc. And kept the same command and control culture, just with new labels. "We do stand-ups now. We deliver every two weeks and we have a PO." All right, I'm gonna pause again because I actually agree with that. I think a big piece of this has to do with culture. And I think that people got so used to different naming conventions and using tools like Jira that they forgot about the holistic how scrum's supposed to work. And they honed in on the titles.
7:18 Speaker 00 "Cool, as long as I still get to micromanage and chase outputs and punish failure, I don't care what you call it, right?" I just gotta tell you, that's not scrum. In the article, he calls it cosplay. People pretending to be scrum. People being scrummy. And I agree with that. So, "Scrum fails when organizations are just simply not ready for change." You can't install scrum and expect magic. I use this analogy all the time where I say that the leader of the company goes out onto the company balcony and he has a staff in his hand and he says, "Be a style of the scrum." And everyone goes, "Awwww." You know, it sounds good in theory, but it never works that way. Scrum only works when conditions are right. Culture, leadership, mindset, trust, all those things have to be in play.
8:02 Speaker 00 I've seen this a hundred times, or more. Leadership wants agility, but they don't want to give up control. Teams want autonomy, but they're judged on their velocity. Product owners are order takers, they want to be decision makers. Developers are treated like ticket machines, they want to be treated like humans. Scrum masters are glorified facilitators stripped of influence. They want to have control of the process and they want to help the organization improve.
8:30 Speaker 00 I don't think this is a far-fetched thing. In fact, I would argue it's not a far-fetched thing. I've seen so many organizations successfully do these things. But you have to understand that it takes steps to get there. A lot of people just write it off as failure and say, we're done. Failure is a first attempt in learning, and if you fail forward, you're gonna learn something. That's the key. You need to take away something that you can learn before you give up and say, fail before we even got started. And because no one wants to blame the culture, guess what gets the blame? Scrum gets the blame.
9:06 Speaker 00 I think the key here is we locked in so hard on roles and accountabilities and responsibilities that the product owner has become a frustrated waiter. They were meant to own the product, drive vision and set priorities. But instead, they're juggling 14 different stakeholders that say yes to everything and logging JIRA tickets in their JIRA instance until midnight. They don't own the product. They take orders and try to look busy. And because of this, product-minded folks are fleeing and just saying they don't want to P O title altogether. Because most people have misused and abused product owners. Wow, I went there. Developers, a ticket taker. In theory, developers choose how to solve problems. But in reality, they're told exactly what to build, when and how much.
9:51 Speaker 00 Tech leads, architects or CTOs make those decisions for them. And developers are there to execute the wishes of those people.
9:59 Speaker 00 Autonomy? You're right. Value-driven delivery? Not if the roadmap says something different. Innovation? Only if it fits within the sprint goal. The result? Talented people stuck in places that suck. They're stuck in output factories. What about the Scrum Master? This is a job no one understands. This one's so brutal. I mean, my goodness, I have seen so many times where, well, the Scrum Master facilitates a 15-minute meeting every day, but I don't know what else they do. I'm like, are you kidding me? Right? Scrum Masters are meant to be change agents, coaches, servant leaders. But most companies just treat them like virtual assistants, meeting organizers and JIRA janitors.
10:43 Speaker 00 Not gonna work. When I try to challenge system, system and try to do things different or better, they're told, you know, sometimes it's better if you just stay in your lane.
10:54 Speaker 00 Yeah, I went there. Wow. It's no surprise that many organizations, this role is disappearing. Whether people complain about the use of the word master, or whether people say, well, we want scrum masters, but we don't want them to just do scrum. We want to do these other things, right? It's no surprise that these people are being hired and then completely having their role change and morph into something different, right? So the key here is scrum isn't dead. I've said it a million times, it's not. But is it misunderstood? Yes. Misused? Often. Mistreated? Almost always at this point.
11:33 Speaker 00 There are so many things we can be doing better. Scrum can work, but not an assistant that's resistant to change. You need executives with courage to empower teams to do their jobs and to make a difference. You need true product ownership, not just proxy decision makers. You need space for learning, iteration, and, and even, shall I say it? Failure, right? Values that are lived, not laminated on a wall. Scrum is more like a mirror, not a manual. If you don't like what you see, smashing the mirror won't help. You're still the same, right? And if we're not willing to confront cultural rot, if we're not willing to confront abuse,
12:17 Speaker 00 if we're not ready to confront misuse, then yeah, scrum will eventually collapse. It will. But if you think scrum's gonna take over the room, I think you're mistaken. Now, or scrum, if you think safe is gonna take over the room, if you think safe's gonna take over, you're a long way from home, right?
12:36 Speaker 00 Safe, beautifully branded, heavy marketing material, enterprise-friendly waterfall recovery solutions. There I went there. When companies drop Scrum for safe, they're not choosing agility, they're choosing to take their pile of crap that they're currently building and then build a bigger pile of crap. They're choosing structured governance and illusion and creating a much bigger pile of crap over fixing the small pile of crap to not be crappy anymore. Safe won't save you from poor leadership or low trust. It just gives you a 200 page PDF to hide it behind, right? That's what it is. The key is, we need to get past the point where we're defending Scrum and start with a fresh set of eyes.
13:22 Speaker 00 We need to have a reset, a restart, and we need to ask ourselves, are we ready to actually empower teams? Do our product designers actually own anything, or do they need to shift? Are developers solving problems, or are they just completing checklist? Is our Scrum Master really shaping and coordinating change, or are they chasing meetings on calendars? You need to figure out how to get this to work inside of your organization in a way that makes sense. So Scrum isn't dead. We're all fine and gonna live another day, but it's up to you to make a difference. 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. As always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous Is it ever OK to deviate from the Scrum Guide? - Mike Cohn Next ScrumBan... Is it real? Or just Camouflage? Page updated November 6, 2026 · transcript and summary are machine-generated