So much has changed in the peer code review space through the years. Here at SmartBear, 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.
Share this Image On Your Site
Dev Collaboration for Your Entire Organization
Developer collaboration tools, like Collaborator, have transformed the ways teams conduct code reviews by providing a single platform for dev teams to review their work and catch bugs before software hits the market. These tools provide critical integrations into your existing tools and environments, and offer reporting and traceability features that aren’t available in traditional code review methods.
Get started today! Start your free trial of Collaborator.