Pod Insights The Agile Daily Standup - AgileDad The “Agile” Team That Was Actually Just Doing Waterfall in Sprints About this episode The “Agile” Team That Was Actually Just Doing Waterfall in Sprints
Every two weeks, they ran a sprint review. The stakeholders attended. The demos were polished. The velocity charts trended in the right direction. And nothing significant ever changed based on what anyone said in that room.
That’s not agile. That’s theater with a two-week rhythm.
I’ve coached enough product teams to know that the mimicry of processes is one of the most expensive habits in software development. It looks like agility from the outside. It absorbs all the cost — the ceremonies, the tooling, the vocabulary; but delivers almost none of the benefit. Teams often know this, but feel powerless to speak up because the ceremonies themselves have become the “proof” of professionalism.
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 Every two weeks, they ran a sprint review. The stakeholders attended, the demos were polished, the velocity charts trended in the right direction, and nothing significant ever changed based on what anyone said in that room. That's not Agile. That's theater with a two-week rhythm. I've coached enough product teams to know that when... The mimicry of process is one of the most expensive habits I've seen in software development. It looks like agility from the outside. It absorbs all the costs: the ceremonies, the tooling, the vocabulary, but delivers almost none of the true benefit. Teams often know this, but feel powerless to speak up because the ceremonies themselves have become proof of professionalism.
0:58 Speaker 00 So, classic waterfall builds a plan, locks it in, then executes. The problem isn't the plan, it's the lock. Once a plan is locked, new information becomes a threat rather than an input. Agile is designed to solve this through short cycles and continuous adaptation. However, in practice, many teams run two-week sprints and hold every ceremony, yet execute against a roadmap decided by leadership months ago that will not change regardless of what the sprint reviews reveal. According to some of the leading websites, this is known as "mechanical Agile," and here's how it manifests.
1:40 Speaker 00 "The daily scrum becomes a simple status report for the managers only. Sprint planning is used only to confirm decisions made elsewhere. Retrospective surface: the same surface-level issues every month with little or no resolution. Sprint reviews: high-production demos followed by polite, meaningless applause. It is tempting to blink the framework when these things happen, but the process is usually fine. The problem is that adaptation is politically dangerous. McKinsey's research indicates that the most consistent predictor of team adaptability is psychological safety. If the team members feel they cannot surface bad news without a personal cost to pay, the ceremonies become defensive.
2:23 Speaker 00 You omit signals that would challenge the roadmap to protect your standing."
2:29 Speaker 00 Three years ago, I worked with a team that was textbook agile, but completely stud. The PM knew a core assumption in the roadmap was wrong, but had been shut down weeks prior. I took a simple uncomfortable step. I canceled sprint planning. In its place, we held a session with one agenda item. What do we actually know and what are we pretending we know? By the end, the team had identified three major risks that the polished sprint reviews had ignored. The Agile Alliance notes that this shift requires leaders to model vulnerability. You can't just give permission to speak.
3:08 Speaker 00 You have to prove that challenging the status quo carries no real cost. It's all a benefit. If your team looks like they're agile, but they're not adapting, stop looking at the velocity and start looking at the retrospective. Change your questions from your traditional questions. What did we know two weeks ago that we chose not to act on? What did we see during a sprint that we're afraid to talk about? Are ceremonies generating genuine reflection or just generating meaningless artifacts? Are we focused on outcome or output? I think ultimately, that's where we need to be. If we can shift gears and focus on outcome, happy customers, with as little output as possible, and we can stay focused on the things that really matter,
3:53 Speaker 00 I could promise you right now, that's going to make everything about our Agile implementation better and easier. And it's going to give an opportunity for those people who who just are looking for the answer to, to really put their finger down for a second and say, "Wait a minute, I actually have something here," and be able to move forward. 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. 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 Why Estimating and Planning Still Matter - Mike Cohn Next Autistic Bowler Achieves Dream With His First Perfect 300 Game And Joins the PBA as a Pro Page updated November 6, 2026 · transcript and summary are machine-generated