Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Evolution of Code Review [Infographic]

DZone's Guide to

The Evolution of Code Review [Infographic]

Pros and Cons of Code Review Methods

· Agile Zone ·
Free Resource

See why over 50,000 companies trust Jira Software to plan, track, release, and report great software faster than ever before. Try the #1 software development tool used by agile teams.

The following was provided by our friends at SmartBear

So much has changed in the peer code review space through the years, we’ve seen it all.

We remember the days of meeting room reviews, based on Fagan methodologies. We’ve seen these evolve into reviews being done “over the shoulder,” as well as reviews being done through email. We also started the movement to tool-based peer code review when we first introduced our code review platform, Collaborator.

Though we love tool-based code reviews, we’ve also seen that these other forms of code review are still the go-to method for a number of organizations. In fact, when we surveyed more than 600 software developers, testers, and IT professionals earlier this year, we found that:

  • 72% of teams are doing ad-hoc, or “over-the-shoulder” code review
  • 63% are doing tool-based code review
  • 53% are doing meeting-based code review

No matter what form of code review your team is involved in, it’s important that your team is regularly doing code reviews. In the below infographic, we’ll take a closer look at the different types of peer reviews and the benefits, as well as downfalls, of each. Find out which code review method is right for your team.


Image title



See why over 50,000 companies trust Jira Software to plan, track, release, and report great software faster than ever before. Try the #1 software development tool used by agile teams.

Topics:
code review ,code review methods ,agile development

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}