The secondary order effects cannot be ignored either. On our team, pairing is used to:
- Coach more junior developers into being more proficient at their work
- Share knowledge so that norms, standards, and other knowledge can propagate through the team in a more natural (and effective) way than documentation
- Share techniques at the more tactical level
- Further explore the solution space and do better planning and execution (go slow to go fast)
And others.