Pod Insights The Agile Daily Standup - AgileDad Scrum Has Become a Nice Term to Hide Bad Management About this episode Scrum Has Become a Nice Term to Hide Bad ManagementOnce a wise man said: Fire all Scrum Masters and your non-technical managers who run your IT departments, and watch your productivity to boost up! In most cases, all you need is to hire highly-experienced Tech Leads and show trust in them. Communicate with them and share your insights, answer their questions, and provide them with what they need, including but not limited to the budget, time, ad-hoc specialist consultants, and coaches who would work for them to improve their non-technical skills. The rest, they will figure out themselves. 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:16 Speaker 00 One time, a wise man said, "Fire all Scrum Masters and your non-technical managers who run your IT departments and watch your productivity just boost up."
0:29 Speaker 00 In many cases, all you need is to hire highly experienced technical leads and show trust in them, communicate with them, and share your insights, answer their questions, and provide them with what they need, including but not limited to the budget, time, ad hoc specialist consultants and coaches who would work for them to improve their non-technical skills. The rest, they'll figure it out by themselves.
0:55 Speaker 00 That's gonna do it for this episode, or that's gonna do it for my company. That's it. That's exactly...
1:02 Speaker 00 No.
1:05 Speaker 00 I just can't believe what I'm reading sometimes. It blows my mind to see where people take this. Traditional management was designed for industries where work is predictable and repeatable and structured in a way that allows managers to oversee and control output through rigid process. However, especially in technical projects, especially software development, it's all highly unpredictable. Oftentimes, it's creative and requires continual learning and adaptation. Traditional management's command and control style slows down all the decision-making process. It puts in its own obstacles and discourages innovation, and often results in micromanagement instead of trust-based leadership.
1:49 Speaker 00 So, why Scrum?
1:52 Speaker 00 Now, I've heard many people comment about this to me. I've heard, I've seen people go up in arms about this, but I'm gonna say it again. Scrum is an agile delivery framework. I'm gonna say it again. Scrum is an agile delivery framework that was introduced to address the inefficiencies of waterfall-style project management. So where long planning phases often led to outdated requirements, or a lack of flexibility, or frustrated developers. It aimed to bring more collaboration, iterative delivery, and adaptability to changing business needs. The core idea behind all of this was to empower teams, break down silos, and reduce bureaucracy,
2:35 Speaker 00 while focusing on delivering working products frequently with good, strong customer feedback. You want to create those feedback loops. Yet, many still assume that Scrum, any Agile manifesto, holistically, are the same. But they serve two completely different purposes. The Agile manifesto is a set of guiding values. I often refer to as guardrails, and principles designed to foster flexibility, collaboration, and responsiveness when you're building a product or service. Scrum, on the other hand, is a framework that attempts to implement agile principles through structured roles, events, and artifacts that focuses on product, or process, or service delivery.
3:21 Speaker 00 Okay, while Scrum tried to align with Agile in theory, its real-world implementation often contradicts the core values of the Agile manifesto. Instead of prioritizing individuals and interactions over processes and tools, many Scrum implementations become so rigid and bureaucratic that they're focusing on enforcement of the rules rather than enabling the teams. This raises the question, if Agile promotes adaptability and self-organization and focuses on initiation, ideation, discovery, delivery, and release,
3:54 Speaker 00 and it promotes the adaptability and self-organization necessary to do it, why is Scrum becoming so prescriptive?
4:03 Speaker 00 I think the answer is we need to look back at what happened in the past to understand why we're doing this going forward. Let's look at extreme programming. So XP is an agile software development methodology that emphasizes technical excellence, continuous feedback and teamwork. It introduced practices like pair programming, TDD, test-driven design, test-driven development, continuous integration, frequent releases to ensure high-quality software was being built. While Scrum focused more on process and roles, XP focused on engineering practices that enable rapid iteration of code quality. Many teams who are trying to do Scrum unknowingly borrow from XP practices but fail to implement them completely properly. I've got news for you.
4:45 Speaker 00 None of that matters because it's still all focused on delivery. We're still stuck in the delivery realm. So
4:54 Speaker 00 let's go back to what traditional managers do. Unfortunately, in many organizations, Scrum has become nothing more than traditional project management disguised under new terminology.
5:07 Speaker 00 If you come to one of my classes, you'll hear me refer to this as when people start to do agile for the first time, they start off by doing miniature waterfalls. They're still doing all of the ideation. They're still doing all the discovery. They're still working on delivery. They're still focused on release. They still have to do all those things. It's just they're doing it for a smaller number of features inside of a two-week time box sprint.
5:32 Speaker 00 It actually makes sense. Instead of empowering teams, many Scrum masters and managers use daily scrums as a micromanagement tool. Sprint planning is a tool to push developers with tight, unreasonable deadlines without asking the why questions behind the what and clarifying the main goals to achieve. And velocity metrics are a means to pressure developers to do more and not to limit work and progress. The original goal of self-organizing teams has been lost and replaced by rigid processes that feel just like old-school management, yo, with new buzzwords in many different meetings with slim to no outcome.
6:11 Speaker 00 There we are. I said the word outcome. There's no outcome because everybody's focused on output. And the reason everybody's focused on output is because we're focused on delivery. This all makes sense when you bring it full circle, right? When you start thinking about it, it all makes sense. What is often practiced under the name of Scrum is in many cases, a flawed combination of poorly adaptive practices and outdated management habits. Instead of fostering trust and autonomy among developers and builders, many organizations have turned Scrum into a rigid system that prioritizes tracking metrics and producing output over meaningful progress and meaningful outcomes.
6:51 Speaker 00 The original intent of Agile delivery was to encourage adaptability. I shouldn't say Agile delivery, sorry. The original intent of Agile holistically, that was what I was looking for, is to encourage adaptability, collaboration, and self-organization. And that all gets lost when the process becomes more about control than empowerment. When you're enabling instead of empowering, you're enabling bad behavior. Take data scrums, for example. They were meant to help teams align and plan for their day, to get everything done effectively and efficiently. Yet, in many environments, they've become a status report meeting where managers scrutinize progress and pressure the teams to do more faster.
7:33 Speaker 00 This misunderstanding of Agile leads to an obsession with speed and speed and quantity rather than sustainable development and outcome-based delivery. Agile is not about working through arbitrary deadlines or excessive meetings. It's about creating an environment where teams can adapt, innovate, and deliver real value. I think what you need to focus on is the fact that I said about a week ago, a couple of weeks ago, I said that I would be shot down for sure because I did it one of my shorts, actually, on YouTube. I said that Agile has four phases. And let me tell you, people lost their minds because I said that ideation and initiation was just as important as discovery, was just as important as delivery, was just as important as release.
8:19 Speaker 00 And without all four of those, you don't have an Agile framework to stand on. That's going to do it. And I hope you enjoyed this episode. If you have a topic you want us to discuss, learnmoreinagledad.com, we would love to hear from you. And as always, I encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, take care. Bye now.
Previous ScrumBan... Is it real? Or just Camouflage? Next When Agile Meets Resistance Page updated November 6, 2026 · transcript and summary are machine-generated