1 | 2005
Pair Programming Is Peer Review
Pair programming ensures that the code is constantly being peer reviewed. This results in quality that is as good as — or better than — that of "non-agile" projects.

The Classic Way Works Better
Pair programming is not all it's cracked up to be. Traditional peer reviews consistently give us better software quality, and they work for most deliverables.
"Over more than two decades of industry experience, we have accumulated considerable compelling evidence that peer reviews work. In fact, there is barely any evidence to the contrary."
- Khaled El Emam, Guest Editor

Next Issue

The Elusive Quest for Collaboration and Teamwork

Guest Editor: Christopher Avery
Where is the teamwork –– the collaborative leadership, the team mindsets, the collaborative environments, and the team skills –– in IT? Does IT want, need, and deserve teamwork and collaboration as a norm, or is it just too much to ask? Join Guest Editor Christopher Avery next month for a debate on key issues surrounding the elusive quest for collaboration and teamwork in IT. You'll receive best practices on designing and developing collaborative IT organizations, innovative solutions for helping cowboy coders see the error of their ways, and an overview of how organizational structures impact teams and teamwork.

[ Back to Top ]

Peer reviews are arguably one of the best techniques for finding bugs in software prior to its release. Many companies claim that they do peer reviews, although they are done with varying degrees of rigor. Join Guest Editor Khaled El Emam for debate and analysis on the value of peer reviews, how they are implemented in different types of projects, and how they can be optimized. You'll learn ways to perform effective peer reviews and discover how to use them as a driver for business results.