402 karma · joined March 23, 2014
Previously RStudio, The Linux Foundation, Microsoft Research, and SAP.
x.com/javierluraschi github.com/javierluraschi linkedin.com/in/javierluraschi
However, I think you are pointing out that devs get "exploited and manipulated" by, surprise, other PMs. I really can't think of someone else that is good at this. So yeah, just remove PMs that are specialized in "politics".
Now, if you remove "politics" PMs then you could argue that customer support, cross-team requests, etc. will impact developers. In this case, dev managers/leads should prioritize those requests and it should be painful to take away dev time to serve other tasks. If it's painful you will probably invest time in fixing the customer support issue rather than managing your customers. If you are spending too much time serving marketing requests, maybe you just have a bad product that needs improvements before it gets shipped, etc.
I really don't believe easing politics is the way to go.
I see PMs having 3 main responsibilities: Project management, user experience and defining requirements.
The problem with this role is that it's REALLY hard to find PMs who are GREAT at all these different skills.
I would rather have a project manager role, user experience researcher role, designer role, business analyst role, etc.
If the project is too small to define each position, then I wouldn't define a role but rather get people to wear multiple hats. There are devs that are very capable at project management, designers that are also good frontend devs, etc. Or bring external help to support the specific needs of your project.