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

Milind Dawande (), Monica Johar (), Subodha Kumar () and Vijay S. Mookerjee ()
Additional contact information
Milind Dawande: School of Management and the School of Computer Science, University of Texas at Dallas, Richardson, Texas 75083
Monica Johar: The Belk College of Business, University of North Carolina at Charlotte, Charlotte, North Carolina 28223
Subodha Kumar: Michael G. Foster School of Business, University of Washington, Seattle, Washington 98195
Vijay S. Mookerjee: School of Management, University of Texas at Dallas, Richardson, Texas 75083

Information Systems Research, 2008, vol. 19, issue 1, 71-92

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.

Keywords: extreme programming; software development methodology; pair programming; integer programming; genetic algorithms; heuristics (search for similar items in EconPapers)
Date: 2008
References: View references in EconPapers View complete reference list from CitEc
Citations: View citations in EconPapers (9)

Downloads: (external link)
http://dx.doi.org/10.1287/isre.1070.0147 (application/pdf)

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:inm:orisre:v:19:y:2008:i:1:p:71-92

Access Statistics for this article

More articles in Information Systems Research from INFORMS Contact information at EDIRC.
Bibliographic data for series maintained by Chris Asher ().