Most code reviews are done in-person, 60% according to data from a Forrester Consulting study commissioned by Klocwork. So how do you accommodate remote sites, out-of-office employees or off-shore development shops?
Most software developer teams will face some form of remote development challenge during their careers or product cycles. As demonstrated from the data above, the breakdown of remote need is as follows:
- 76% use some form of outsourcing,
- 64% have some developers located outside of the main campus,
- 40% of reviews are conducted with remote participants.
You can’t let development come to a grinding halt simply because a critical team member is not physically available at the scheduled time or location. For most organizations, code reviews need to be performed and employee travel is not the solution for cost and timing reasons. This has driven the adoption of lightweight review processes and new tools that support it.
Klocwork built a code review tool for this express purpose. Other ones exist like Code Collaborator and the open source Review Board . How do you support your remote code reviews? Email? Wiki? Or a purpose-built tool like one of the ones mentioned?
Related posts:
- Developers think code reviews are great… what?
- Code Reviews – Mandatory but Ad-Hoc?
- Static analysis and code reviews
Tags: Code Review, software developer
Very interesting data Eric, the challenge we face in security code review is organizations letting their code out of their facility. Up till now, most security code reviews have to happen physically in the vendor’s premises. Interested to see if have others have other opinion.
Good point Sherif. I had not really thought about security other than using a VPN solution to gain access to internal corporate resources.
[...] This post was mentioned on Twitter by Ahmed M. Dirie, Tom Pierson. Tom Pierson said: How do you support a remote code review process? http://bit.ly/9MT2pZ #in #codereview [...]