Listen with the Flash player.

Download Team Reviews and Intro to Jupiter Plugin.

This week we’re looking at peer reviews.

Show Notes

This show discusses how we use the Team Review technique talked about in the last show, how I’ve seen it done, and touches on how the Jupiter plugin supports those efforts.

There a few resources mentioned in this podcast. First is the article When Two Eyes Aren’t Enough, by Karl Wiegers that we touched on last time. The next is the CSDL code review standards document that we used as a model to create our own internal code review standards. The last resource is the list of code review tools:

Here’s the outline I worked from during the show.

  • Attributes of Team Reviews

    • Planned, structured; but less formal
    • Review material ahead of time
    • Meeting
    • Basic follow-up, sometimes omitted
    • Collect data
    • Often author lead discussion
  • Ways to make it work

    • Keep time investment small — Basic group interaction stuff
      • Email
      • Groupwise Appointment
      • Links at the bottom
      • What you’ve got questions about
    • Keep it simple
      • Use a simple tool, instead of paper
      • Keep the focus right (defects vs. knowledge sharing vs. design exploration)
    • Review standard procedures
      • Decide on them once
      • Link to them from the announcement e-mail
  • Jupiter Plugin Overview

    • Eclipse plugin
    • Individual, Team, and Rework phases
    • Captures data on resolutions and such
    • Keeps line numbers and files, makes it easy to run through list during review
    • Data kept in source control, so it’s convenient
comments powered by Disqus