I finished the book but it took me a long time. It's nice to see that someone dears to question extreme programming and write a book about it in the `extreme programming' series. I personally feel the same with extreme programming. Lots of the practices are very sensible, especially for programmers. My favorites are: Test first programming, Pair programming, and Refactoring. But when we look at the design-part, I feel a bit less confident about XP. I think some basic architecture needs to be in place and that that won't be created by refactoring alone. Pete McBreen takes all XP practices one by one and talks about them. I bought this book because I had good experiences with the earlier books in the series. But this one I had difficulty to get through and it took me a long time to read it completely. Is this because the book is bad quality? I don't know, I had a few problems with it:





1. It's assumed to answer the question: is XP good for your project. Well there is no real answer. It's just for you to find out like it was with the first books in the series



2. All attacks on the xp were a bit fuzzy like Pete doesn't support his own statements



3. I'm more in favor of books that explain things using a diagram and makes me wanna go further because the next chapter has some interesting stuff...