Liberating pair programming research from the oppressive driver/observer regime
- 1 May 2013
- conference paper
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE) in 2013 35th International Conference on Software Engineering (ICSE)
- p. 1201-1204
- https://doi.org/10.1109/icse.2013.6606678
Abstract
The classical definition of pair programming (PP) describes it via two obvious roles: driver (the person currently having the keyboard) and observer (the other, alternatively called navigator). Although prior research has found some assumptions regarding these roles to be false, so far no alternative PP role model took hold. Instead, most PP research tacitly assumes the classical model to be true and thus PP to be no more difficult than solo programming. We perform qualitative research (using Grounded Theory Methodology) to find a more realistic role model, and have uncovered a suprising complexity: There are more than two roles, they are assumed and unassumed gradually, multiple roles can be held by one person at the same time, and some of their facets are subtle. Mastering this complexity requires specific PP skills beyond mere programming and communication skills. By ignoring such skills, previous PP studies (in particular the controlled experiments) have investigated a rather mixed bag of situations, which explains their heterogeneous results. The emerging result is that qualitative research on the PP process will lead to constructive behavioral advice (process patterns) for pair members and to more meaningful designs for quantitative PP research.Keywords
This publication has 6 references indexed in Scilit:
- The effectiveness of pair programming: A meta-analysisInformation and Software Technology, 2009
- Pair programming and the mysterious role of the navigatorInternational Journal of Human-Computer Studies, 2008
- Program quality with pair programming in CS1Published by Association for Computing Machinery (ACM) ,2004
- The impact of pair programming on student performance, perception and persistencePublished by Institute of Electrical and Electronics Engineers (IEEE) ,2003
- Strengthening the case for pair programmingIEEE Software, 2000
- The case for collaborative programmingCommunications of the ACM, 1998