This book is written by someone with plenty of experinence of projects with problems. I think anyone who has been on a project will be able to empathise with at least some (if not many) of the problems that are catalogued here.
What's useful is the book offers guidance as to how these problems can be minimised by proper planning and tracking, and responding to changes in a sensible manner. It doesn't try to mandate a particular way of working or running a project (practioners of agile methodologies may find that some of their ways are very compatible) but does present a realistic business case for how projects can be managed well, and be managed badly.
This is an excellent book, not only for your bookshelf, but also for dipping into regularly in order to anticpate problems rather than reacting to them.