Take a look at this review from KnowledgeTrain:
I think it definitely captures what we were trying accomplish with our book. I agree with almost all of his criticisms — for the most part, they are a reflection of decisions that we made about the direction of the book. (As you know, in any project of any reasonable size the team always has to make tradeoffs!)
I liked what he had to say about our writing style, which I really think is a strength of our book:
- There are too many books about software project management or software engineering which are dry, overly complex and boring, but this book is not one of them. It was a joy to read because their style of writing is clear without being simplistic and the authors describe things in just the right amount of detail. It seems they understand their audience and set out to write in an extremely helpful and practical way. They have certainly achieved this.
And I especially like this part:
- I would recommend this book to anyone who works on a software development team because the book has so much practical advice to help people improve their capability to deliver quality software. Come to think of it, I would also recommend it to senior managers of companies who have a negative view of their own software development teams. Perhaps then senior managers might understand why committing resources to process improvement is one of the best investments they can make.
Exactly! I’m really glad that idea came across — it was a point that Jenny and I really thought was important.