1. Review your own code first.
  2. Write a clear change list description.
  3. Automate the easy stuff.
  4. Answer questions with the code itself.
  5. Narrowly scope changes.
  6. Separate functional and non-functional changes.
  7. Break up large change lists.
  8. Respond graciously to critiques.
  9. Be patient when your reviewer is wrong.
  10. Communicate your responses explicitly.
  11. Artfully solicit missing information.
  12. Award all ties to your reviewer.
  13. Minimize lag between rounds of review.

Source: John Crickett