I (Chad) was asked to provide some notes and tips on pair programming, based on his experience with part- and full-time pair programming, in-person and remote, since the early 2000's.
Here they are. Pair programming is a big topic, and much has been written on it, but I've tried to keep it short, and mention the points I find most important.
The MartinFowler.com article above on pair programming is very thorough. Here are a few points I feel are important to call summarize, and provide some additional info/analysis. I won't necessarily describe each one; please refer to the article for that.
(This approach is not mentioned in the article)
Pairing session: [Short title describing topic]
More detailed description indicating what the session is about