Pod Insights The Agile Daily Standup - AgileDad Are You Chasing ScrummerFalls? About this episode Are You Chasing ScrummerFalls? You can be pure Agile, you can be pure Waterfall, but have you ever been Waterfalling Agile? I have seen Waterfalling Agile, and it’s not a good scene. Essentially, when you are doing the worst of both worlds, thinking you are on top by taking the best of both, but you are wrong. 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:15 Speaker 00 So if I understand this correctly, you can be pure agile. You can be pure waterfall. But can you be pure scrummer fall? That's the question, right? Or agile fall, or water scrum, or water agile. I've heard it called so many different things. Water falling agile. Overall, when you think about it, many people just on the surface say, eek, it's not a good scene. When you're trying to do the best of both worlds, sometimes you end up doing the worst of both worlds. Thinking you're on top of the best, but in this case, you could be wrong. Now, I'm not saying that you can't mesh the two together. So let me explain.
0:56 Speaker 00 There are certain tenants from traditional project management that I absolutely love. For example, limiting team size for lines of communication. There's a whole formula for that in a PMP. Uh, the concept of earned value management. There's such a thing as agile earned value management. I absolutely adore earned value management. The concept of limiting work in progress to the scope that's within a set work breakdown structure. The concept of a work breakdown structure, just like a product backlog. The point I'm trying to make is, I don't think that waterfall is as wrong as we're making it out to be. So for the first example, I want to talk about requirements. So requirements in agile can be fluid, but they should always be well thought out.
1:39 Speaker 00 Uh, for example, a developer can start with 80% of requirements as long as those 80% are the key manageable anchor requirements that aren't going to shift another 17 times over the course of one single sprint, right? If your 80% requirements consist of the small stuff, the priority three requirements that have that have the tendency to get pushed out. You might find yourself having completed a whole lot of stuff, but it not being the right stuff, not being the stuff that you need. And the inverse is true as well. Having your team wait and wait and wait for requirements to even begin and not starting on anything. Getting the notion of what they think they're building is just as bad as if they were working on the wrong 20% to begin with.
2:21 Speaker 00 So you gotta find a way to, whether it's software delivery or non software delivery, you gotta find a way to get just enough work for the team to get started. In other words, you don't need a proper technical user requirements document to get everything done. Or a business user requirements document, right? What you need instead is just enough for the team to feel confident that they can get going without things changing 100 times on them. Sometimes when I'm working with brand new teams, I'm constantly be surprised by how how often the people who are doing testing don't know how long it takes to run, for example, our aggression tests or to physically go through and test a specific feature or on a suite.
3:04 Speaker 00 Or they'll get involved with testing when everything else is completely done and finished. And they can look at the whole thing holistically then. I think that if we address this testing culture, if you will, and start thinking about how the product's built. I want the people in the room, the people listening to approach how these things are going to impact the system as it currently stands. And I want these people to hear what's going to change in the requirements in case somebody forgets to write it down. Most importantly, I want their input on how we can improve a feature. I mean, after all, the tester is the one that's going to be clicking the buttons.
3:47 Speaker 00 It's about seeing the product through a different set of eyes than we could when you're down in the weeds. So for me. Whether it's peer reviewed, peer reviewed, mob programmed, or whether you have a separate testing environment altogether, we need to just come up with the fact that testers are special. They rock. We need them. And they don't necessarily get a mulligan or a buy when it comes to doing estimates or providing input. In fact, I would argue that sometimes their input is even more important. It needs to be part of the feedback loop. And feedback loops in general are the key that makes agile work. It is what greases to skids. They're the cornerstone of what makes agile work in small teams or in large organizations.
4:32 Speaker 00 You might think everything's going fine, but once you hear from the team, it might change what you're doing and why you're doing it, or you might hear from a stakeholder and that changes everything. In waterfall, this really doesn't happen too much because no one wants to deal with the change control process to make it happen. So a polarizing shift that I'm seeing in the agile community today is that coaches and organizations are starting to lean in more in change management. And this makes sense. Because if you're waterfalling agile, you go through the motions, confident that the process is perfect and that everything's going to correct itself. We have the retros, we write down feedback, we don't change anything. And after a few sprints, we wonder why we're having this extra meeting that's yielding little or no value.
5:15 Speaker 00 And how do we move on and give this back to the team, right? I mean, we can give the team back their hour and it can do something else with it. But I think that if we don't understand the value of what we're trying to do and if we're not pushed in a direction that's going to help us get where we need to be, we're going to struggle. And that's going to cause a breakdown of everything that's going on. Because what most people don't realize is that, for example, Scrum is a delivery framework. And many people come in and say agile is for software development only. These two misconceptions, uh, you know, Scrum is a delivery framework, period. But people don't realize that. And when people think that Agile solves everything, I guess the better way to put it,
5:59 Speaker 00 or it's for software development only, that's, that's a myth, right? When only one portion of what you're doing is Agile and everything else isn't, that doesn't mean you're Agile.
6:09 Speaker 00 I mean, it, it, it really makes sense to me, uh, when you can say, are we doing all this stuff? Sure, we are. Are we focused on the same product? Yeah. Are we all focused on the same goal? Well, I don't know, right? Because sometimes when you're trying to get one team or more teams to move together towards a common North Star goal, you'll see the results you should see, but are you inspecting and adapting enough to make that result a tangible result that the end consumer really wants, right? So are you doing competing systems at play because you're not sure that Agile's going to work? Or you're trying to adhere to a set of rules that are antiquated and baked in? Or are you really understanding what the end goal is of the consumer?
6:52 Speaker 00 Are you focused on the outcome instead of the output and driving towards that outcome? That's the question. So if you're worried about falling into the, the Scrum or Fall trap, go back to what the original goal was and ask yourself, help me understand, what are we trying to do here? And, and, and look at grow, right? What is our goal? What is our reality? What options or opportunities do we have to get there? Or what are the obstacles that are standing in our way? And then what will we do today to make a difference? And if you can get there, you can deliver faster, you can deliver better products, you can deliver things that consumers actually enjoy using, because that's, that's why we're all here anyway. That, that's the purpose of us doing Agile to begin with. So 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.
7:36 Speaker 00 As always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye.
Previous Why Is Your Team Skipping Daily Standups? Next What If Scrum Masters Only Want To Act On A Team Level? Page updated November 6, 2026 · transcript and summary are machine-generated