Pod Insights The Agile Daily Standup - AgileDad Agile in 2026 Looks Nothing Like Scrum About this episode Agile in 2026 Looks Nothing Like Scrum
That delay cost us 42,000 failed checkout attempts and a week of executive explanations. Nothing was broken in the code. The failure was procedural. The fix was ready. The sprint boundary said no.
That was the moment we stopped pretending Scrum was helping us ship.
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 I think this is just one of those weeks. I don't necessarily understand exactly why, but all the articles this week that people have been sending me are just same, same vibe. Agile 2025 looks nothing like Scrum and teams are better for it. Let's have that conversation.
0:34 Speaker 00 The delay. It cost us 42,000 failed checkout attempts
0:40 Speaker 00 and a week of executive explanations. Nothing was broken in the code. The failure was procedural. The fix was ready. The sprint boundary said no. That was the moment we stopped pretending Scrum was helping us ship. The truth is, Scrum is designed to help us, but on paper, when everything was correct, two weeks sprints, clearly defined backlog, well-defined stories, a committed sprinkle, the release candidate was done on Wednesday. QA signed off on Thursday morning. The rollback was approved. But production traffic does not care about sprint ceremonies. A pricing bug surfaced Thursday afternoon. The fix was a four-line change. It sat in a branch for two days because it was not in scope.
1:24 Speaker 00 And by the time it shipped, the damage was already done. This is why Agile hurts differently in 2026. Let's, let's have this conversation.
1:36 Speaker 00 Expectations of people in 2026 far outweigh the predecessors. And what I mean by that is with the introduction of AI-assisted help in doing all these different things, we're finding that Organizations are leaning in so hard on AI as we had our discussion with Mike Cohen, the collaboration is slipping by the wayside and people aren't doing the right levels of commitment when it comes to what they're actually doing. Users are expecting continuous correctness, executives expect the daily signal, infra-failures cascade in minutes, not in iterations, and when process introduces latency larger than the bug itself, the process becomes the actual risk.
2:20 Speaker 00 This all happens because we're focusing on Scrum as an agile delivery framework. Scrum works beautifully in a stable domain, clear requirements, predictable change, bounded teams, low coupling, that's why it became a default for many organizations. Production systems in 2026 looked nothing like that. We ship behind feature flags, we deploy multiple times per day, incidents trigger design changes, observability feels like roadmap decisions, the work arrives asynchronously and expires quickly, the sprint model assumes work is batchable, production work is not. The moment you operate at scale, sprint commitments compete with incident response, revenue impacting fees or fixes, infrastructure regressions, regulatory changes.
3:04 Speaker 00 Scrum doesn't fail because teams are undisciplined, it fails because it encodes a fixed cadence into a variable environment. The symptom is subtle at first, stories start to roll over, high fixes feel disruptive, planning becomes defensive, eventually, velocity becomes fiction. Let's pause. This has more to do with understanding and discipline and has to do with any of the things you're describing. What it sounds like to me is that maybe your organization had some poor agile training or a poor agile coach at some point that placed Scrum in a doctrinal format instead of in a dogmatic format that would, or a dogmatic format instead of a pragmatic format that would allow you to make the adjustments and pivots that you're trying to make.
3:45 Speaker 00 And the patterns that you're describing are the symptom of not honoring WIP limits, not honoring work in progress limits, and they're also symptoms of not understanding how to govern Scrum better in the organization. So if you're following Scrum correctly, it should feel more like a Scrum bond approach, approach, especially today. And AI should be clearly integrated in, and organizations and developers should be focused more on quality management and integration, which will solve all of these problems. It just feels like to me that you're not focused on the right things. And organizations are starting to face problems where sprint commitments create artificial scarcity. Teams delayed high signal work because
4:28 Speaker 00 it wasn't planned. Urgent fixes were treated as scope violations. Change, we remove sprinkles. That's not going to solve the problem. Working under a single prioritized queue, engineers pulled the next item when capacity freed up, priority was reevaluated, so you went combo. No sprint boundaries, no rollover, and no commitment theater. The result, medium lead time dropped from 9.4 days to 2.1 days. P99 lead time dropped from 27 days to 6 days. Emergency fixes shipped same day without escalation. Trade-off, forecasting became problematic, not deterministic. Stakeholders had to learn ranges instead of dates. Yeah, there's so many things wrong with this. And gosh, I'm just reading all these. Work shaped by failure,
5:12 Speaker 00 not epics. Large epics hit risk. Teams delivered entire business features for discovering performance usability errors. Once again, this is just poor planning. Everything that I'm seeing here is all symptomatic and problematic instead of making sure we're doing things the right way. So I guess instead of finishing the article or discussing who the author is, I'm just going to stop here and say this. The disappointment that I'm facing right now is more because so many people are applying Agile incorrectly and applying Scrum incorrectly due to misunderstandings and misalignments that have happened in the past. And with AI pushing so hard right now, speeding things up, it's causing us to speed up the frequency of the errors and speed up the inconsistency and speed up the lack of communication. And
5:55 Speaker 00 this is causing bigger and bigger problems. So I don't know that Agile is the problem or that Agile is broken. I think, in fact, if anything, Agile is amplified and showed us that These problems are systemic and have been there all along, but now they're amplified so that we can see them actually happening, which is incredible. And it doesn't necessarily mean I want to be careful, slow down, or stop. What it means is we need to pivot and adjust how we're approaching work. We need to honor whip limits and we need to make sure we're focused on the right things that lead us all the way through Initiate, Discover, Deliver, and Release so that we can have a system flow that works inside of our organization. Sounds pretty easy, but not without the right level guidance and coaching necessary in order to make those things happen. You know, that's going to do it for this episode. I hope you enjoyed it.
6:40 Speaker 00 If you have a topic you want to discuss, learn more at agiledad.com. We'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.
Previous AI Doesn’t Eliminate Agile Teams — It Increases the Need for Great Ones - Mike Cohn Next Celebrating Episode 1500 - Special Edition With Bob Hartman Page updated November 6, 2026 · transcript and summary are machine-generated