3 ms·
And what's the significant difference between these two titles? I see two difference. First of all not all projects result in products, in which case you don't
by dagw 9y ago
And what's the significant difference between these two titles?
I see two difference. First of all not all projects result in products, in which case you don't need a product manager. Secondly I'd say a product is often made up by combining several projects (or at least products that need a separate product manager) and it's the product managers job to manage the project managers.
It's the product managers job to work out how the different projects should interact and be combined into a unified product, decide which projects to priorities for the next release and which to scrap as well as deciding which projects need to be started up tomorrow so that we can have that killer feature we want in 18 month, set release deadlines (after getting input on all the project deadlines) etc. They should also work with how to market and sell the product and to whom, as well as taking in customer feedback.
- dozzie 9y ago> [P]roduct is often made up by combining several projects [...] and it's the product managers job to manage the project managers. So if a product is split, it's like a project manager with a team composed of project managers? Do I get that right? And when a product is made of a single project, then what's the difference between product manager and project manager? What exactly can do one that is not the job of the other?
- dagw 9y agoSo if a product is split, it's like a project manager with a team composed of project managers? Do I get that right? For a big enough project, I guess. MS Office probably has product managers that manage the product managers for each component of Office. But honestly I'm just guessing at that. when a product is made of a single project, then what's the difference between product manager and project manager? In those cases you won't need/have two roles.