Peer Code Review – Benefits and Statistics

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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:

Categories:

Tags:

Rapid RTC
Engineering Practices
Scaled Agile Framework
Effective Agile Retrospectives
Reading List
Webinar
WIP
Advanced Roadmaps
Lean and Agile Principles and Practices
Agile Mindset
ROI
Agile Release Planning
Scrum.org
An Appreciative Retrospective
Agile Basics
Kanban Kickstart Example
Jira Plans
Video
What Is Kanban
Professional Scrum Master
Jira
Atlassian
Quality Assurance
ART Success
Portfolio for Jira
ALM Tools
Agile and DevOps Journey
Scrum Master Role
RTE Role
speed at scale
Product Ownership
Introduction to ATDD
Product Management
Release Train Engineer
Nexus and Kanban
Test Driven Development
Continuous Planning
Agile Assembly Architecture
Continuous Delivery
Kanban Basics
AI
SAFe DevOps
Systems Thinking
Team Flow
BDD
Program Increment
Pomodoro Technique
PI Objectives
Tools
Coaching Agile Teams
Accelerate Value Delivery At Scale
System Team
RSA
Kanban Game
Scrum and XP
Kaizen
Professional Scrum with Kanban
Agile Delivery
Perfection Game
The Kanban Method
Scrum With Kanban
RTE
Agile Project
Process Improvement
Agile India
Lean-Agile Software Development
System Integration Environments
Artificial Intelligence
IT Operations
AI Artificial Intelligence
Kaizen Workshop
Agile for Embedded Systems
Agile Israel Events
Slides
Change Management
ATDD vs. BDD
Agile Games and Exercises
agileisrael
Jira Cloud
Agile Israel
LPM
AgileSparks
Frameworks
The Agile Coach
Nexus vs SAFe
ScrumMaster Tales
EOS®
Limiting Work in Progress
Story Slicing
Implementing SAFe
Spotify
Lean Risk Management
Entrepreneurial Operating System®
TDD
Agile Program
LAB
Lean Software Development
Lean Agile Management
Enterprise DevOps
Sprint Retrospectives
speed @ scale
Managing Projects
Business Agility
Professional Scrum Product Owner
Covid19
Risk Management in Kanban
lean agile change management
Elastic Leadership
Sprint Planning
Agile
Lean Startup
Continuous Deployment
Lean and Agile Techniques
Continuous Improvement
DevOps
Lean Agile Organization
Agile Techniques
Lean Agile
Agile Outsourcing
SPC
Manage Budget Creation
SA
Nexus Integration Team
Retrospectives
SAFe Release Planning
Iterative Incremental Development
Agile in the Enterprise
Value Streams
Agile Exercises
SAFe
Jira admin
Lean Budgeting
Sprint Iteration
Continuous Integration
Agile Release Management
PI Planning
Agile Community
Risk Management on Agile Projects
Scrum Primer
Agile Product Development
Daily Scrum
Lean-Agile Budgeting
Agile Development
Scrum Guide
chatgpt
Applying Agile Methodology
Agile Risk Management
Introduction to Test Driven Development
Managing Risk on Agile Projects
Agile Games
Lean Agile Leadership
Amdocs
Scrum
Achieve Business Agility
Software Development Estimation
Hybrid Work
Acceptance Test-Driven Development
Agile Marketing
Self-organization
A Kanban System for Software Engineering
Legacy Enterprise
Nexus
QA
Certified SAFe
Certification
Legacy Code
Scrum Values
Agility
Kanban 101
Planning
Risk-aware Product Development
transformation
predictability
ARTs
Confluence
Rovo
Operational Value Stream
ATDD
Atlaassian
Code
Lean Agile Basics
Presentation
Agile Project Management
POPM
Software Development
Agile Testing Practices
Nexus and SAFe
Large Scale Scrum
Keith Sawyer
Games and Exercises
Agile Contracts Best Practices
Development Value Streams
System Archetypes
Implementation of Lean and Agile
User stories
Releases Using Lean
GanttBan
LeSS
Agile Product Ownership
Kanban
Scrum Master
NIT
Tips
Built-In Quality
AgileSparks
Logo
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