The other issue I have with project management in general is that there is no universal model that incorporates different ways of doing things depending on the situation.

For example, at a macro level, there is an inability for PMBOK and PRINCE2 to accommodate the agile methods. To me this means that the good points from the agile methods are not necessarily easily slotted into a non-software project. Indeed, the reverse can be true too.

Another example is that some of the very real benefits of the systems engineering discipline are not incorporated into the project management paradigm. Yet the "engineering management" part (as opposed to the "engineering systems" part) of systems engineering has some very robust concepts and tools.

Perhaps it is my own bias and the way I do things and manage projects, but to me there isn't really a "black vs white" way of doing things. There is a "continuum" of different ways and where your project is located within that continuum, will determine the most appropriate tools and techniques you use. I hope to explain this further when I get further into my blogging and I discuss what I call the "seeing the knowledge elephant".