I find it fascinating to follow the process of how new software is designed, built and rolled out. There are so many moving pieces involved and so many decisions to make. Too many people participating and you get idea overload and a bad product. Too few people involved and your schedule tanks and your solution doesn’t meet the market need. Classic Goldilocks resourcing problem.
Then you have the roles of different people on the project. Developer, DBA, Architect, Designer, Project Manager, Product Manager. Each with specific things that they do. Sometimes you have one person playing multiple roles. Other times you have multiple people in the same role. Fascinating.
But the one that’s always held my attention the longest is the Project vs. Product Manager. As far as I’ve gotten:
Project Manager = the person who makes sure the project is completed on schedule, on budget and meets the design criteria.
Product Manager = the person who makes sure the project is actually going to make money once it is done.
Oversimplified? Sure. But they are distinct roles that are both vital. A Project Manager is tasked with completing the project – regardless of need. A Product Manager makes sure it fits a need – regardless of schedule and budget. These roles classically clash and force each other to compromise.
A Product Manager by nature cannot fit nicely into a Project Manager role. The personality types are too different.
Which are you?
Hi David,
We explained the difference between project management and product management in a post back in 2007, you can find the post here: http://www.pmhut.com/product-management-vs-project-management
In any case, I think that every project manager should be also a product manager, or at least have it product management in his heart. If the project manager only cares about making it on time and on budget regardless of whether the end product will be used or not, then there is something seriously wrong about what he’s doing…