The company was a tech company but the people with influence were ignorant of general SW development practices. If a project manager did not cut it, they were replaced with another one just like the previous one. Tech had little input on the next choice - after all, it was the project managers dept. I suspect there are good PM's with a tech bent, but they are hard to come by.
I hope you can make a difference by hiring and encouraging others PM's who do want to improve and understand the technical environment they are in, and not just live on the 'project schedule line'. Spend a day with support, spend a day with QA, talk to an engineer and find out why one task on your schedule is dependent on the other. It will make for a better cohesive team with common goals (and ideally less departmentalism).
If you don't do this- Us Vs Them kinda environment emerges rather too quickly.
Some companies hire these MBAs straight out of college, and put them into fast track programs. This is not a bad thing in itself, but it means you can end up with a (S)VP or C level who has never actually worked in the area the company is in.
This leads into "great" ideas being generated (e.g. every new hire has to be signed off by the VP of the division, all purchasing needs 2 levels of sign off etc), that may sound great, but to people actually living with the ideas, it causes massive issues.
Without fail, everytime I have seen a policy like these that makes me groan out loud, when we find out who came up with it, they have an MBA.
I deal with this all the time as a developer. I am tired of guys who "used to develop, so they know what they're talking about".
Some of my worst managers think they know everything, they think they know how quickly something can be done, when they simply don't.
Many times they are downright disrespectful because they think they know it all.