Unclear about which is whose opinion (Score 1)

Thanks for the review. On first reading, I quit about a quarter of the way through, at the third substantive error in fact, which the authors had been informed of in reviews and feedback from earlier material over the last few years.

A second reading shows that I might have been too hasty in turning off -- the long summary of the book might have been a simple paraphrase, reflecting only the authors' opinions and not those of the reviewer. By the end of the second reading, I'm still not sure which way to read it, so I'll give benefit of the doubt.

My second reading also revealed several other wilful misreadings and misrepresentations that the authors had published in earlier material, and had been called on. For instance, that "XP is risky": each of the practices in fact manages, in part or whole, at least one risk which prevents software teams from delivering software. Or that "XP is good only for maintaining software": in a sense that's true, but only because the first releasable build happens immediately and it's all maintainance upgrade from there!

Overall, I hope that the reviewer will have an opportunity to examine "Extreme Programming" further sometime later in his career. At the very least, that the negative spin by the authors on XP will not keep him from looking at other "agile" methods and practices which can benefit his team and his organization.