volume_mute

Why Pair Programming Productivity Can Match Two Individual Programmers

publish date: 2026/06/04 22:55:38.726762 UTC

volume_mute

You might expect that two programmers working in a pair would only produce half as much code as two programmers working independently. Which of the following reasons help explain why pair programming productivity can be comparable to — rather than half of — two people working alone? Select all that apply.

Pairs discuss the software design before development and so probably have fewer false starts and less rework than individual programmers who start coding without discussion

Pair programmers write less code overall — they avoid over-engineering because two perspectives challenge unnecessary complexity

Working in a pair provides social motivation and accountability, reducing the risk of developers becoming distracted or losing focus

The informal code review that occurs naturally in pair programming catches errors early, meaning less time is spent repairing bugs discovered during later testing phases

The continuous sharing of knowledge during pair programming reduces the time spent looking up documentation or asking colleagues for help

Pair programming always produces code that runs twice as fast as individually written code

Correct Answer

(1) Pairs discuss the software design before development and so probably have fewer false starts and less rework than individual programmers who start coding without discussion

(2) The informal code review that occurs naturally in pair programming catches errors early, meaning less time is spent repairing bugs discovered during later testing phases

(3) The continuous sharing of knowledge during pair programming reduces the time spent looking up documentation or asking colleagues for help

(4) Pair programmers write less code overall — they avoid over-engineering because two perspectives challenge unnecessary complexity

(5) Working in a pair provides social motivation and accountability, reducing the risk of developers becoming distracted or losing focus

Explanation

Research suggests pair programming productivity is comparable to two people working independently for several reasons: fewer false starts because pairs discuss the design before coding; less time repairing bugs because the informal review catches errors early; knowledge sharing reduces time spent looking things up; two perspectives challenge over-engineering, keeping code simpler; and social accountability reduces distraction. Pair programming does not magically double code execution speed.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Exercises: Applied Agile Development