Understanding the impact of Pair Programming on developers attention: A case study on a large industrial experimentation
Authors:
- 1 June 2012
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 02705257,p. 1094-1101
Abstract
Pair Programming is one of the most studied and debated development techniques. However, at present, we do not have a clear, objective, and quantitative understanding of the claimed benefits of such development approach. All the available studies focus on the analysis of the effects of Pair Programming (e.g., code quality, development speed, etc.) with different findings and limited replicability of the experiments. This paper adopts a different approach that could be replicated in an easier way: it investigates how Pair Programming affects the way developers write code and interact with their development machine. In particular, the paper focuses on the effects that Pair Programming has on developers' attention and productivity. The study was performed on a professional development team observed for ten months and it finds out that Pair Programming helps developers to eliminate distracting activities and to focus on productive activities.Keywords
This publication has 24 references indexed in Scilit:
- Limited Attention as a Scarce Resource in Information‐Rich EconomiesThe Economic Journal, 2008
- Interruptions on software teams2006
- An empirical comparison between pair development and software inspection in Thailand2006
- Pair programming productivity: Novice–novice vs. expert–expertInternational Journal of Human-Computer Studies, 2006
- Effects of pair programming at the development team level: an experiment2005
- Are Reviews an Alternative to Pair Programming?Empirical Software Engineering, 2004
- When Does a Pair Outperform Two Individuals?2003
- Behavioural and ecological consequences of limited attentionPhilosophical Transactions of the Royal Society B: Biological Sciences, 2002
- Strengthening the case for pair programmingIEEE Software, 2000
- The case for collaborative programmingCommunications of the ACM, 1998