A Comparison of Pair Versus Solo Programming Under Different Objectives: An Analytical Approach

Authors:
Milind Dawande;Monica Johar;Subodha Kumar;Vijay S. Mookerjee
Affiliations:
School of Management and the School of Computer Science, University of Texas at Dallas, Richardson, Texas 75083;The Belk College of Business, University of North Carolina at Charlotte, Charlotte, North Carolina 28223;Michael G. Foster School of Business, University of Washington, Seattle, Washington 98195;School of Management, University of Texas at Dallas, Richardson, Texas 75083
Venue:
Information Systems Research
Year:
2008

Citing 0
Cited 6

Coevolving Systems and the Organization of Agile Software Development

Information Systems Research
The centrality of user modeling to high recall with high precision search

SMC'09 Proceedings of the 2009 IEEE international conference on Systems, Man and Cybernetics
Test-driven roles for pair programming

Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
On a labeling problem in graphs

Discrete Applied Mathematics
A Hierarchical Framework for Organizing a Software Development Process

Operations Research
Organizing knowledge workforce for specified iterative software development tasks

Decision Support Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

This study compares the performances of pair development (an approach in which a pair of developers jointly work on the same piece of code), solo development, and mixed development under two separate objectives: effort minimization and time minimization. To this end, we develop analytical models to optimize module-developer assignments in each of these approaches. These models are shown to be strongly NP-hard and solved using a genetic algorithm. The solo and pair development approaches are compared for a variety of problem instances to highlight project characteristics that favor one of the two practices. We also propose a simple criterion that can reliably recommend the appropriate approach for a given problem instance. Typically, for efficient knowledge sharing between developers or for highly connected systems, the pair programming approach is preferable. Also, the pair approach is better at leveraging expertise by pairing experts with less skilled partners. Solo programming is usually desirable if the system is large or the effort needed either to form a pair or to code efficiently in pairs is high. Solo programming is also appropriate for projects with a tight deadline, whereas the reverse is true for projects with a lenient deadline. The mixed approach (i.e., an approach where both the solo and pair practices are used in the same project) is only indicated when the system consists of groups of modules that are sufficiently different from one another.