A pairing session is a bounded period in which two developers work together on a task. Effective sessions give both people a comfortable view of the code, a place where conversation will not distract others, and enough time to focus without exhausting the pair. section 11.2.3
Shape a session around the team, task, and available energy:
- Start with 30 minutes to an hour, then adjust based on how the team feels. Avoid forcing pairing throughout the workday; three to four hours per day may already be a practical maximum. section 11.2.3
- Pair on work that benefits from two perspectives, such as adding a new feature. Skip routine, repetitive, and simple tasks when the collaboration costs more than it adds. section 11.2.3
- Use Pomodoro, tag-team, or ping-pong styles when explicit time limits help the pair switch roles or maintain focus. section 11.2.3
- Treat pairing as an experiment rather than a mandate: establish expectations, try it for a week or sprint, and review the results during a retrospective. section 11.2.1
A low-risk trial
A hesitant team can begin with a voluntary, 30-minute pairing session when someone gets stuck. Afterward, the team discusses whether the focused collaboration helped and decides whether to try pairing on a larger feature or during the next sprint. section 11.2.1 section 11.2.3
