When initially introducing pairing, it's worth recognizing that it requires more concentration, mainly because pair of programmers are less likely to get interrupted or distracted.

Before starting, discuss pairing etiquette:

• Agree on a start and finish time for the session. Ensure you schedule time for regular breaks.
• Discuss how to avoid distractions. For example, turn off email and instant messenger notifications. Also, have mobile phones turned to silent or preferably off.
• Decide how to manage outside interruptions. For example, explain to the person or persons interrupting that you'll be on a break soon, tell them when that break is and that you can talk to them then.
• Determine who will drive first and how often you'll exchange the keyboard. Make sure you swap the keyboard regularly. Do not allow one person to drive exclusively. 
• Accept that pairing is not silent, but like any new skill, we will need to learn how to describe what we're doing while coding. It's often odd at first.

Remember, don't just pair program the "hard bits," pair program for an entire story from start to delivery. 

To keep things interesting, try pairing with different members of the team. Also, bear in mind that you both don't have to be software developers to make a pair.

For example, try pairing with a Product Owner, in particular, if the current work involves creating a tangible aspect of the system such as part of the user interface or another form of output. In these situations, they will be able to offer immediate feedback on the direction you're taking.