Pod Insights The Agile Daily Standup - AgileDad Product Owners vs. Product Managers vs. Project Managers About this episode Product Owners vs. Product Managers vs. Project ManagersWhile you are knee-deep looking for your next role, I’ve seen endless variations of “product” roles. Specifically, the terms Product Owner (PO), Product Manager (PM), and Project Manager (PjM) seem to be used interchangeably, or even used to describe the same person. Yet, some teams have all three within each individual squad. So, what’s the difference between these three roles? And why do we need all three in the first place? 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 Let the games begin. Product owner versus product manager versus project manager. Are they all the same person? Do you really need all three? What do you need to do? This seems to be a question that gets revisited a lot while people are talking to me. And I know a lot of people who are currently in the job market looking for their next opportunity. So I thought this would be a great way to help them understand is there a difference? What is the difference and where do they see themselves? I've seen endless variations of product role. Product lead, product manager, product governor, product overlord, product ruler, product vice president over product, director of product. I've seen so many different product terms.
0:59 Speaker 00 The same is true for project. And many people try to use these terms completely interchangeably. Or even worse, use it to describe one person. Yet some teams I've seen have all three within each individual squad or group that they have broken out. So what's the difference between these roles? Do we need all three? How does it work? So let's break it down for you. I'm going to try to simplify this the best I can for you. So product owner, let's start there. This role specifically on a scrum team. So they focus on outcome, maximizing value, managing the backlog. They're accountable for identifying opportunities for value and making sure that team has everything that they need to deliver on that value.
1:44 Speaker 00 This means that they're organizing work and making sure the work's easy to consume. It's a pretty simple set of accountabilities, but it's something that means that they also have to understand all of the business acumen, the strategy behind why we're trying to build it. They need to understand the customers wants, needs, whims, and desires. And they also need to understand strategically for the team, how is this going to help them going forward if there's any technology value to what's being built, which makes total sense. Then comes in the product manager. The product manager is often described as the strategic thinker, the one who focuses on the bigger picture. A lot of times in the past, they were release managers or even portfolio managers. They're responsible for defining a product's vision, strategy and roadmap,
2:29 Speaker 00 as well as managing stakeholder expectations and communications. So in this world, in contrast to the PO, the PM is more focused on delivering business value rather than just meeting the consumer's needs. They're responsible for prioritizing bigger features, allocating people, making sure money is there to do the job, ensuring the product meets its goals. Although not everyone agrees that it's a distinction,
2:54 Speaker 00 many people say the product owner should be doing those things. And like I just said a few moments ago, most good product owners do those, but it's usually for a dedicated small number of products or projects. So that's the easiest way to figure that out. And then there's the project manager. So the project manager is responsible for coordinating time, money and people to deliver a specific project or feature. They're often involved in planning and executing and monitoring progress toward defined objectives. Anytime I hear the word project manager, I think Gantt chart. That's the easiest way for me to describe it. So in many cases, the project manager role is seen as an extension of the product manager role with the project manager focusing on strategy and vision, while the project manager focuses on execution and delivery.
3:39 Speaker 00 This is the way that it was set up originally, if you ever went and got your PMP. So if you went and got your project management professional, this is the way it was explained. This is the way it was doled out. This is the way it fell. So with that being said, this should not be confused with the product owner, who also focuses on execution and delivery only in a context of what the work, not in a context of the people to deliver the work. So they're not focused on the people. They're focused on organizing the work in such a way so it's easily consumed by the people, which makes a lot of sense. So the differences are clear, but you have a PM to manage the strategy stakeholders and business impact, a PO to manage business impact stakeholders and execution, and a project manager to manage
4:21 Speaker 00 priorities and timeline. Guess what? That's not easy. There's a ton of overlap there. It's like trying to figure out, this can get controversial, and I've heard people argue this. I've heard people get into debates about this. In some teams, it can really feel like all those roles have unique functions and are required to deliver high quality. Even in large organizations, in my experience, they're usually doing more, they're usually using more people as a solution to try to solve a larger problem. I remember working once with a project manager on a scrum team, and she doubled as a scrum master. She managed a timeline, argued with leadership on estimates,
5:05 Speaker 00 got things going when they fell behind. It took a ton of tough conversations for me. I remember I liked working with her, but at the same time, she wasn't individually creating or adding value. She was instead acting as the Band-Aid to the company's much larger problems, lack of clarity, alignment, vision. And this, you see, when you have all those overlapping roles, things tend to slow down. Suddenly, you need to talk to your PO before you want to adjust the features requirements. Then you need to get buy-in from the project manager to confirm it can be done on time. And at worst, each of these roles start making decisions independently and put out an unaligned conflicting direction, which is a nightmare. Remember, work will expand to
5:48 Speaker 00 fill, to artificially fill our pre-allocated time, right? We all know that. That's Parkinson's Law. Don't create people hours without a reason for them. Despite my disdain for understanding these roles, the understanding of these roles, I should say, I don't think that you should completely wipe them off the face of the earth. Project managers are still great. A project manager can help you survive the chaos. I'm sure plenty of other successful product owners and project managers out there doing awesome stuff at their teams, too.
6:23 Speaker 00 But if you're a bit more experienced, but still don't get why we need three people to do the same things, try to break out where your skills fall in each of those roles and identify your weak spots. Remember, these are titles that just overlap. And sometimes you're looking at the wrong thing. You're, you're not looking at how you create value. You're looking at how you Band-Aid a bigger picture problem. So if you're a product manager and you feel like you'd make a terrible project manager, follow up some things to make you a stronger project manager. That's going to help you going forward in your role as a product manager. What I can tell you is the big change that I've seen, the big shift in focus is that more organizations are leaning towards agile project managers
7:07 Speaker 00 and product owners to get that separate distinction. So that the, I'm sorry, product managers. So the product manager gets the holistic picture of how to make things work. And they're working with BOSS, BOSS and TOS, business analysts, functional analysts and technical analysts to get input so that they can manage the big picture of organizing the work. And then the change management side where a project manager type role comes in and does the duties of a scrum master, cheerleading for the team, but does it in the sense of a project management set of responsibilities that they're governing change as well. That's going to do it for this episode. I hope that that was helpful. And I hope it helps you get some distinction. If you have additional questions, concerns, or if you just want to talk about a topic that's important to you, reach out to us, 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.
7:52 Speaker 00 Until next time, do take care. Bye now.
Previous The 5-Second Conversation Hack Next Why Your Scrum Teams Are Failing - The Hard Truth Page updated November 7, 2026 · transcript and summary are machine-generated