1. Informal review
   1. No formal process
   2. May take the for of pair programming or a technical lead reviewing desings and code
   3. Results may be documented
   4. Varies in usefulness depending on the reviewers
   5. Main purpose : inexpensive way to get some benefit
2. Walkthrough
   1. Meeting led by author
   2. May take the form of scenarios, dry runs, peer group participation
   3. Open-ended sessions
      1. Optional pre-meeting preparation of reviewers
      2. Optional preparation of a review report including list of findings
   4. Optional scribe (who is not the author)
   5. May very in practice from quite informal to very formal
   6. Main purpose : learning, gaining understanding, finding defects
3. Inspection
   1. Led by trained moderator (not the author)
   2. Usually conducted as a peer examination
   3. Defined roles
   4. Includes metrics gathering
   5. Formal process based on rules and checklists
   6. Specified entry and exit criteria for acceptance of the software product
   7. Pre-meeting preparation
   8. Inspection report including list of findings
   9. Formal follow-up process (with optional improvement components)
   10. Optional reader
   11. Main purpose : finding defects
4. Technical Review
   1. Documented, defined defect-detection process that includes peers and technical experts with optional management participation
   2. May be performed as a peer review without management participation
   3. Ideally led by trained moderator (not the author)
   4. Pre-meeting preparation by reviewers
   5. Optional use of checklists
   6. Preparation of a review report which include the list of findings, the verdict whether the software products meet its requirements and, where appropriate, recommendations related to findings
   7. May vary in practice from quite informal to very formal
   8. Main purposes : discussing, making decisions, evaluating alternatives, finding defects, solving technical problems and checking conformance to specifications, plans, regulations, and standards