Pod Insights The Agile Daily Standup - AgileDad Scrum Is Dead - Here Is What Killed It! About this episode Scrum Is Dead - Here Is What Killed It!
My dear friend Katharine reached out to me and asked me to review and reply to this LinkedIn post. NOW I perfectly understand why! Great job bringing this to my attention.
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 All right, it's that time again for a conversation. I want to let you know, my dear friend Catherine sent me a message on LinkedIn about a post that was made, and she said she would like to hear me chime in on it and make a good podcast episode. So I'm not going to tell you the author is, but I am going to read the post to you. Now, there's a couple of things interesting about this post. First, the post was posted, then the post was edited, then a flood of comments came in, then the comments were turned off. So this post tells me that it was quite controversial, but at the same time, I feel like this author had a golden opportunity to let something explode, and they didn't let it percolate. So this is one of those things where I'm tempted to grab the same post and
1:00 Speaker 00 repost it and let the comments fly. But before I do that, let me read you the post, and I'm going to give my opinion as we go. Let's get started. So of course, it starts with, "Scrum is dead, and here's what killed it." Pause. We all know how I feel about these "Scrum is dead, Agile is dead" posts. I've probably seen a thousand of them. And my friend Catherine said the same. She says, "I'm starting to see these more and more. This is something that's becoming prevalent." And I don't know that the authors have bad intention when they do it, but I don't know, sometimes they realize the harm that they're causing, or I shouldn't say harm, the turmoil that they're causing in community when they do it, or maybe they do. It says, "AI did not just make your team faster, it changed the physics of software development." That statement I agree
1:43 Speaker 00 with. AI is here to stay. AI is not going anywhere. The best Python coder in the world is ChatGPT, period, end of story. The best JSON coder is also ChatGPT. Yay. But my point is, if you put code into into any of the LLMs, it's going to tell you where there's defects in the code, where it's deficiencies, how to make it more efficient, how to make it operate better. It's going to give you all the answers that you're looking for. As far as development is concerned, one of the predictions that I made my top three predictions on January 1st of 2026, which is about three months ago, I said that AI was going to change the way that a developer works, that you're no longer going to have people just pounding away at code.
2:22 Speaker 00 Instead, you're going to have people who are in charge of quality management, integration, change management, all of those responsibilities. So the the perception of what a developer does and what they physically do is severely going to change. At least over the next two years, I believe you're going to start to see it evolving to something completely different. Why this matters? Scrum was calibrated to human speed work, sprints, story points, velocity. All of it exists to manage one constraint. Humans are slow and unpredictable. AI just eliminated that constraint. Okay, pause. That's not wholly true, but it's also not wholly wrong. Let me explain what I mean. Scrum was not calibrated. Well, let me take that back.
3:05 Speaker 00 Scrum was calibrated for agile delivery. It focused on delivering products and services. And whether you used electronic assistants to get there, whether you use humans to get there, it focused on delivering based on outcome. Okay, I get it. That's true. All of those things are true. Or at least it should have been delivery based on outcome. Lots of times it fell into the delivery based on output. But in most cases, we're going to give this team the benefit of the doubt and say they were they were tracking points and sprints and all this good stuff so that they could achieve the right outcome. We're going to give them the benefit of the doubt. The part here that's interesting is all this all of this exists to manage one constraint, that humans are slow and unpredictable. Humans are slow? Yes. Unpredictable? Not quite. In fact, I would argue humans are often more predictable than AI.
3:50 Speaker 00 And I think what I'm saying is sometimes you can look at something and know who did it just by the way it's presented, as opposed to AI where everything kind of looks the same, which is really interesting. You can tell AI did it, but you don't know who, which is, I guess, let's continue and see where it takes. So three things broke simultaneously. Okay, let's do these three things. Three things are, one, roles justified by capability are meaningless when AI can do anyone's job. Ah, I can't chew on that one. I'm sorry. So roles justified by capability are becoming not as meaningful, but I wouldn't go as far as to say they're
4:31 Speaker 00 meaningless. AI can do most people's job better, but AI cannot do everything. It still requires human oversight, and that's an important declaration that we need to understand. You can't do it all without AI. Two is velocity based planning collapses when effort variance becomes infinite. Pause. Effort and velocity should never be used in the same sentence. This is a clear misunderstanding of velocity. A velocity is a measurement of volume. It's the volume of work or amount of work that can fit inside of a two week container, a sprint, or a three week container, whatever it might be. The point I'm trying to make, no pun intended,
5:10 Speaker 00 is that velocity measures volume, capacity measures, or in this case, effort measures, the amount of capacity a team member has. Capacity should not be managed across a team, and velocity should never be managed at the individual level. And if you have that separation, that that solves this problem. And finally, the third one is the two week sprint is now the equivalent of a 20 week waterfall cycle. I don't believe that either. I think that if you've read too many of Jeff Sutherland's books, you might believe that. But what I honestly believe is we're not at the point where we're moving that fast. We're not at the point where we're getting productive things that fast. I still feel like one week experience and two weeks experience are good. I just feel like the ability to do the work more effectively and
5:55 Speaker 00 better focus on outcomes, I don't know that at first it's going to speed us up as much as it's going to make us better focused. And I think that's the difference here, where you're saying everything's just going to speed up and the physics are completely different and everything's going to change. I'm saying things will change, but it's going to take time. But what it's going to do is it's going to give us the greater ability to focus on what we really should be doing. And then he goes on to say, but here's what did not break. I hope this is good. The need for someone to own a decision. There we go. AI can build anything. It can never be held accountable for anything. And the people that have the best judgment about usability are designers. Feasibility are engineers. Viability are product people.
6:39 Speaker 00 This is something that I have been teaching for over 10 years. The concept of BAFATA, a product owner should never be thrown at this alone. They should have a business analyst that understands consumer awareness. Consumers wants, needs, wants and desires. A functional analyst that understands strategic alignment. Where we're trying to go as an organization with our North Star goal. And then a technical analyst who can speak on behalf of the team with regard to technological feasibility and what makes sense. I have said this for a long, long time. But I feel like finally the message is getting through. And I kind of want to thank this author because I feel like even though you may not have intended to stir up a hornet's nest. The fact that you did, it's just a trigger that this is a good topic that we need to talk about.
7:23 Speaker 00 But what's funny to me or amazing to me is that I've been talking about this topic for 10 years and it's finally coming to the surface. Once again, this is probably the fourth time in my career that this happened where I've talked about something and everyone said, that's blasphemy. It'll never happen. And then 10 years later, here it is. Uh, the good news is it's not too late for you to jump on board and get some help with this. Uh, Catherine, you did a fantastic job pointing this out to me. Thank you. Thank you. Thank you for telling me about the article. And I know what you're going to say, Nancy, you dare me to repost it. Guess what? I'm going to repost it because I want the comments to fly. Thank you so much, Catherine. You are awesome sauce and I appreciate all of the things you send to me. And, uh, yeah, I'm glad that I got to do this one for you. If you have a topic you want us to discuss, feel free to reach out, learn more at agiledad.com. I'd love to hear from you or you can reach out to me on LinkedIn like Catherine did.
8:08 Speaker 00 And as always, I encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye now.
Previous That's What Friends Are For Next The AI TPM Landscape Page updated November 6, 2026 · transcript and summary are machine-generated