Pod Insights The Agile Daily Standup - AgileDad I Have NEVER Used Scrum 100% - Take It From The TOP! About this episode I Have NEVER Used Scrum 100% - Take It From The TOP! Fifteen years ago, I stumbled upon Scrum. It gave a name to many things I was already doing and introduced me to new working methods. But here’s the thing:👉 I’ve never used Scrum 100%.👉 I’ve never developed a product without using parts of Scrum. For me, Scrum — or any framework — was never the goal. The goal was always to build high-quality products that deliver value to customers while enjoying the process. Take it from the TOP T = TeamsO = OutcomesP = ProductHow 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 I recently discovered an article by Barry Overeem. It's titled "I Never Used Scrum 100%." And the second I saw the title, I'm like, "Man, I agree with that title." So I'm hoping this is going to be as good as I think it is. We're going to dive in and do a review of this article by your request. So let's get started. "After 24 years in IT-related roles, he commented, 'Yes, I'm old. Think Gandalf.'" Let's pause there. "If you're Gandalf, what does that make me? Holy cow, I've been around this thing for a long time, too. I've been around the block with you, so I get that. I've had the privilege of working both hands-on with teams and guiding them from the sidelines. Today, I balance the two worlds, building Calumny while supporting teams and organizations in their growth. 15 years ago, I stumbled upon Scrum.
1:01 Speaker 00 It gave a name to many things that I was already doing and introduced me to new working methods. But here's the thing, I've never 100% used Scrum. I've never developed a product without using parts of Scrum." I love, love, love where this is going, Barry. This is perfect. This is exactly the way that my thought works. So let's, let's keep going. "For me, Scrum or any other framework was never the goal. The goal was to always build high-quality products and services that deliver value to customers while enjoying what you're doing." Yes, yes, yes. This is what we're trying to do. We're trying to focus on not only external enjoyment and joy for the customers in the form of outcome, but we're also focused on making internal joy for the people who are building the product or service.
1:46 Speaker 00 This is the connection that many people miss. So I'm proud of you figuring that out.
1:52 Speaker 00 Conversations like these became the backbone of my approach. What should we focus on next? How can we plan this work? What's the best way for us to visualize it? Let's get some feedback from the users and see what they think. How can we improve? These are the pieces or elements that are the backbone of a real agile framework. I'm going to say that again. These are the components that are the backbone, backbone, rather, of a real agile framework. These are the questions you should be asking. These are the things that should be happening. But looking back, a common thread ran through it all. Empiricism. We constantly tried things, learned what worked and what didn't, and adapted and went in. And we went, we went on, we did it. We didn't always call it Scrum or call it agile.
2:37 Speaker 00 Sometimes it was just a bunch of like-minded people figuring out the best way to solve problems together. I think he's referred to as teamwork, maybe? Is that the word I'm looking for? Yeah. Over time, I've learned something important. Here it is. Most teams don't obsess over frameworks or labels. They don't debate whether they're doing Scrum right. What matters to them is building something valuable to their customers and doing it so smoothly, supportively and productively, that everyone just says, wow, mic drop. That's what they're trying to do. As someone who naturally gravitates towards processes and structure, this wasn't always easy for me. I had to unlearn bad habits like being the Scrum police early in my career.
3:21 Speaker 00 Oh, you know, you can't do that because that's not Scrum. I was in that same boat. We need to learn to focus on what mattered. The product, the team, and the outcomes. And I would argue a different order here. The team, the outcomes, the product. Because we need to take it from the top. Team, outcomes, product. Bam, there's your acronym for today. If you take from the top and you focus on the team first, that internal joy and happiness that they get when they are able to work with autonomy and build things and learn and explore and fail and try again and get it right. If you focus on a team first, that energy, that excitement, that level of enthusiasm. enthusiasm you're trying to get. That's what you're trying to deliver. That's what we're trying to drive home.
4:06 Speaker 00 If you go to the O and you look at the outcomes, is the customer as happy as we are? Are they overjoyed with what we built? We need to make sure we're focused on the outcome. And then third, we don't even need to worry about the product point because we know the product is there. We need to understand that the other P, the process, is just an enabler for us to get to our true goal, which should be a well-refined, defined product. It's not about following a framework perfectly. It's about finding a way of working that helps the teams both deliver value and grow. That's going to look different for every team. Some teams, it's not as outward, but with many teams, it is outward and we need to pay attention to that.
4:51 Speaker 00 But what about you? That's the question. Have you blended or adapted frameworks to fit what your teams need? Or do you try to stick to a specific approach and follow one line on a subway map, never switching trains, even though there may be a better route? I'd love to hear how your experience is compared to what I've just now talked about. So I encourage you to leave some comments, start a conversation, talk to some people and find out. And what I'm telling you right now is take it from the top, because if you do take it from the top, you're going to have incredible results. That's going to do it. Barry, thanks for the article. 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 You Don’t Need Agile... YES You Do Need Agile! Next 3 Powerful Questions I Love Asking My Team Page updated November 6, 2026 · transcript and summary are machine-generated