This is not a good practical introduction to software project management. It uses confusing language and regularly uses terms before defining them in chapters much later on, by which time I was totally confused and had wasted a lot of time and effort trying to figure out what was meant.
This reads like a book by that college professor whom no one ever understood. It is undoubtedly well researched and contains many valuable insights. Unfortunately they have been obfuscated with unnecessarily complicated language and academia-speak. A lot of effort is required to get the most out of the book. A wasted opportunity! A book full of really useful information, clouded by its delivery. Some of the sentences look like strings of randomly assembled manager speak -- meaningless -- it's only after careful analysis that each sentence can be understood, and by then the flow and context have been lost.
If you're thinking -- this guy must be thick, he didn't get it -- then be warned, I'm no slouch. Degree from Oxford, eight years experience developing and managing software projects. This book was understandable, but only just.
I suggest buying Steve McConnell's "Software Project Survival Guide". Along with "Code Complete" and "Rapid Development" these will give you more readily understandable info than "Software Project Management" will.