Pod Insights The Agile Daily Standup - AgileDad Why are product managers still using agile? About this episode Why are product managers still using agile? Ah, Agile — the buzzword that just won’t quit. It’s been the darling of software development for years, promising flexibility, speed, and a better way to build products. But here’s a cheeky thought…why are product managers still using Agile? Don’t get me wrong, agility is essential. But sometimes, it feels like we’re trying to fit a square peg into a round hole, especially when it comes to product management. We continue to attempt to fit a delivery focused methodology into outcome-based work… and we seem to never learn our lesson. The limitations for Agile are prevalent for discovery, an overlooked part of product management for many years. How does agile help to support a workstream that is primarily focused on research? Can it? 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 At some point, we gotta get tired of hearing that agile is a buzzword, but I still get the question, why are product managers still using agile? And it's almost as if they're saying that agile is a bad thing, right? But what I can tell you is, for years, for many years, people have been saying that agile has promised flexibility, speed, and a better way to build products and services. But here's a thought. Why are product managers still determined to use it? I mean, don't get me wrong. Agility is essential, or else I wouldn't be agile dad. But sometimes it feels like we're trying to fit a square peg into a round hole, especially when it comes to product management.
0:54 Speaker 00 I think that some people force agility to try to say, yes, we're doing the agile, when in actuality, they need to focus their attention less on agile delivery and more on agile ideation and discovery. We'll get to that in a minute. But we continue to attempt to fit a very delivery-focused methodology into outcome-based work, which is what I was just now describing, right? And I think that too many people look at agile or Scrum and say, hey, that it is definitely squared away for delivery. And I guess the question becomes, do we assess the real difference between agile and agility? Because I think they are two totally different things.
1:36 Speaker 00 So agile is not the same as agility. So if you look at agile, agile methods, agile framework, right? This is focusing on small iterations. Instead of waiting for something to reach its done state, you release things little by little incrementally and start gathering feedback as soon as you see how people respond. It's about breakdown of work into manageable chunks and iterating based on the feedback you receive. Agility, on the other hand, is how quickly you get those things out the door. It's about speed and responsiveness, the ability to adapt swiftly to changes, whether it are from customer feedback, market shifts, new strategic insights, et cetera. So for me, Agile is about output and how the agile team can be, how agile a team can be within
2:21 Speaker 00 an environment, whereas product management is the greater focus on outcomes. And this might be the big push that we're seeing now for change management to be integrated in with product ownership. And I saw a formula the other day that said, product ownership plus change management equals agile product management. And I don't necessarily disagree with that. I feel like agile product management is something that people have not addressed. A lot of people are still using it synonymously agile product ownership and agile product management, but the two aren't the same. So many years ago, seventeen guys got together and created the Agile Manifesto in 2001, and their whole goal was to focus on improving efficiency and adaptability of delivering
3:05 Speaker 00 processes. For those of you who haven't read it yet, it emphasizes principles like quick customer collaboration, responding to change, delivering working products and services quickly and frequently. It didn't explicitly incorporate product management into the framework. In fact, it was originally called the Agile Manifesto for software development, so it was very software centric and focused. It didn't talk about ideation and discovery. Its main focus was on agile software delivery. So if that's true, most people then say that an agile environment is where a product owner role is considered to subset the product management role. The product owner is responsible for representing stakeholders and defining the product backlog,
3:47 Speaker 00 and a prioritized list of features and requirements the development team will work on is distributed by the product owner. Because Agile didn't specifically account for product management roles, product managers often struggle to align discovery and ideation and strategic activities with the development team's agile processes. And this is why I come up with the call for a BAFA TA. So BAFA TA is business analyst, functional analyst, and technical analyst, but I want to draw emphasis that it does not mean that these titles or these individuals have to have these specific titles. The business analyst takes on the role of consumer representation, a functional analyst, strategic representation, and technical analyst, architecture, infrastructure, and
4:29 Speaker 00 development representation, so that they can work hand in hand with the product owner so that they can coexist and create an agile ecosystem. And when you hear people talking about the agile ecosystem, One of the things they never remember is missing is everyone always focuses on agile delivery, but nobody really takes the time to talk about agile initiation, agile ideation, agile discovery, and those are the pieces that are often missing. So it's definitely possible to integrate these things and to create an agile ecosystem or agile framework outside of delivery. But you need to make sure that when you're doing this, that you're continuing your focus on new opportunities while you move forward with current work.
5:11 Speaker 00 So there needs to be an arm of innovation or ideation. There needs to be some strategic discovery. We need to make sure we understand our personas implicitly and we need to make sure that we're focused on, you know, as close as we can to continual integration and delivery so that we can get feedback quickly and iterate on that feedback, whether it's internal feedback or external feedback. And I think that sometimes we just totally forget about the initiate and discover phases and we jump straight into delivery. And when people ask, why do we do that? We always use agile as our crutch and say, because, well, because we're agile. And that's not what agile says you should do. I think the big picture here is that agile is more of a hyper focus on all four phases of delivery,
5:54 Speaker 00 which includes initiator ideation, discovery, delivery, and then of course, release, because you still need to align how you're going to get things to the customer. And I think that when you say for the sake of agile, well, teams spend too much time in meetings, so we're going to get rid of initiate and discover, you're literally killing yourself by just hyper focusing on delivery. And that's what's causing a great paramount and the great confusion between agile product ownership, change management, and agile product management. I think there is a merge here and I really do love the way agile focuses on a traditional way, in my opinion, to
6:32 Speaker 00 Do all of the four steps, but the problem is people like to zoom in only on the delivery piece because they want, they do it for the sake of eliminating meetings or for, or for getting people to talk more often. So we don't have all this pre-work per se. And I think that if you can focus on things like swarming to the work in progress, allowing the product owner to organize the work in such a way that it's easily consumable using invest methods, embracing things like test-driven design and hypothesis-driven development, utilizing people to do experiments and to do brief cases to study and figure out where they are. Those are the tools that are going to help you really, really be effective using
7:14 Speaker 00 Agile. So I guess what I'm trying to say is Agile in itself is not dead. Agile product ownership is not dead, but Agile product management is real. And I think that when you start thinking outside of the delivery box, that's when you're going to discover the best thing you can do for your Agile implementation. That's going to do it. I hope you enjoyed this episode. If you have a topic you want 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.
Previous The Mindset of Highly Attractive People Next How Value Stream Management Transforms Project Managers and Agile Experts Page updated November 7, 2026 · transcript and summary are machine-generated