Research the recommended resources. Download Karl Wiegers’ templates. (see bibliography link below) Keep your modified process simple. Peer Review the process with entire team. Select work products from entire SDLC. Schedule highest risk items first. Keep group sessions to about 1 hour. Measure what relates directly to other defects. Use measures to prove value of Peer Reviews. Use Lessons Learned sessions for continuous improvement. Bibliography: Bolton, David. Sited January 6, 2015. Excellence Through Code Reviewing. Cohen, Jason, Eric Brown, Brandon DuRette, and Steven Teleki. Best Kept Secrets of Peer Code Austin, TX: Smart Bear, 2006. Sited 6 Jan. 2015. Review: Gilb, Tom, and Dorothy Graham. Harlow: Addison-Wesley, 1994. Software Inspection. Lienhard, Tom. Statistical Tune-Up of the Peer Review Engine to Reduce Escapes. CrossTalk 26.1 (2013): 33-37. Jan. 2013. Sited 6 Jan. 2015. Magazine TechRepublic: Sited 6 Jan. 2015. Developer’s Guide to Peer Reviews. Westfalls, Linda. Sited 6 Jan. 2015. Risk-Based Peer Reviews. Wiegers, Karl. and Peer Reviews in Software: A Practical Guide Goodies for Peer Reviews. (Professional templates at a low cost.) Peer Review Software Tools: Atlassian Crucible Crucible provides code review configurable for Subversion, JIRA, CVS, – Perforce, Eclipse and more. Atlassian Fisheye Fisheye provides a read-only window into Subversion, Perforce, CVS, Git, and – Mercurial repositories for reviews. Code Collaborator by SmartBear SmartBear combines code review with document review. It is – configurable for CVS, Subversion, Git, Mercurial, MKS Integrity, ClearCase, Eclipse, Perforce, TFS, Visual Studio, and others. Code Reviewer by SmartBear SmartBear’s freeware tool for code review. – Code Striker A web-based code reviewing tool. – Code Review Tool by Protium A freeware code review tool configurable for Perforce, Subversion, – GitHub, and Team Foundation Server. Review Board an open source tool and a paid version; drag-and-drop any file onto a review request, – and your team can leave comments on it.
Research the recommended resources. Download Karl Wiegers’ templates. (see bibliography link below) Keep your modified process simple. Peer Review the process with entire team. Select work products from entire SDLC. Schedule highest risk items first. Keep group sessions to about 1 hour. Measure what relates directly to other defects. Use measures to prove value of Peer Reviews. Use Lessons Learned sessions for continuous improvement. Bibliography: Bolton, David. Excellence Through Code Reviewing. Sited January 6, 2015. Cohen, Jason, Eric Brown, Brandon DuRette, and Steven Teleki. Best Kept Secrets of Peer Code Review: Austin, TX: Smart Bear, 2006. Sited 6 Jan. 2015. Gilb, Tom, and Dorothy Graham. Software Inspection. Harlow: Addison-Wesley, 1994. Lienhard, Tom. Statistical Tune-Up of the Peer Review Engine to Reduce Escapes. CrossTalk Magazine 26.1 (2013): 33-37. Jan. 2013. Sited 6 Jan. 2015. TechRepublic: Developer’s Guide to Peer Reviews. Sited 6 Jan. 2015. Westfalls, Linda. Risk-Based Peer Reviews. Sited 6 Jan. 2015. Wiegers, Karl. Peer Reviews in Software: A Practical Guide and Goodies for Peer Reviews. (Professional templates at a low cost.) Peer Review Software Tools: Atlassian Crucible – Crucible provides code review configurable for Subversion, JIRA, CVS, Perforce, Eclipse and more. Atlassian Fisheye – Fisheye provides a read-only window into Subversion, Perforce, CVS, Git, and Mercurial repositories for reviews. Code Collaborator by SmartBear – SmartBear combines code review with document review. It is configurable for CVS, Subversion, Git, Mercurial, MKS Integrity, ClearCase, Eclipse, Perforce, TFS, Visual Studio, and others. Code Reviewer by SmartBear – SmartBear’s freeware tool for code review. Code Striker – A web-based code reviewing tool. Code Review Tool by Protium – A freeware code review tool configurable for Perforce, Subversion, GitHub, and Team Foundation Server. Review Board – an open source tool and a paid version; drag-and-drop any file onto a review request, and your team can leave comments on it.
ASQ0511_20150211_Top10ActionItemsAndReferencesforPeerReview.docx