Pair Programming is when two people write code together on one machine. It helps improve code quality, readability, and simplicity. Not only is it an on-the-fly code review, since it has two pairs of eyes looking it over, but it is also a form of design review, thereby beating regular code reviews on several fronts. Pairing also helps with Sprint progress by moving the focus to completing stories and limiting the WIP. There are too many other benefits to list in a short glossary entry.
Ironically, some of the earliest programming work (before it was called programming) was done in pairs: “Betty Snyder and I, from the beginning, were a pair. And I believe that the best programs and designs are done by pairs, because you can criticise each other, and find each others errors, and use the best ideas.”
– Jean Bartik, one of the original programmers of the ENIAC computer. (source – https://martinfowler.com/articles/on-pair-programming.html)
- On Pair Programming – this is a deep article
- Pair-programming makes people share
- Two Elements of Pair Programming Skill
PAIR PROGRAMMING BOOKS
- Pair Programming: A book on problem solving – YvesHanoulle, talboomerik, and Clare Sudbery
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.