ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Evaluating the effectiveness of VOSDM: a vision oriented approach
ACM SIGSOFT Software Engineering Notes
Disengagement in pair programming: does it matter?
Proceedings of the 34th International Conference on Software Engineering
Proceedings of the 34th International Conference on Software Engineering
DroidSense: a mobile tool to analyze software development processes by measuring team proximity
TOOLS'12 Proceedings of the 50th international conference on Objects, Models, Components, Patterns
| Hi-index | 0.00 |
The interest in pair programming (PP) has increased recently, e.g. by the popularization of agile software development. However, many practicalities of PP are poorly understood. We present experiences of using PP extensively in an industrial project. The fact that the team had a limited number of high-end workstations forced it in a positive way to quick deployment and rigorous use of PP. The developers liked PP and learned it easily. Initially, the pairs were not rotated frequently but adopting daily, random rotation improved the situation. Frequent rotation seemed to improve knowledge transfer. The driver/navigator roles were switched seldom, but still the partners communicated actively. The navigator rarely spotted defects during coding, but the released code contained almost no defects. Test-driven development and design in pairs possibly decreased defects. The developers considered that PP improved quality and knowledge transfer, and was better suited for complex tasks than for easy tasks.