A practice that originated with eXtreme Programming (XP), where two people work closely together, and frequently switch roles, with one writing code (the Driver), and the other reviewing and thinking of ways to test the code (the Navigator). Also, in a less formal sense, pairing can occur any time two team members work together such that the overall quality of the solution they produce is better than what would be possible if they worked alone. Some of the benefits associated with pairing include higher quality code thanks to real-time feedback, along with reduced likelihood that rework will be needed, either in the form of fixing defects or refactoring.
Pair Programming Video
Pair Programming Podcasts
Pair Programming Example
Authored by Philip Rogers
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Resources as the source, who the author is, and the photo creator (if used).