Everyone agrees that peer code inspection finds bugs, makes code more maintainable, and promotes learning and sharing. But how much time does it take? Are the savings worth the expense?
Use this ROI calculator to see the business case for Collaborator and Collaborator Community.
For the table below, the default numbers come from industry-standard sources, including some of our own customer data. When you consider the cost per defect in QA or at the customer site, consider the time to find and the time to fix, and try to account for intangibles such as Customer Goodwill.
This calculation represents a savings of %, or $, per release cycle.
Cost of the code review tool is not included in this evaluation. Use our Pricing Page to get this cost depending on tool choice, the number of developers, and licensing scheme.
Try Collaborator Free
1 Industry-standard rate: 45% of defects are found during code review instead of QA or at customer sites.
2 Industry-standard rate, also found in several case studies at SmartBear's customer sites: Code review typically costs 30% that of QA because bugs are found faster and locations/methods of fixes are already identified.
3 Code review removes defects both from QA and at customer sites, so these numbers are reduced proportionally.
Best Practices for Peer Code Review
Code Review: An Agile Process
What is Code Review?
The Case for Reviewing Requirements and Design Documents
Why Review Code?
What Technical Documents Should You Review?
Thanks for subscribing!
Keep an eye on your inbox for more content like this.
80 Tips from Real Developers: Guidebook for Writing Better Code
Developer Collaboration Online Summit
Delivering Quality Software Using Visual Studio: Faster, Better, Cheaper