Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    How could you possibly engage in a code review if you don't want to be directly confronted with your work? Commented May 19, 2015 at 19:00
  • My team schedules a code review at the end of each sprint/iteration,etc or when a certain milestone or has been reached. We have two defined REVIEW tags, REVIEW_R for dead/pointless code for requirement validation and REVIEW_Q for code quality concerns. Either myself (lead) or the project manager will copy all REVIEW_* comments from the task list in visual studio. The REVIEW_Q list is dumped into a powerpoint presentation along with the code from each. Commented May 20, 2015 at 17:38
  • The REVIEW_R list is sent to our requirements team (which consists of a few developers, the requirements manager and a tester/QA/functional). They either concur with the observation of the REVIEW_R comment or they identify the requirement that this code fulfills. The updated REVIEW_R list, is added to the bottom of the powerpoint presentation. Finally, the development team hashes it out in a meeting and resulting changes are made. It becomes a group review, not just developerA telling developerB their code sucks. YMMV Commented May 20, 2015 at 17:38