Is your team thinking about doing
code review, but isnt sure if its worth the time?
Code review used to be a huge
pain. While they were certainly effective at finding bugs, old methods of
code review simply took too much time, and many programmers still feel like
its not worth the trouble. But online collaborative review tools like Code
Collaborator changed the reality of code review by removing the grunt working,
making fast and efficient code review a reality.
If youre not sure if code review
is worth your teams time, here are three short, simple steps to try it and
1. Download a free evaluation copy
of Code Collaborator.
2. Have your team spend 25 minutes
per day reviewing code for one week.
3. Assess your teams results
using straightforward metrics (number of bugs found vs. time spent), collected
automatically by Code Collaborator. To calculate how much time your team spends
to find each bug, divide the total time spent on reviews by the total number of
You may be surprised by the
results: most teams find and fix one bug
for every 10-15 minutes spent doing reviews.
Consider the greater cost to fix
those bugs once they reach QA or worse, customers.
Want to know more about this
topic and how to achieve maximum results in minimal time with code review?
Check out our Evaluation Tips document, Is Code Review for You?