Somebody has to drive the product forward, merging marketing sales and technical issues so as to maximize gain from people’s effort. Things like importance of

Somebody has to drive the product forward, merging marketing sales and technical issues so as to maximize gain from people’s effort. Things like importance of fixing bugs, critical features, etc. Unless you want 3-4 people arguing all the time, somebody has to sit in the middle of the interactions. Call them whatever you wish. To me, a project manager owns the codebase and the developers, while a product manager owns the software product. There are different drivers for these people, as sometimes the nasty bug has to be fixed rather than maxing bug fixing. The project manager isn’t interested in what s&m might be saying but knows all about the pain and effort levels for fixes and additions. S&m thinks the software people don’t do anything and lie about their workload.