Developer code reviews

Am about to write up a checklist for performing software code reviews. As lead dev I often find myself performing this task since Quality Assurance is one of my key job outputs. 

If I’m always performing the review then why document it? Well, for a number of reasons. First one being we’ve recently adopted SCRUM. SCRUM promotes cross-functional teams which means individually we should also be cross-functional, to some extent. Developers may never become designers but surely most developers can perform code reviews?

Its a given that performing code reviews requires a keen eye and attention to the details. It can require great skill when detecting XSS vulnerabilities or profiling issues but for the most part every developer can spot a boo-boo or coding horror. We all make mistakes from junior to senior. A peer review is an excellent tool to foster quality.

So once I have that documented checklist I can delegate! What a beautiful beautiful concept :-)

So, I’m still busy writing up that checklist! But in the meanwhile I’ve done a bit of research to ascertain whether my checklist is on par with the industry’s.

Some interesting links/articles I’ve stumbled upon:

The first one is a real gem