Pairing
A collaboration technique where two team members work together at the same time on a single task or work item, sharing one workflow or workstation. They discuss the approach, review each other's work in real time, and rotate roles to improve quality and spread knowledge across the team. Common in agile for coding, testing, analysis, or design. See Pair Work.
Key Points
- Two people focus on one work item together (e.g., driver and navigator) for real-time feedback.
- Roles rotate frequently to maintain engagement and maximize learning.
- Benefits include higher quality, faster problem solving, and accelerated knowledge sharing.
- Works in person or remotely using shared tools (IDE, whiteboard, screen share).
Example
During a sprint, a developer and a tester pair on a user story to create automated acceptance tests. They alternate between writing tests and implementing code, catching defects immediately and documenting edge cases as they go.
PMP Example Question
Which scenario best describes pairing on an agile team?
- Two developers work on different modules in parallel to finish faster.
- Two team members share one workstation to complete the same user story, switching roles regularly.
- A developer completes a feature and hands it to a tester at the end of the day.
- The Scrum Team discusses progress in the Daily Scrum.
Correct Answer: B — Two people collaborate on one task at the same time
Explanation: Pairing involves two team members working together on a single work item with frequent role changes and continuous peer review.
