References
- Aiken J. Technical and human perspectives on pair programming. ACM SIGSOFT Software Eng Notes. 2004;29(5):1–14.
- Arisholm E, Gallis H, Dyba T, et al. Evaluating pair programming with respect to system complexity and programmer expertise. IEEE Trans Software Eng. 2007;33(2):65–86.
- Balijepally V, Mahapatra R, Nerur S, et al. Are two heads better than one for software development? The productivity paradox of pair programming. MIS Q. 2009;33(1):91–118.
- Boehm BW. Software engineering economics. IEEE Trans Software Eng. 1981;10(1):4–20.
- Boehm BW, Madachy R, Steece B. Software cost estimation with Cocomo II with CD-ROM. Prentice Hall PTR; 2000.
- Coman ID, Robillard PN, Sillitti A, et al. Cooperation, collaboration and pair-programming: field studies on backup behavior. J Syst Software. 2004;91:124–134.
- Copeland L. Extreme programming; 2001. Available from: http://www.computerworld.com/s/article/66192/Extreme_Programming?taxonomyId=63&pageNumber=1
- Copeland L. Programming Gets Extreme, Development Method Takes Off, but Not in U.S. 2001. Available from: http://www.computerworld.com/s/article/59388/Programming_gets_extreme
- Dawande M, Johar M, Kumar S, et al. A comparison of pair versus solo programming under different objectives: an analytical approach. Inf Syst Res. 2008;19(1):71–92.
- di Bella E, Fronza I, Phaphoom N, et al. Pair programming and software defects -a large, industrial case study. IEEE Trans Software Eng. 2013;39(7):930–953.
- Erdogmus H. Comparative evaluation of software development strategies based on net present value. In: International Workshop on Economics-Driven Software Engineering Research EDSER; 1999.
- Erdogmus H, Williams L. The economics of software development by pair programmers. Eng Econ. 2003;48(4):283–319.
- Luck G. Subclassing XP: breaking its rules the right way. In: Agile development conference. Washington DC: IEEE Computer Society; 2004.
- Müller MM. A preliminary study on the impact of a pair design phase on pair programming and solo programming. Inf Software Technol. 2006;48(5):335–344.
- Nelson EA. Management handbook for the estimation of computer programming costs (AD-A648750). Santa Monica (CA): System Development Corporation; 1967.
- Porter L, Guzdial M, McDowell C, et al. Success in introductory programming: what works? Commun ACM. 2013;56(8):34–36.
- Padberg F, Müller MM. Analyzing the cost and benefit of pair programming. In: Proceedings of the Ninth International Software Metrics Symposium. IEEE; 2003.
- Putnam LH. A general empirical solution to the macro software sizing and estimating problem. IEEE Trans Software Eng. 1978;4(4):345–361.
- Radding A. Extremely agile programming. 2002. Available from: http://www.computerworld.com/s/article/print/67950/Extremely_Agile_Programming
- Rosenberg D, Stephens M. Extreme programming refactored: the case against XP. New York: Apress; 2003.
- Sillitti A, Succi G, Vlasenko J. Understanding the impact of pair programming on developer’s attention: a case study on a large industrial experimentation. In: Proceedings of the 34th International Conference on Software Engineering; 2012. p. 1094–1101.
- Sun W, Marakas G, Aguirre-Urreta M. Effectiveness of pair programming: perceptions of software professionals. IEEE Software. 2016;33(4):72–79.
- Wolverton RW. The cost of developing large-scale software. IEEE Trans Comput. 1974;100(6):615–636.