Pod Insights The Agile Daily Standup - AgileDad Why I Switched to a Hybrid Approach and Tripled My Team’s Delivery Rate About this episode Why I Switched to a Hybrid Approach and Tripled My Team’s Delivery Rate
Agile was supposed to be the answer. Stand-ups, sprints, retros, these rituals promised faster delivery, happier teams, and stakeholders who finally felt in sync with engineering. For a while, it worked. My team hit a rhythm, delivered features quickly, and felt engaged in the process.
But over time, the cracks showed.
Velocity slowed to a crawl. Stand-ups became theater. Engineers dreaded sprint planning. Stakeholders kept asking when features would actually be done. And remote work made it worse with Zoom fatigue, Slack overload, and endless context-switching draining the energy Agile was supposed to give us.
At first, I blamed the team. Maybe we weren’t “doing Agile right.” So I doubled down on the rituals. More retros, stricter sprints, tighter velocity tracking. But the harder I pushed, the more Agile turned into bureaucracy.
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 I knew the day would come where someone would send me an article or give me this type of input. And here it is. So this article was sent to me by someone who recently took one of my advanced Scrum Master classes. And this is the title of the article. It says, When Agile Fails, Why Switch to a Hybrid Approach and Triple My Team's Delivery Rate? Doesn't that sound exciting? Tripling the delivery rate? Dot, dot, dot. Okay, I think you know where I'm going to go with this, right? If your focus is on delivery, that means your focus is on output and not outcome. So let's see where they went with this article. Agile was supposed to be the answer. The stand-ups, sprints, retros, the rituals promised faster delivery, happier teams, and stakeholders who finally felt in sync with engineering
0:59 Speaker 00 instead of Backstreet Boys. It doesn't say that I added that. For a while, it worked. My team hit a rhythm. Rhythm is a dancer. Delivered features quickly and felt engaged in the process. But over time, the cracks showed. Velocity slowed to a crawl. Stand-ups became simple theater. Engineers dreaded sprint planning. Stakeholders kept asking when features would actually be delivered. And remote work made it worse with Zoom fatigue, Slack overload, and endless context switching draining the energy Agile was supposed to
1:37 Speaker 00 give us. At first, I blamed the team. Maybe we weren't doing the Agile... Oh, it says it. Maybe we weren't doing the Agile right. So I doubled down on the rituals. More retros, stricter sprint guidelines, tighter velocity tracking. But the harder I pushed, the more Agile turned into bureaucracy. And that's when I did something I never thought I'd do. I stopped running pure Agile and built a hybrid approach that combined the best of Agile with the structure of traditional project management.
2:16 Speaker 00 The results shocked me. Within six months, our delivery rate had tripled. Stakeholders trusted us again. Engineers had room to breathe and planning finally felt like it was serving us, not the other way around. Okay.
2:32 Speaker 00 I don't know what to pick apart first. There's so much here to pick apart. My goodness. Well, let's, let's go up a little bit. Let's start up here. So
2:48 Speaker 00 let's go here. Agile was supposed to be the answer. Here's the quote, "Stand-up sprints, retros, and these rituals promise faster delivery, happier teams, stakeholders find a felt and sync for engineering." Okay, let's pause.
3:00 Speaker 00 That's not agile. What you just described is the delivery portion of the agile framework. What you described is delivery. You did not talk about ideation or initiation, discovery or release. You simply focused in on a delivery piece that sits inside of agile. And you wondered why it didn't work.
3:21 Speaker 00 Agile delivery is not the answer. Agile holistically is the answer. There we go. All right, that's good. No, I'm kidding. I'm not going to sign off yet. But there's still more to talk about. But she said her team hit a rhythm and were delivering features correctly. Everything was great. Do you know why? Because in order for you to launch agile inside of your organization, you had to have ideation and discovery complete so that the first rounds of delivery could take place. I'm going to say it again. You had to do a little bit upfront to make delivery work. The second you decided, "Oh, it's wonderful. It's great."
4:00 Speaker 00 And you stopped focusing your attention on ideation and discovery and started dedicating 150% of your delivery, 150% of your attention straight to delivery. That's when it failed. That's when it broke down. And that's where quote unquote, "The cracks showed."
4:16 Speaker 00 Velocity slowed to a crawl because velocity wasn't the metric you should have been mentioning or measuring. Standups became theater, probably because the team didn't feel like they were effective. I'm just saying. Engineers dreaded sprint. Of course they did because there was not enough preparation. Stakeholders kept asking what features would actually be done. Of course they did. Because they were promised things over and over again and nothing actually got delivered. You kept breaking promises and you broke trust. Then you add in Zoom fatigue because people were having 100 meetings because they didn't talk directly to the stakeholders. Slack overload because people are pointing fingers and accusing each other in Slack and talking to each other endlessly, day and night, trying to get things done. Context switching all over the place because you weren't limiting work in progress.
5:00 Speaker 00 I think you get where I'm going with this. You were not running pure agile. You were running pure insanity. You were running you you took the word sprint literally and had the team running as fast as they could for as long as they could without giving them a chance to catch their breath or stop for Gatorade. You you just you just took and annihilated. You took what agile really stands for, all the tenants, principles and goodness of agile. And you crushed it.
5:28 Speaker 00 I I'm going to continue. Just I don't want to, but I'm going to. Why agile fails and it's not your fault. Agile was created over 20 years ago for software teams in a very different world. Back in the day, teams were co-located, projects were smaller and customer feedback loops were faster. The principles still matter, but the context has changed.
5:52 Speaker 00 Agile is exactly the same as it was 20 years ago. The only difference is we figured out that it doesn't just work for software teams. It works on everything. And I got news for you. The speed of delivery has gotten faster. The feedback loops can come faster. The only thing you have to do is stop throwing so many things in the air at the same time. Here's when Agile started breaking down for us. Ceremonies became overhead. Stand-ups turned into daily status reports because you weren't asking the right questions. Sprint planning dragged into two-hour debates because you didn't time-box the 40 minutes. Retros felt repetitive because you weren't gathering the right information. You weren't asking the right questions.
6:32 Speaker 00 What started as lightweight rituals slowly calcified into heavy bureaucracy because you let it. Because you let it get to that point. Velocity replaced outcomes. We obsessed over story points, burn-down charts, and sprint velocity. Yeah, because all you were focusing on was output, delivery. That's all you were focused on. You didn't care about outcomes. You didn't care about happy customers. Then stakeholders chimed in and said, "We don't give a crap about your abstract t-shirt sizes and numbers. All we want to know is what time are we going to get that working thing in our inbox?" Because you broke promises. You failed to deliver and broke trust.
7:16 Speaker 00 This isn't rocket science. This is very, very easy if you do it correctly. One-size-fits-all didn't fit our projects. Well, good thing, because the very first thing I teach in my Scrum Master and Product Owner classes is Agile is not a one-size-fits-all approach. You went on to say Agile thrives in environments with short feedback loops. It does, but it also works with long feedback loops. We weren't always iterating on features. That's great, you don't have to. We were doing system migrations, complex integrations, and research projects. This type of work didn't fit neatly into two-week chunks. Okay, do three weeks, do one week, do four weeks. The point I'm trying to say is, pick a lengthier sprint and go for it, but it's not a one-size-fits-all
8:01 Speaker 00 initiative. You don't have to marry to the perfect things. Remote amplified the cracks. In-person Agile thrives on sticky notes and whiteboards. Remote Agile, it thrives on sticky notes and whiteboards. In-Miro or Mural, it's the same exact thing. But they say remote means more Zoom calls, more Slack channels, more tools. The overhead multiplied. The face-to-face conversation principle collapsed under the remote reality. Agile was the villain. It was just designed for the complexity and distribution. It wasn't designed for the complexity and distribution of our work because we're different. Okay, Caillou, I'm tired of this complaint.
8:41 Speaker 00 You are not different than anyone else. Your work isn't different than anyone else. This might be one of the biggest cop outs I've ever heard. Yeah, I called you out. I said it's a cop out.
8:55 Speaker 00 The overhead didn't multiply because of what you did. The overhead multiplied because of what you didn't do. You didn't establish relationships with stakeholders upfront. You didn't implement electronic sticky notes and whiteboards so people could feel like they were in person. You didn't put the right tools in place. You didn't get the developers the information they needed. So they went behind your back and established all this extra communication and tried to solve problems that they shouldn't have been trying to solve themselves.
9:20 Speaker 00 Yes, I went there. Why hybrid made sense? Well, the alternative wasn't to throw a agile and run straight back to waterfall for safety. That probably would have been just as painful. Instead, I decided to borrow from both. You're a hero. You didn't borrow from both. Do you want to know what you did, Ms. Hybrid? You didn't even do hybrid. You decided, hey, agile holistically has four phases and not one. I'm going to focus on ideation and initiation to make sure that the ideas that we have are good ideas, that they're valid, that they're vetted, and that they apply to our customers. Then I'm going to do lightweight discovery, where we identify and try to build a minimal viable product
10:03 Speaker 00 by identifying who our targeted personas are and putting together a vision and strategy statement that everyone understands. For our target customer that is struggling or suffering with this problem, our product or service is this type of product or service that provides a key benefit or compelling reason to buy it. Unlike our competitors' product or service that sucks, ours is different and better for these reasons. Then you affinity clustered the features together and created a map, a story map, journey map, ecosystem map. I don't care what kind of map it is, perspective map. You created a map of how it was going to walk through a day in life. So by the time it got to delivery, it actually worked. And then you labeled it hybrid.
10:38 Speaker 00 All you did was adhere to what Agile really is. And by the way, the same thing that I've been teaching for 23 years. I'm gonna say that again in case you didn't hear me. It's the same thing I've been teaching for 23 years. You didn't invent something new. You didn't like create some magic serum or potion, Miss Harry Potter. All you did, oh my goodness, and I love this here. Think of it like cooking. Agile is the salt and waterfall is the sugar. On their own, they don't work, but blended, they made their recipe come alive.
11:15 Speaker 00 I got news for you. Some things need salt. Some things need sugar. You try to mix those two together and it's gonna taste pretty nasty. I grew up in New Orleans. My son's a chef. I should know these things.
11:28 Speaker 00 What did hybrid look like for us? After months of trial, error and team feedback, we landed, we finally landed on a hybrid model that worked. And here's I broke down. Long-term visibility with quarterly roadmaps. I teach that in all my classes. We replaced sprint to sprint chaos with a true 90-day roadmap. This gave stakeholders confidence without locking us into inflexible Gantt charts.
11:53 Speaker 00 Sorry, I threw up a little bit in my mouth. That was terrible. Excuse me.
11:58 Speaker 00 That was a natural reaction to what I just read. That's horrible. You can have a 90-day roadmap without any issue.
12:09 Speaker 00 I want a 365-day roadmap, an M plus two, this quarter plus the next two. I want to have a, what is that, 270? I want to have a 270-day roadmap. And I think it's fine. You can outline major initiatives. You can break them into quarters. Oh my goodness, this is all things that are part of Agile. We focus on short-term execution with light sprints. We still run our two-week sprints, but with much lighter ceremonies. We cap all our planning meetings at one hour. I've been teaching that for 23 years, an hour or less. Stand-ups, async and a shared channel, no more than 15 minutes wasted daily. How about 30 seconds per person not to exceed 15 minutes? That's what I teach. Retros, one or two focus questions, not a laundry list.
12:52 Speaker 00 How about making a quadrant on the board with four panels and giving everyone a sticky note and letting them do it the right way? That gave us our rhythm without all the bloat. Continuous flow for maintenance work. Not everything belongs in a sprint. Bugs, small features and support tasks with your combine boards. This eliminated the overhead of trying to size tiny things into story points.
13:18 Speaker 00 You don't want to do that. You can do Scrum Bon and you can make those tickets and you can put them on a combine board. I'm fine with that, but you need to allocate a percentage of story points to known work and to unknown work. And if you do that, it's going to solve that problem too. Once again, this isn't something brand new that you invented. This is something I've been teaching for 23 years. Milestone tracking instead of velocity. Oh, I can't wait to hear this one. We shifted from how many points do we burn to what outcomes do we deliver? Progress was measured by milestone shift and customer value created, not by an abstract velocity chart.
13:53 Speaker 00 If you do burn up charts and you're tracking velocity using a cone of uncertainty, all you're doing is becoming predictable.
14:01 Speaker 00 Doing it the way you're describing takes away all predictability. I'm telling you right now, you might have this little jolt of excitement because you did all these wonderful things, but all you did is implement agile in a more complete way. Let's get to the last one. Remote collaboration with a tool. This was the glue that made our hybrid work in a remote first world. Agile rituals collapsed for us on Zoom, but in our new tool, a virtual office platform, we created a collaboration layer that felt natural again, so we could talk to each other. Planning sessions could happen in shared rooms. Teams split into smaller spaces for focus work. AI note taking integrations automatically capture decisions and action items so we could hold people accountable.
14:46 Speaker 00 This sounds like the most horrible place in the world to work with the exception of you implementing agile.
14:53 Speaker 00 The result was half the meeting time and double the alignment. Yay.
15:00 Speaker 00 Okay, then they won't give you an example. Here's the results. Here's what happened within six months of us switching to the new hybrid model. 3X delivery rate. We shipped three major features in the same time it previously took to ship one.
15:18 Speaker 00 40% less meeting time. Stakeholder trust rebounded, team morale surge. Okay. How about this? Do you want to know why you had 3X delivery rate? Because you limited work in progress for a change and you had a little bit of planning done upfront. You should get anywhere from three to five times the delivery rate if you do it correctly. 40% meeting time. Try this. Every team that I've coached has 70% less meetings. 70% less meetings. This isn't rocket scientists. Stakeholder trust. Of course it did because you're finally delivering things that you said you were. Team morale surge. Of course it did because you found ways to keep them out of freaking meetings, which is their number one complaint. And she is a list of lessons learned.
16:03 Speaker 00 But how about I bypass her list and I give you my list of lessons learned. Lesson number one. When someone posted an article like this, take it at face value. They didn't do anything spectacular, magnificent, or incredible. All they did was implement agile the way it was supposed to be implemented. And they're trying to be a superhero for it. Number two. If you don't have proper training and coaching inside of your organization, go find it. Whether it's me, the team at Agile Dad, or another team that you trust. Get somebody in there to lay these foundational things down. So you don't take months to figure out how to do it correctly and then call it something that you invented. And finally, if you want to increase team morale, and I'm going to go here. Organizational morale. Provide leaders with predictability.
16:47 Speaker 00 Give them graphs and charts that they can count on, including red light, green light, burn up, cumulative flow reports, things that are going to help them. Do apply a scrum bond approach where you have combo boards to help manage work that's unknown or service-based work and then have the known work contained in a scrum sprint. Allocate it be a story point. Don't be afraid to do that. But the most important one, make sure you remember there's four phases to agile. Ideation, discovery, delivery, and release. Don't live in delivery. If you're living in delivery, you got a lot of learning to do. That's going to do it for this episode. Man, I got hot. If you have a question or topic you want to discuss, or if you just want me to shred somebody like I just did, feel free to reach out at learnmoreatagiledad.com and I'd love to hear from you.
17:31 Speaker 00 As always, we encourage you to stay healthy, stay well, and most importantly, stay agile, my friends. Until next time, do take care.
17:43 Speaker 00 Don't get caught doing the agile. Bye.
Previous AI Is Changing The Economics of Software Development - Mike Cohn Next Celebrating PI Day! Page updated November 6, 2026 · transcript and summary are machine-generated