Pod Insights The Agile Daily Standup - AgileDad When Agile Meets Resistance About this episode When Agile Meets ResistanceYou’ve probably heard Agile being described as a novel way of navigating productivity at work, that it could boost collaboration, and uplift your teams into a well-oiled machine. That’s what they say, but how true is this? Especially in the IT culture? In reality, when Agile is incorporated into traditional IT culture, it seems like a wreck than a harmonious integration. The resistance is strong with this one with developers, project managers, and IT leaders staring at each other with palpable tension. 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 You've probably heard about Agile being described as a novel way of navigating productivity at work. That it could boost collaboration, uplift your teams into a well-oiled machine. That's what they say, but how true is it? Especially if you're looking at a technology culture. In reality, when Agile is incorporated into traditional technology culture, it seems like a wreck more than a harmonious integration. The resistance is strong with this one. Developers, project managers, and even technical leaders staring at each other in palpable tension. Why does this happen? And how does one navigate this resistance in order to make the Agile adoption better?
1:01 Speaker 00 Technical environments are usually centered around hierarchies that are rigid. This is paired with lengthy development cycles. It is where the team works in silos. They use formal and slow communication and are forced on, uh, focused, rather not forced, they're focused on massive releases when delivering with little flexibility about what they can and can't or should or shouldn't build. It's basically the opposite of Agile as it asks teams for flexibility change in short delivery cycles, hence the resistance. When Agile is introduced, the response is to roll their eyes because many might think that Agile is just another useless trend that promises to fix their problems, but ends up adding to it instead. There are also other reasons for this. Let's review a few. One.
1:46 Speaker 00 We fear that we don't understand.
1:51 Speaker 00 We fear everything, what we don't understand. It's nice being in your comfort zone when teams are taken out if they feel like it's disruption in process. They've been using waterfall or other methods for years and ease of doing something you already know is comfortable. And since learning new things takes time, it might seem that Agile doesn't really bring any value aside from disrupting the flow of the way things are going. Or how about an understanding of who does what? Traditional roles are clear. The developer's code, tester's test, project managers manage. It's clear, simple, easy. But in Agile, there are unknown roles that are unfamiliar, such as the Scrum Master, or product owner, or product manager.
2:33 Speaker 00 And it blurs the clarity of who does what. And then, of course, there's a fear of losing control. Leaders to this day will still deny this, but they may feel that Agile makes them lose control of what they were once leading. Since it all becomes about self-management, autonomy, and collaboration. This makes people feel skeptical. It does, especially those that have worked with rigid pipelines and guidelines and deadlines for years. So how do you overcome, how do we overcome the resistance, right?
3:07 Speaker 00 Vive la résistance!
3:11 Speaker 00 Since we've not seen a root of the problem, it becomes an effort to find the root of the problem. Then, once you find a root of the problem, it is time to fix it now. You can start by leading my example. I'm not saying Agile's solution to everything, because it's not. So it's important to implement Agile slow enough, but surely in a way that fits your team and your corporate structure. Use small wins in manageable areas where you can show quick results to improve the trust people have in Agile. And when people see results, they're more likely to get used to it and approve of it and say, hey, this is something I can get on board with. How about number two? Leave with clarity, give clarity.
3:52 Speaker 00 Since role confusion is one of the biggest problems, by the way, role confusion is number three. I said three, three, there we go, that's better. Number three on the list of the top three things that organizations struggle with. Since it's still one of the biggest problems with adapting Agile in a culture, make sure to explain the purpose of each role with intent. And I'm going to go here. Instead of focusing on roles, focus on accountabilities. Make sure you focus clearly. You need to show what empowerment, what empowerment means to each role, what it brings, and get everyone on the same page. Everyone's working together. And to that end, and at the end of every day, each role has a similar goal.
4:33 Speaker 00 That delivers value better, more quickly, and is focused on outcome-based results, not output. How about number three? Ease the fears. Show everyone involved that agile doesn't mean relinquishing control, but fostering accountability and ownership. This eases the fear that agile is only there to wreak havoc without any proper oversight. Let them know what Scrum Masters do, and what they are, and how they are there to facilitate and guide teams, keeping them in check and preventing chaos. This layer of transparency soothes leaders, and it shows control is still exercised just in a way different than what they're traditionally used to. How about this one? Acknowledge the struggles.
5:17 Speaker 00 Adopting agile is never going to be a clear road without any bumps on it, and that's fine. Mishaps and issues happen all the time. Just acknowledge it. Continual learning is the most important thing when undergoing change. Remember to acknowledge struggles, but also celebrate wins, big or small. Don't let things just get washed away. And then, of course, this is my big one. Balancing tradition and change. I've been to so many organizations where they say, "We want to change, but we've been doing everything the same for the last so many years." And I'm like, "Oh, my goodness. You're killing me, right? You're killing me, Smalls." The resistance between agile and traditional culture doesn't have to be death.
6:01 Speaker 00 It's a chance to show that even opposite perspectives can work when there's proper communication and clarity. There will always be resistance to new ways of doing things, but by addressing the causes of the resistance, you're showing how to build a bridge and bridge a gap and move forward as opposed to how to be apprehensive, slow, and hateful when it comes to solving these problems. Agile isn't chucking traditions in the trash. It's here to improve upon things that we've already done. It's about continual improvement. This kind of resistance is something that you can you can expect to see, but it shouldn't be too difficult to overcome. You need to figure out how to navigate resistance in your teams when it comes time to adopting Agile.
6:47 Speaker 00 And you need to learn how to follow a pattern. And if you can follow the pattern and you can understand the whole concept of ideation, discovery, then delivery and release, you're going to be way better off than you were yesterday. And it's going to help you with your Agile implementation. That's going to do it for this episode. I hope you enjoyed it. If you have a topic you want us to discuss to 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 Scrum Has Become a Nice Term to Hide Bad Management Next The Only Three Things You Must Do To Improve Agility - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated