Pair Programming Review
In a pair programming approach, two programmers work simultaneously on the same program at a single workstation (Beck, 2000; Cliburn, 2003; McDowell et al., 2003). This approach provides an informal review of the software artefact as the two programmers work continuously and incrementally on the working product (Katira et al., 2004).
The rationale behind the pair programming paradigm is that "two heads are better than one" (Jeffries, Anderson & Hendrickson, 2001; McDowell et al., 2003; VanDeGrift, 2004; Williams & Kessler, 2000). As the pair works, typically with one partner coding while the other checks and reviews the software, they can identify defects and make corrections immediately (Katira et al., 2004; McDowell et al., 2003).
[Source: Modern Software Review: Techniques and Technologies]
Also See:
Technical Review
Importance of Review
Types of Review Process Structures
Difference between Formal & Informal Reviews
Deciding Whether to do Formal or Informal Reviews
Software Design Reviews
Formal Review & Informal Review
Walkthrough and Inspection
Peer Review
Software Management Reviews
Test Case review
Code Review