Pair Programming
Pair Programming is an XP practice where two developers work together at one workstation, with one writing code (the driver) and the other reviewing each line in real time (the navigator).
Know it well enough for the exam? Questions on Pair Programming are scenario-based, not definitional.
Practice it freeExplanation
In pair programming, the driver focuses on the tactical aspects of writing code while the navigator thinks strategically, reviewing for errors, considering edge cases, and thinking about the bigger picture. The roles are rotated frequently to keep both programmers engaged and to share knowledge.
Pair programming produces higher-quality code with fewer defects because every line is reviewed as it is written. It also accelerates knowledge transfer between team members, reduces the risk of knowledge silos, and helps onboard new team members quickly. While it may seem like two people doing one person's work, studies show that the reduced defect rate and improved design often offset the cost.
Pair programming is not meant for all tasks. Simple, routine tasks may not benefit from pairing, while complex, high-risk, or unfamiliar work benefits greatly. Teams should use judgment about when pairing adds value.
Key Points
- •Two developers at one workstation: driver writes code, navigator reviews
- •Produces higher-quality code with fewer defects
- •Accelerates knowledge sharing and reduces knowledge silos
- •Most beneficial for complex, high-risk, or unfamiliar work
Exam Tip
Pair programming is an XP practice focused on real-time code review and knowledge sharing. It is not a Scrum practice, though Scrum teams may adopt it.
Frequently Asked Questions
Related Topics
Extreme Programming (XP)
Extreme Programming (XP) is an agile software development framework that emphasizes technical excellence and engineering practices such as pair programming, test-driven development, continuous integration, and frequent releases.
Test-Driven Development (TDD)
Test-Driven Development (TDD) is a software development practice where developers write a failing test before writing the production code that makes it pass, following a red-green-refactor cycle.
Cross-Functional Teams
A Cross-Functional Team is a team that possesses all the skills and competencies needed to accomplish the work without depending on others outside the team.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice Pair Programming
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.