A bad PM can be countered with good engineering management. That said, I've been at a place that had both. Weekends were planned into the schedule and they thought that was the norm. At a certain point, the brain drain was pretty serious (myself included). Not meeting deadlines isn't always an engineering issue it is a management and planning issue.
Another more recent example, boot strapped startup. General engineering goal with a high level of what pieces are needed. Most of those working on it are contractors not always onsight. Functionality decisions are made between a couple of parties, but not communicated down resulting in added effort. In this case, there isn't a lot of engineering pushback, but the PM should be aware of the need to communicate more directly, yet doesn't. When pressed for specs, a blank face. An example, for me, of a bad PM.
Agreed. Thanks for the comments. We actually wrote recently about a "goal first" approach where you start with the strategy and why you are doing something and then clearly articulate the features in a collaborative way. Consider checking it out here - http://blog.aha.io/index.php/goal-first-a-product-roadmappin...
Another more recent example, boot strapped startup. General engineering goal with a high level of what pieces are needed. Most of those working on it are contractors not always onsight. Functionality decisions are made between a couple of parties, but not communicated down resulting in added effort. In this case, there isn't a lot of engineering pushback, but the PM should be aware of the need to communicate more directly, yet doesn't. When pressed for specs, a blank face. An example, for me, of a bad PM.