Close this search box.
Close this search box.
Close this search box.

Peer Code Review – Benefits and Statistics


Benefits and statistics of embedding peer code review into your software development process.

As a Lean-Agile coach, I regularly talk with software development groups about the benefits of adding code review to their development process. Some easily embrace it and some require a little bit of persuasion, but usually, I find enough internal allies to initiate the change. Lately, I encountered a whole group that completely rejected this essential practice as a luxury they can not afford. Explaining that they will see immediate ROI within a sprint or two was not enough to convince them. So, I sat to compose the following list and sent it to the group. Luckily I had a sympathetic ear with the general manager of the business unit who embraced it and made it easier for the team to experiment with the practice. All’s well that ends well… here is the list, shared with you too.

Code review is a software quality assurance practice in which one or more developers, called “reviewers”, inspect program code by viewing, reading, and checking it. At least one reviewer is not the code author. Peer code review is done by peer programmers, usually one.

So why should you deploy code review? Here are some of the benefits:

  1. BIQ – Builds quality into your process with the best ROI
  2. Fewer defects in your code – by more than 80%, see the next section below for more details
  3. The cost of software defects is lower the earlier they are detected, x10, x100, and even x1000 times – it starts with collaborative story writing and continues with peer code review
  4. Builds peer pressure on code quality due to the Ego Effect – People will write better code when they know their code is going to be “reviewed”
  5. Knowledge sharing between team members promotes internal learning
  6. Provides opportunities for mentoring junior developers – junior developer can review the mentor’s code and the mentor can review the junior’s code, both practices will support the junior’s development
  7. Supports the development of T-shaped professionals – T-shaped people are experts in one area but understand enough in other domains to support the continuous flow of the development process
  8. Removes the notorious single-point of failure manifested by the one expert developer
  9. By discussing and collaborating on code its readability is inherently improved
  10. Code standardization – style of code becomes similar in the team and thus more readability, better support, and maintenance
  11. Technical collaboration results in better estimates and better planning of efforts ahead
  12. Provides another checkpoint that requirements are fulfilled

Apparently, as seen in the following list of statistics, code review is the most effective practice you can embed into your software development process to strengthen BIQ (built-in quality).

Steve McConnel in his book CodeComplete provides the following statistics:

“… software testing alone has limited effectiveness – the average defect detection rate is only 25 percent for unit testing, 35 percent for function testing, and 45 percent for integration testing. In contrast, the average effectiveness of design and code inspections is 55 and 60 percent. Case studies of review results have been impressive:

  • In a software-maintenance organization, 55 percent of one-line maintenance changes were in error before code reviews were introduced. After reviews were introduced, only 2 percent of the changes were in error. When all changes were considered, 95 percent were correct the first time after reviews were introduced. Before reviews were introduced, under 20 percent were correct the first time.
  • In a group of 11 programs developed by the same group of people, the first 5 were developed without reviews. The remaining 6 were developed with reviews. After all the programs were released to production, the first 5 had an average of 4.5 errors per 100 lines of code. The 6 that had been inspected had an average of only 0.82 errors per 100. Reviews cut the errors by over 80 percent.
  • The Aetna Insurance Company found 82 percent of the errors in a program by using inspections and was able to decrease its development resources by 20 percent.
  • IBM’s 500,000-line Orbit project used 11 levels of inspections. It was delivered early and had only about 1 percent of the errors that would normally be expected.
  • A study of an organization at AT&T with more than 200 people reported a 14 percent increase in productivity and a 90 percent decrease in defects after the organization introduced reviews.
  • Jet Propulsion Laboratories estimates that it saves about $25,000 per inspection by finding and fixing defects at an early stage.”

A couple of notes:

Are there any downsides to code review?

Apparently, it takes time, but most often it saves more time already within the same Sprint !!!

Code review may be done with a peer, tech expert, manager, or group of peers. It has siblings such as pair programming, and group programming. Each practice has its own benefits and all are worth practicing.

However, research suggests that the most cost-effective practice with the highest return on investment is “peer code review” where peers in the team review each other’s code.

So what are you waiting for? Go and try it.

Subscribe for Email Updates:



Agile Israel
Daily Scrum
Professional Scrum Master
The Agile Coach
User stories
Artificial Intelligence
Nexus and Kanban
Risk Management on Agile Projects
Lean and Agile Techniques
Reading List
Risk-aware Product Development
Agile Release Management
Lean Risk Management
Large Scale Scrum
Entrepreneurial Operating System®
Release Train Engineer
Nexus and SAFe
Introduction to Test Driven Development
Limiting Work in Progress
speed @ scale
ScrumMaster Tales
Agile Mindset
Enterprise DevOps
An Appreciative Retrospective
Continuous Delivery
Value Streams
Legacy Code
Pomodoro Technique
Kanban Basics
Perfection Game
Effective Agile Retrospectives
Sprint Retrospectives
Product Ownership
System Integration Environments
Agile Delivery
Lean Software Development
Agile Israel Events
Managing Projects
Scrum Primer
Agile Product Ownership
Advanced Roadmaps
PI Objectives
Kanban Kickstart Example
Keith Sawyer
Acceptance Test-Driven Development
Scaled Agile Framework
Applying Agile Methodology
Sprint Planning
Agile India
Managing Risk on Agile Projects
Agile Techniques
Lean Agile
SAFe DevOps
Portfolio for Jira
ALM Tools
Agile Project Management
Systems Thinking
PI Planning
Lean-Agile Software Development
Lean Budgeting
Engineering Practices
Agile Product Development
Scrum Guide
speed at scale
Coaching Agile Teams
Agile Release Planning
Software Development Estimation
Lean Agile Management
Nexus Integration Team
Business Agility
Nexus vs SAFe
Agile Exercises
Agile Development
Agile Testing Practices
Agile Program
RTE Role
Releases Using Lean
Risk Management in Kanban
Jira Plans
Agile Games
Lean Agile Organization
A Kanban System for Software Engineering
Professional Scrum Product Owner
Scrum Master
Built-In Quality
Sprint Iteration
IT Operations
Team Flow
Agile Risk Management
Agile for Embedded Systems
Implementation of Lean and Agile
Lean Agile Leadership
Scrum Master Role
Jira Cloud
Kaizen Workshop
System Team
Legacy Enterprise
Continuous Integration
Manage Budget Creation
Principles of Lean-Agile Leadership
AI Artificial Intelligence
Hybrid Work
Agile Basics
Agile and DevOps Journey
Program Increment
Lean Startup
Lean-Agile Budgeting
Rapid RTC
Agile Community
Agile Assembly Architecture
Elastic Leadership
Agile Marketing
What Is Kanban
Software Development
Introduction to ATDD
Implementing SAFe
Games and Exercises
Continuous Improvement
Kanban Game
Agile in the Enterprise
Lean and Agile Principles and Practices
Continuous Deployment
Operational Value Stream
System Archetypes
Product Management
Agile Games and Exercises
Quality Assurance
Process Improvement
ART Success
Kanban 101
Scrum Values
Accelerate Value Delivery At Scale
SAFe Release Planning
Jira admin
Achieve Business Agility
lean agile change management
Scrum With Kanban
Agile Contracts Best Practices
Professional Scrum with Kanban
The Kanban Method
Test Driven Development
Change Management
Story Slicing
Agile Project
Iterative Incremental Development
Scrum and XP
Lean Agile Basics
Certified SAFe
Agile Outsourcing
Continuous Planning
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart