Extreme programming explained: embrace change
Extreme programming explained: embrace change
Test Driven Development: By Example
Test Driven Development: By Example
Strengthening the Case for Pair Programming
IEEE Software
Reducing wasted development time via continuous testing
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
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
Two controlled experiments concerning the comparison of pair programming to peer review
Journal of Systems and Software
The Social Dynamics of Pair Programming
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Video analysis of pair programming
Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
Pair programming and the mysterious role of the navigator
International Journal of Human-Computer Studies
Crystal clear a human-powered methodology for small teams
Crystal clear a human-powered methodology for small teams
A Comparison of Pair Versus Solo Programming Under Different Objectives: An Analytical Approach
Information Systems Research
Safe-commit analysis to facilitate team software development
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
JUnitMX - A change-aware unit testing tool
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Distributed side-by-side programming
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Hi-index | 0.00 |
The driver/navigator model of pair programming needs to be revised. We propose a model of programming in pairs where roles are based on test-driven development. Each programmer uses a different view of a shared development environment. One member of the pair writes tests, while the other implements the system. The programmers can cooperate as needed and move between different collaboration modalities. As part of a user-centered design process, we built a prototype web-based collaborative development environment for test-driven pair programming and ran a user study with professional software developers to evaluate the idea and identify research challenges. We used existing vocabularies and developed two novel visualizations to analyze the data, and found that the approach is feasible.