Peer Code review includes a complete review of all the source code that is transitioned as part of the release, all the unit test cases, all the integration test cases and a demo of the integrated build of the application in its true execution environment by a team of peer developers, who preferrably are not involved directly in the development of that release, or at least have the opportunity to review modules that they did not develop.

Peer developers who are not directly involved in the development process, but have a complete understanding of the implementation and the implementation platform will perform the Code review. The goal is not only to ensure the quality of execution, but to ensure that consistency is maintained in the organization codebase in all aspects, from configuration, logging and event handling to naming conventions, indenting, commenting and even formatting of code.

From a Separation of Duties Perspective, it is advisable to have the person performing the code review not be the person who was developer for that code. This not only ensures a detached perspective, it also encourages healthy competition and better quality.