Awareness and coordination in shared workspaces
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
Case study: extreme programming in a university environment
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Pair Programming Illuminated
Strengthening the Case for Pair Programming
IEEE Software
Tracking Test First Pair Programming - An Experiment
Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods - XP/Agile Universe 2002
Toward Measuring and Maintaining the Zone of Proximal Development in Adaptive Instructional Systems
ITS '02 Proceedings of the 6th International Conference on Intelligent Tutoring Systems
Exploring Extreme Programming in Context: An Industrial Case Study
ADC '04 Proceedings of the Agile Development Conference
Double Trouble: Mixing Qualitative and Quantitative Methods in the Study of eXtreme Programmers
VLHCC '04 Proceedings of the 2004 IEEE Symposium on Visual Languages - Human Centric Computing
Activity Patterns of Pair Programming
HICSS '05 Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences (HICSS'05) - Track 3 - Volume 03
A multiple case study on the impact of pair programming on product quality
Proceedings of the 27th international conference on Software engineering
The Social Dynamics of Pair Programming
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Exploring mutual engagement in creative collaborations
Proceedings of the 6th ACM SIGCHI conference on Creativity & cognition
Experiences of Using Pair Programming in an Agile Project
HICSS '07 Proceedings of the 40th Annual Hawaii International Conference on System Sciences
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
IEEE Transactions on Software Engineering
Perceived Effects of Pair Programming in an Industrial Context
EUROMICRO '07 Proceedings of the 33rd EUROMICRO Conference on Software Engineering and Advanced Applications
Pair programming and the mysterious role of the navigator
International Journal of Human-Computer Studies
Pair programming: what's in it for me?
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
The effectiveness of pair programming: A meta-analysis
Information and Software Technology
Exploring foundations for computer-supported collaborative learning
CSCL '02 Proceedings of the Conference on Computer Support for Collaborative Learning: Foundations for a CSCL Community
Personality and the nature of collaboration in pair programming
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
How Pair Programming Really Works
IEEE Software
Effects of Personality on Pair Programming
IEEE Transactions on Software Engineering
The collaborative nature of pair programming
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
Investigating Equity of Participation in Pair Programming
AGILEINDIA '12 Proceedings of the 2012 Agile India
Collaborative learning and anxiety: a phenomenographic study of collaborative learning activities
Proceeding of the 44th ACM technical symposium on Computer science education
Hi-index | 0.00 |
Pair Programming (PP) requires close collaboration and mutual engagement. Most existing empirical studies of PP do not focus on developers’ behaviour during PP sessions, and focus instead on the effects of PP such as productivity. However, disengagement, where a developer is not focusing on solving the task or understanding the problem and allows their partner to work by themselves, can hinder collaboration between developers and have a negative effect on their performance. This paper reports on an empirical study that investigates disengagement. Twenty-one industrial pair programming sessions were video and audio recorded and qualitatively analysed to investigate circumstances that lead to disengagement. We identified five reasons for disengagement: interruptions during the collaboration, the way the work is divided, the simplicity of the task involved, social pressure on inexperienced pair programmers, and time pressure. Our findings suggest that disengagement is sometimes acceptable and agreed upon between the developers in order to speed up problem solving. However, we also found episodes of disengagement where developers “drop out” of their PP sessions and are not able to follow their partner’s work nor contribute to the task at hand, thus losing the expected benefits of pairing. Analysis of sessions conducted under similar circumstances but where mutual engagement was sustained identified three behaviours that help to maintain engagement: encouraging the novice to drive, verbalisation and feedback, and asking for clarification.