[peteevans]

In a lot of business code reviews are compulsory (or at least some sort of inspection) and often required for accreditation. There is often a convenient change set from version control tools such as SVN/GIT etc that can be used to define review content and these change set often have associated diff tools to help. On previous projects we'd just branch every change in SVN and get someone else to check the changeset to merge onto trunk. Saying that we are currently using JIRA with associated code review tools and this is great and provides a nice log of comments and responses which we can present to QA (as review evidence) on a simple web interface. Reviewing the code is a great way of sharing the knowledge in addition to finding bugs earlier (if done well).