|
Peer Reviews in Software: A Practical Guide
 |
Author: Karl E. Wiegers
List Price: $39.99
Our Price: Click to see the latest and low price
ISBN: 0201734850
Publisher: Addison-Wesley Pub Co (15 December, 2001)
Edition: Paperback
Sales Rank: 37,530
Average Customer Rating: 5 out of 5
|
Customer ReviewsRating: 5 out of 5
Essential reading for any software development team
Every developer I have known has experienced the phenomena of spending an inordinate amount of time searching for a bug only to have a colleague look at the code and find it almost immediately. Study after study has indicated that the worst review process for software is self-criticism and the best is to have other coders take a good look at it. Therefore, it is logical that a formal process for developers reviewing each others code be implemented. The problem is that the former is informal, making it "off the books" and not subject to review by decision makers. Being human, developers react differently when their livelihood is potentially at stake, which can cause problems and prevent adequate reviews of the code.
Creating a stable, scalable and structured peer review system is not something that can be done by fiat or in a short time. It requires clear managerial direction that inspires confidence and builds a sense of security for both the evaluator and evaluated. Creating such an environment is the key and that is the main point of value in this book.
Wiegers lays out in great detail how to create a culture where all involved are peers in the real sense. It is absolutely necessary that everyone in the review process understand that creating quality software is the only thing that matters. Therefore, posturing, ego tripping, ego inflating, ego protection and all related activities must be suppressed. These are the most difficult tasks for professional humans to engage in, and it requires a combination of carrying a big stick to move the process as well as a soft pillow for the necessary falls from perfection. Wiegers shows you how to do this with the skill of a counselor.
In my reading of the trade press, the recent rise in the concern for computer security has led to a great deal of coverage about errors in software. Responding to this pressure, Bill Gates has sent out a public memo noting that quality is now the number one priority at Microsoft. The best way to achieve this quality is to have an effective peer review process and in this book you can learn how to do that. In the new world order of software, your very survival may be at stake, so your plan of action should include a rendezvous with this book.
Rating: 5 out of 5
The Best In Depth Peer Review Textbook
Excellent up to date survey of the literature, excellent survey of the many methods and analysis of their differences. A rich insight into the area of peer reviews in general, including Inspections and their variations. Practical for the industrial user. Highly recommended.
Rating: 5 out of 5
Persuasive, practical
I have attempted over the years to get various organizations to buy into peer reviews. We have lots of evidence why these reviews are highly worthwhile, but their implementation has not been anything to write home about. There's always many reasons why organizations don't buy in or give peer reviews half-hearted support.In my opinion, this book is an important contribution to the field. I'm sufficiently impressed that I've passed copies of the book to a few busy software development managers, software engineers and business managers so far. They've taken the time to look at it, and they find the book talks to them -- it is clear, addresses their issues, offers practical solutions which they may not have considered before, and is persuasive. I believe the book will have a postive influence in their organizations. I hope to see copies in lots more people's bookshelves.
Similar Products
· Software Requirements, Second Edition
· Creating a Software Engineering Culture
· Software Project Survival Guide
· Software Inspection
· Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products
|
