Pod Insights The Agile Daily Standup - AgileDad Are Agile Frameworks Really Agile? - A Blind Article Review About this episode Are Agile Frameworks Really Agile? - A Blind Article Review
Have you ever read an article before and just scratched your head and wondered to yourself... WHY?
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 One of my students sent me an article titled, "Are Agile Frameworks Really Agile?" Now, I'm doing a blind read. What that means is I've never looked at the article. It sounds like an interesting topic, so I'm gonna go through and read the article with you and fill in some commentary in between, and then give you a summary of my thoughts at the end. "So after seeing the moderate success of a previous article reviewing Solid Principles, interesting, I've decided to continue sharing my ideas. This time, this article is based on a decade of observing and participating in processes built on popular agile frameworks, Scrum, Safe, and Kanban." Okay. It's divided into two parts. The first part focuses on existing problems, and the second is on suggested solutions. Love that. For me, I always say, "It's a wine and cheese party."
0:59 Speaker 00 You can bring the wine, the problems, W-H-I-N-E, as long as you bring the cheese, the potential solutions, right? You need to have both. So, the Agile story started a long time ago, around 2001, according to Wikipedia. It's actually earlier than that. And the Agile Manifesto promoted four values: individuals in interactions over processes, tools, working software, software for comprehensive documentation, customer collaboration over contract negotiation, and responding to change following a plan. If you haven't already, I encourage you to go download our copy of the Agile Manifesto 2026, which shifted a little bit. Instead of saying working software, it's as working products and services, because we're trying to make the Agile Manifesto more inclusive. And I think that's a good idea. That way, everyone can use it.
1:45 Speaker 00 These principles apply to every product and service that you build, not just software. Let's continue. It says, "My experience fully supports all those principles," as they, well, those that are values, but it's okay. "as they indeed lead to high-quality and stable projects, happy customers, and happy developers." "While not explicitly included in those principles, Agile was presented as a lightweight alternative to the traditional waterfall methodology, allowing quick iterations and faster market response. It was particularly useful for the software development industry due to its constantly-changing nature, so software companies around the world started adopting it." Okay, that's mostly true.
2:24 Speaker 00 I love that it goes through and tries to describe all these different pieces. There's just so much more depth and context to this that I don't want to get into right now because it will make this episode last 30 to 40 minutes. But this is something that if we need to have the discussion, I'd love to dedicate a couple of days to this discussion. And then goes on to the agile reality. Since it's hard to adopt just some values, people wanted to understand what they should do and how to do it. Thus, a number of lightweight frameworks quickly gained traction with Scrum taking the lead. Funny enough, the framework's popularity mainly emerged because of the processes and tools they provide, clearly violating the first point of the Agile Manifesto. Okay, let's stop.
3:07 Speaker 00 Okay, this is my hard, yeah, this is my hard no, and I apologize. This is probably why the person sent me the article. I just want to read this one more time and then give you my perspective. It says, funny enough, the framework's popularity mainly emerged because of processes and tools. That is not true. The framework's popularity came from short cycles where you can inspect and adapt and pivot and make adjustments. It came from the empirical process, transparency, inspect and adapt. That is what made it popular. That is what made it easy to grasp. I could see something in two weeks instead of in 12 weeks or 16 weeks. It gave me the ability to constantly adjust, pivot, reevaluate where I was. That is what made it the popular framework that it was.
3:52 Speaker 00 It had nothing to do with Jira or with, you know, with Azure DevOps. It had nothing to do with the daily Scrum, a release planning meeting, and none of those things mattered. In fact, Scrum was very light on meetings and very light on processes to help you manage and govern so that you could have things that would guide you in the right direction. And I would vehemently disagree that it was in violation of the first, the first value of the Agile Manifesto. I believe that Scrum holistically talks about individuals and interactions. Now, if you want to have a separate discussion about Scrum being an agile delivery framework, that discussion, I'll agree with you and we can have that discussion. But I don't feel like Scrum violated anything. Let's continue.
4:35 Speaker 00 As time passed, this has only become worse. Today, in most average-sized companies, I've seen the Agile process has become the backbone of operations and development teams that have to obey its rules. This is a very sad statement, in my opinion. This is so sad. The Agile process has become the backbone of operations and development teams. First of all, Agile process, and it's in quotes, but Agile process scares me. Agile is a way of obtaining information and processing information. It is a way of processing and making clear, clean decisions based on information that you have. It is a way to research and discover things that you don't already know.
5:17 Speaker 00 It is a way to step you through ideation, discovery, delivery, and release. It walks you through all four phases. It is not meant to be just this rigid delivery process that you're making it out to be. And obey its rules. Regular, daily, weekly, and monthly meetings with strict procedures must be conducted. Sprint's properly planned, tasks committed and assigned, goals fixed, and numbers put in the charts. I didn't make that up. I'm reading it. That might be the most scary manifestation of what someone believes agile is. If this person honestly believes that that's agile, I would love to invite them to come to one of my trainings. Even if I have to put it on my dime, even if you have to come for free, I would love to have the author of this article in one of my trainings,
6:02 Speaker 00 just so I can show you how not strict it is and how, what things are required and what things aren't required. Because I think that what you're doing is you're making it out to be something that's completely dogmatic and rigid when it's not. To support, so I'm going to continue now. To support the rise of frameworks, the quality and complexity of tools have greatly improved. Jira and similar instruments now provide all the required bells and whistles for managers to enforce framework rules and policies.
6:30 Speaker 00 Here we go again. Jira is not meant to be used that way. If you're using it that way, there's a bigger problem. And I think I see just a huge underlying red flag here. And it's that this individual clearly has had some really bad agile experiences. And I'm not saying that they're not going to come around and say, hey, you know, that's why we do things differently. But you can't let bad agile drive your thoughts about how it should be implemented. If you have the right coach or the right trainer guiding you through, these things should be simple and easy to do. And it shouldn't be this arduous thing that you're making it out to be. As frameworks mature, the rules and processes become more elaborate, only and safe.
7:13 Speaker 00 Which is an emerging, oh, I guess, discipline agile delivery too. Which led to demand, which led people, the demand of people whose job was to enforce rituals, ensure proper execution, DevOps, and they go on and talk about DevOps principles. Okay, I'm just gonna stop. There are probably, in a history of over 1,500 podcast episodes, this might only be the second episode that I stopped because my face is turning bright, right? Because I'm so upset. I owe each of you an apology. I should have read this article first. What I can tell you is this article was designed to be rage bait, in my opinion. They go on to talk about the first agile has become the first, the first agile principle
7:58 Speaker 00 has become the first to fall, da, da, da, da. And the last agile principle has become the second to fall. And here's a list of agile smells that are making things bad and things you should be looking for and why you shouldn't. These types of articles really disappoint me because there are a lot of people who put their credence, their credibility and their credence into these articles, thinking that these experts are here to help them, you know, drive things forward. All I'll say is sad day. For me, understanding the fundamentals is so important. And that's why we teach an agile fundamentals class. We want everyone to know that no matter where you are on a path or on a journey, that we can get you there. And that there are certain things that you can do, sure, you know, is it completely dogmatic?
8:42 Speaker 00 Absolutely not. If it is, you're doing it wrong. Does it require you to have some meetings? Yeah, it does. But are those meetings, you know, run a certain way with specific rules and strict guidelines? And I don't know. No, they're not. I'm going to say it again, no. In fact, if I go to Agile or eBay or Amazon or SpaceX, yes, I've coached at all of them. Those meetings have a different complexion and look different in every single one of those organizations. Do they have some similarities? Of course. Do they have lots of differences? Absolutely. I think that it's important for people to understand that organizations, small or large, have different cultures, different team sizes, different types of products and services that they're building.
9:25 Speaker 00 A product or service in a nonprofit organization would look completely different than a project at a department of war. A project at Disney, ABC, ESPN would look completely different than a project for World Wrestling Entertainment, right? And I'm not saying one's good, one's bad. I'm just saying the complexion of the project, the way it's structured, the things that we study are all going to be different. And I think it's just so important for us to really get our heads on straight and to not spread propaganda or falsehoods, especially this week while we're honoring the Agile Manifesto, to break it down and say that it's ugly and that it doesn't work and that it's fallen. I feel like it's shameful on many levels. First, that you chose this week to do it, and second,
10:10 Speaker 00 that it's just not true. It's one of those things where do I live and die by the manifesto? Absolutely not. Do I believe it could have been written a little differently? Absolutely. Do I also acknowledge it was written 25 years ago? Yes. Do I think it was revolutionary 25 years ago? Yes. And I'm proud to say it stood the test of time. But I think that sometimes we need to take a step back and evaluate where we are, what we're doing, and how we're making things better for ourselves, our teams, and our organizations. And when you do that, that's going to put you in a much better place. So instead of finishing the article, I'm going to say that will do it for today. And if you have any questions or comments or a topic you want us to discuss, feel free to reach out to me, learn more at agiledad.com. I'd love to hear from you.
10:52 Speaker 00 And I do want to specifically thank my subscriber who recommended this article. Because even though I didn't finish, I completely understand why you recommended this article because you just had to hear me break it down for you, and I appreciate that. Until next time, I encourage you to stay healthy, stay well, and stay agile, my friends. Do take care. We'll see you soon.
Previous How Much Are Meetings Hurting You? - Mike Cohn Next The February Blanket - A Story of Mae Page updated November 6, 2026 · transcript and summary are machine-generated