Movies Books Music Food Tv Shows Technology Politics Video Games Parenting Fashion Green Living more >

Lunch » Tags » Books » Reviews » Peer Reviews in Software: A Practical Guide » User review

Essential reading for any software development team

  • Mar 22, 2002
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.

What did you think of this review?

Fun to Read
Post a Comment
About the reviewer
Charles Ashbacher ()
Ranked #78
Charlie Ashbacher is a compulsive reader and writer about many subjects. His prime areas of expertise are in mathematics and computers where he has taught every course in the mathematics and computer … more
Consider the Source

Use Trust Points to see how much you can rely on this review.

Your ratings:
rate more to improve this
About this book


Peer review works: it leads to better software. But implementing peer review can be challenging -- for technical, political, social, cultural, and psychological reasons. In this book, best-selling software engineering author Karl Wiegers presents succinct, easy-to-use techniques for formal and informal software peer review, helping project managers and developers choose the right approach and implement it successfully. Wiegers begins by discussing the cultural and social aspects of peer review, and reviewing several formal and informal approaches: their implications, their challenges, and the opportunities they present for quality improvement. The heart of the book is an in-depth look at the "nuts and bolts" of inspection, including the roles of inspectors, planning, examining work products, conducting code review meetings; improving the inspection process, and achieving closure. Wiegers presents a full chapter on metrics, and then addresses the process and political challenges associated with implementing successful software review programs. The book concludes with solutions to special review challenges, including large work products and software created by distributed development teams. For all developers, project managers, business analysts, quality engineers, testers, process improvement leaders, and documentation specialists.
view wiki


ISBN-10: 0201734850
ISBN-13: 978-0201734850
Author: Karl E. Wiegers
Publisher: Addison-Wesley Professional

First to Review
© 2014 Lunch.com, LLC All Rights Reserved
Lunch.com - Relevant reviews by real people.
This is you!
Ranked #
Last login
Member since