Pod Insights The Agile Daily Standup - AgileDad Why We Killed Scrum Sprints Forever About this episode Why We Killed Scrum Sprints ForeverWhen I started my journey as a product manager, I went through every article, book, and video I could find about Scrum. Sprint planning, daily stand-ups, reviews, retrospectives — the whole shebang... 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:16 Speaker 00 All right, it's time for another eye roll episode of the Agile Day with Stand Up Podcast episode. Why did I call it an eye roll episode? Because this article was sent in to me to review. It's called "Why We Killed Scrum Sprints Forever" from Sovik Sarkar. Now, I wasn't gonna say your name initially because I didn't know whether I liked the article or not, but then after reading it, I decided to say your name, and you'll see why in a second. "When I started my journey as a product manager, I went through every article, book, and video I could find about Scrum. Sprint planning, daily stand-ups, reviews, retrospectives, the whole shebang." Okay, let's pause there. So, interestingly enough, sprints capitalize,
0:59 Speaker 00 planning's not. Daily stand-ups instead of daily scrums, reviews, demos, you know, it's just, there's a lot left to be desired just right there in the first paragraph. So, that concerned me even more about whether this person is going through the motions or actually executing. Let's continue. "When it came to my own venture, I implemented the entire Scrum framework, believing this was the path to product success. We followed everything by the book to keep our teams on track and hit our targets, only to eventually abandon most of it. Like many organizations before us, we discovered that rigid adherence to Scrum was actually hindering our agility rather than enhancing it. Monday mornings were consumed by sprint planning sessions where we debate story points and slice user stories that would
1:41 Speaker 00 inevitably change days later. Two-week sprints created artificial deadlines that are rarely aligned with how our features naturally developed. Our engineers were context switching to fit sprint boundaries while QA rush testing at the end of a sprint, creating ripples of technical debt." Okay, let's pause.
2:00 Speaker 00 First of all, wow, there's, there's so much to digest here. Yeah. First of all, debating story points. Story points aren't part of Scrum. So I don't know why you were debating story points. This is interesting, right? I mean, nowhere in a Scrum guide does it even mention story points or slicing user stories. It does say to keep work small in size, but it doesn't say to slice user stories. Talking about two week sprints, that's great, but making it an artificial deadline is not so great. So what I'm saying is it feels like to me, someone was looking for a checklist of exactly what to do. And you created one and you got exactly what you expect from a checklist failure. Because what's going to happen is if you try to execute Scrum in such a way where it's a pass fail,
2:43 Speaker 00 and you solely focused on checking the boxes and making sure you're delivering the things that align with the checkboxes, you're going to quickly discover that Scrum is an agile delivery framework and that it doesn't incorporate things like initiation, discovery, release planning. And you're going to quickly discover that it only fills one small hole, the delivery hole of the four-part process. So he goes on to say, as a product manager, my responsibility was responding quickly to market needs. Yet I was simultaneously locked into sprint commitments made days earlier. We noticed that even though Scrum is an agile methodology, it is filled with redundancies that ultimately make it unagile. Let's start there. That's false, right?
3:24 Speaker 00 Scrum is not an agile methodology. Scrum is an agile delivery framework. Let's make sure we get it right. And you might say you're splitting hairs. No, I'm not. This is a big difference. Scrum is designed to focus on optimizing and making agile delivery more efficient. That's it. Period. And if you do it correctly, it's not filled with any redundancies. The problem is people aren't executing, initiate ideation or discovery before they get to delivery. And it's causing redundancies because, well, you don't know what you want. So you're looping around that and that is redundant. Number two, as we sliced our development timeline in the sprints, we saw complacency at the beginning of a sprint and a rush at the end of a sprint.
4:07 Speaker 00 Let's pause there. This is a behavioral driven issue right here. What this means is that you weren't honoring WIP correctly. That the team felt like either A, they had too much or too little work and that they felt like the timeline didn't match the scope of work that was being given to them. It didn't mean that they were trying to do this to adhere to Scrum or to a sprint. It just meant there was frustration that you didn't recognize. Three, we'd meet every single day for daily scrums, even though there is nothing to discuss. Okay, let's stop there. Three, there's always something to discuss for the daily scrum. The daily scrum is not about status updates. The daily scrum is about accountability and it's about where are you or what did you get done yesterday?
4:49 Speaker 00 You might have heard, popular or not, the whole Doge thing about what five things did you do this week? The daily scrum is there to identify what one thing you did in the last 24 hours that's going to move forward with the project. And I think that's important to know because sometimes you can identify potential bottlenecks there. Sometimes you could see when people are putting in a lot of extra effort. It's just really, really nice to have that type of flexibility, right? Okay, so let's go to number four. Number four says, in the event of new information, there's no flexibility to restructure an ongoing sprint. That is also false. Uh, let's finish it though. It says either we had to abandon the new information till the next sprint, or we had to terminate a sprint altogether.
5:28 Speaker 00 Once again, false. There's no rule saying you can't remove items from our sprint. You can add items to a sprint at the beginning of the sprint, but you're not allowed to touch a sprint or add things to a sprint once it's in motion. But there's no rule saying you can't take items out of a sprint. And when a team has a natural effect of finishing early and asks, hey, what should I work on? There's nothing stopping you from saying, go get a head start on a first item in the next sprint, which could be the item that you originally wanted to push into the current sprint. So what I'm trying to say is there's a time and a place to terminate a sprint. There's a time and a place to pivot. But I guess the bigger message is you need to understand that there is actually a lot of flexibility if you understand how to implement agile correctly.
6:09 Speaker 00 And number five, it's important to correctly estimate the capability of the development team for sprint planning. And no matter how well we knew them, we would either overshoot or undershoot and the situation becomes worse if one of our developers is taking a vacation or sick. Let's pause. Number five, you are talking about capacity and not velocity. This is also a common problem. If you don't understand how to navigate velocity and you're solely focused on time-based, how long is Johnny gonna be here? You are gonna fail because there's no way to tell. Different types of work take different people, different amounts of time. Based on their skillset, the tools they have, the way they learn, their education level, there's so many things to take into consideration.
6:52 Speaker 00 You can't just go in blind and expect everybody to be perfect with their time. That's just not gonna work, right? It just never works. So, how do you fix this? How do you fix this conundrum? How do you get there? You need to separate velocity and understand that velocity is the number of units a team can complete. When you think about velocity, think about volume, right? If this is a sprint, this water bottle that I'm holding, if this is a sprint, how many ounces of water can it hold? The number of ounces has to do with the number of story points. Now, each team member might be more or less thirsty, or maybe some of them like water and some of them don't. So what's gonna happen is in this case, I'm holding a standard-sized 20-ounce bottle. So they will be able to do 20 units of work, yes?
7:36 Speaker 00 Now, if I had a more experienced team, their sprint might look like this hydro jug. They could finish a full 40 units of work, right? It doesn't mean they're better or worse. In fact, what it means is there might be a time where this team starts working on something they're not familiar with and can only do 20 units of work. But regardless, you don't want to try to overfill the container with more points. If I tried to put 30 units in this one, it would overfill and it would be impossible for the team to catch up. If I tried to play tradesies and switch things out mid-sprint, oh, well, they're the same t-shirt size. That's not gonna work either. Because when you spread things out like that and you split them and you try to do tradesies, what winds up happening is the team says, "Well, that's great. We don't know anything about that. We didn't research that item. We researched this item over here at our backlog refinement session."
8:21 Speaker 00 So what I'm trying to say is, in order to keep things flowing, in order to keep things fair, you need to make sure you understand that A, nothing should ever be added to a sprint. B, it is perfectly fine to take something out of a sprint. C, the natural effect will be the team finishes early and the advice you give them is to go get a head start on the first item in the next sprint.
8:43 Speaker 00 Notice I didn't say pull it in. That's important. And then D, don't leverage time to determine whether you're overshooting or undershooting. Figure out the number of walls the team can paint collectively, not argue over who's the better painter. There you go. He goes on to say, we believe deeply in agile practices. That's why we asked ourselves whether our implementation of Scrum was actually serving the goal of the company, or if we become servants to the framework instead. In this case, by the way you described it, you became a servant of the framework. You didn't understand the goal of Scrum, nor did you implement it in such a way that everyone could catch on and do it. So he goes on to say, after months of frustration with traditional Scrum, we gathered to reimagine our development process.
9:25 Speaker 00 And the result is what we now call a release candidate approach, a framework that helps us focus on a release candidate instead of sprint boundaries. So basically it's a Kanban flow is what you're doing. It's just a longer Kanban flow. So I think what you need to do is totally reconsider looking at how you approach Scrum or Agile to begin with. And take a minute to figure out, did you have your head on straight about what it really is and how it really works? Or were there areas that we had some confusion that could have been corrected with a strong coach? I think that, you know, trying to create a new or innovative framework that just piggybacks off of, you know, feature-driven design.
10:09 Speaker 00 I think that you're in the right place when you start talking about a release candidate. But what you're trying to do here is you're trying to take principles from SAFE, the worst principles from Scrum, and principles from other places and bundle them together into a traditional flow format. And what I can tell you is over time, you're going to quickly discover that you're going to lose autonomy, you're going to lose flow, that even experienced candidates are going to feel like they're not getting what they need to get done, done. They're going to start looking for other opportunities and it's going to be ugly. So what I'm saying is instead of experimenting with this new flow, try experimenting with limiting whip, try experimenting with understanding team needs, try experimenting with why do we do story points? What are they and how do we pivot and adjust?
10:52 Speaker 00 Figure out how to get predictable. What I can tell you is all my teams get to 85% predictability. There's no reason why you can't either. So make sure you understand what's going on, that you can actively correct and that you know exactly what you need to do to help these teams be successful. Because if not, they're going to look for a job over here. They're going to look for a job over here. They're going to look for a job wherever they can. And that's not where you want them to be. Okay, that's going to do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledad.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 Do Your User Stories End in a Coffee Break? - Mike Cohn Next Exploring How To Discuss Sensitive Topics From a Spiritual Approach Page updated November 6, 2026 · transcript and summary are machine-generated