Pod Insights The Agile Daily Standup - AgileDad Is Scrum Slowly Taking Away Your Will To Live? About this episode Is Scrum Slowly Taking Away Your Will To Live?
On the surface, it sounds innocent, doesn’t it? Cheerful even. Like something British schoolchildren might play on a muddy field before promptly breaking an ankle. But no. In reality, Scrum is a framework for managing work in software development, and it is somehow both wildly popular and completely misunderstood by… well, almost everyone.
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:15 Speaker 00 Scrum, on the surface, sounds innocent, doesn't it? Cheerful even, like something British schoolchildren might play on a muddy field before promptly breaking an ankle. But no, in reality, Scrum is a framework for managing work in any type of product or project development. And it's somehow both wildly popular and completely misunderstood by, well, almost everyone. Here's the idea: A Scrum team is supposed to work in small time-box chunks called sprints. Two weeks typically. Sounds neat, right? Deliver a bit, learn a bit, adapt a bit, try again. Except, here's where it gets horrifying.
1:00 Speaker 00 The second you explain this, someone in management immediately goes, "Great, that means we'll get everything faster, right?" No, that's not what it means at all. That's like being told a toddler is learning to walk and then screaming, "Great, so when are they running the half marathon?" You know, it doesn't work that way. Scrum is designed to be incremental, and as such, it comes with events like daily scrums, sprint plannings, reviews, retrospectives. In theory, these help create the focus and transparency we're looking for. In practice, they often look like a hostage situation where seven engineers mumble into a Zoom call while one guy insists on screen-sharing Jira until your soul gently vacates your body and your will to live is gone.
1:46 Speaker 00 There, I said it. And then, "Oh, we haven't even talked about the accountabilities yet." Oh, oh, does say "accountabilities," I meant roles, but I meant "accountabilities," because that's what they're called. So there's a Scrum master, that's the coach or servant leader, often downgraded to meeting scheduler and Jira jockey. The product owner, divisionary prioritizing the backlog, in reality, the person everyone blames when a CEO's cousin suddenly wants a blockchain feature. Go figure. And then the developers, the people that actually do the work, AKA the ones who can't escape the rat race, the ones who are running in the hamster wheel. Now, in best cases, Scrum works beautifully. It's absolutely wonderful. Teams deliver incrementally.
2:27 Speaker 00 They had that to change. They delight customers. In worst case, it becomes micromanagement speedruns, where velocity charts are weaponized like some kind of bizarre productivity Hunger Games. And here's the kicker. Scrum isn't ever actually prescriptive. It's intentionally lightweight so that you can adapt it and modify it and change it. What do most companies do? They treat it like IKEA furniture instructions, following every step poorly, ending up with a wobbly delivery process and at least one missing screw in the end, because we always have screw missing in IKEA. So is Scrum a scam? Am I trying to say it's bad? No, not at all. Done right. It's incredibly powerful. Done wrong, well, it's the business equivalent of thinking that The Purge
3:09 Speaker 00 was a quirky family comedy, because it wasn't. But I think there's a key, and I'm going to give you the key to unlock success in Scrum. The key is to understand that Scrum is an agile delivery framework. There I said it. I'll say it again. Scrum is an agile delivery framework. If you're focused solely on delivery and output, and you're not focused on outcome and behavioral driven things, you're going to lose the game. So in order for Scrum to be successful, you need to bookend it. You need to stop talking about just the delivery piece. You need to start talking about the initiation and ideation and discovery. What is the MVP? Who's our target audience and persona? What systems are going to be using? What does a day in a life look like if we did
3:54 Speaker 00 a walkthrough? These are the things you should be focusing on. These are the things you should be talking about. And the problem is, most people do Scrum, just focus on that one piece, delivery. And leaders don't help the matter any. Leaders sit here and their focus is, what am I going to get? When am I going to get it? And how much is it going to cost? They're so driven by the actual production of something, that they lose sight of the outcome focused of, let's build the right thing the first time. So in order for Scrum to be successful, you need to not only understand How it integrates into business agility. But you also need to understand what those roles and accountability is are. Why we have those meetings? And we need to make sure that we're not selling our soul or giving away our life
4:37 Speaker 00 or having a life of the will to live sucked out of us by something that we're methodically trying to call scrum. That's going to do it for today. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledad.com. I'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. Bye now.
Previous Project Manager vs Product Manager vs Business Analyst Next Are You Protecting Your Team Against the Right Thing? - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated