Sigh, I had high hopes for this book. But it is obviously written by a moron that doesn't know project management, which leads to outrageous claims for Agile versus Waterfall, that gets a real project manager to think he doesn't understand anything. As an example, he describes the revolutionary concept of breaking down tasks in lesser, and more detailed tasks, as something totally unique to Agile (anyone heard about Work-Breakdown Structures, a basic block of project management?), or that Waterfall methods only evaluate risks in the beginning of projects (check Prince2, IPMA, PMI, etc and you'll find that constant risk management, handling, and updating is at the core). 

The moron explains that having intermediate goals is a good and unique thing in APM, but he obviously has never heard of Milestones…

This is a book best avoided, as drivel like this will scare people away from APM, instead of adapting the parts that are good.