The DOI matches its Crossref record; 9 of the 11 references it cites were found in a registry or an index.
Are Reviews an Alternative to Pair Programming?
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“One of the primary advantages of pair programming is its positive impact on code quality. Collaboration in real-time allows for immediate error detection and correction, leading to fewer defects and improved overall code structure (Müller, 2004).”
Citations
Cites
Statistical power analysis for the behavioral sciences
(1990) · Computers, Environment and Urban Systems · doi:10.1016/0198-9715(90)90050-4 · Cited by 65,269
Gentleman R: R: A language for data analysis and graphics
Ihaka, R., & Gentleman, R. (1996) · Journal of Computational and Graphical Statistics · doi:10.1080/10618600.1996.10474713 · Cited by 11,747
A discipline for software engineering
(1995) · Control Engineering Practice · doi:10.1016/0967-0661(95)90062-4 · Cited by 1,018
Strengthening the case for pair programming
Williams, L. A., Kessler, R. R., Cunningham, W., & Jeffries, R. (2000) · IEEE Software · doi:10.1109/52.854064 · Cited by 779
Gilb, T., Graham, D., & Finzi, S. (1993) · Cited by 515
The costs and benefits of pair programming
Cockburn, A., & Williams, L. A. (2001) · Cited by 425
The case for collaborative programming
Nosek, J. T. (1998) · Communications of the ACM · doi:10.1145/272287.272333 · Cited by 375
The effects of pair-programming on performance in an introductory programming course
McDowell, C., Werner, L., Bullock, H. E., & Fernald, J. L. (2002) · ACM Technical Symposium on Computer Science Education (SIGCSE) · doi:10.1145/563340.563353 · Cited by 353
The effects of "pair-pressure" and "pair-learning" on software engineering education
Williams, L. A., & Kessler, R. R. (2005) · IEEE International Conference on Software Engineering Education and Training (CSEE&T) · doi:10.1109/csee.2000.827023 · Cited by 112
Research works printed but not linked: 1
- Müller, M., and Padberg, F. 2002. Extreme programming from an engineering economics point of view. In International Workshop on Economics-Driven Software Engineering Research (EDSER). Orlando, Florida, USA, May.
Cited by
Salleh, N., Mendes, E., & Grundy, J. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.59 · Cited by 367
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
Arisholm, E., Gallis, H., Dybå, T., & Sjøberg, D. I. K. (2007) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.17 · Cited by 277
A multiple case study on the impact of pair programming on product quality
Hulkko, H., & Abrahamsson, P. (2005) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1062455.1062545 · Cited by 155
Measuring and modeling programming experience
Siegmund, J., Kästner, C., Liebig, J., Apel, S., & Hanenberg, S. (2013) · Empirical Software Engineering · doi:10.1007/s10664-013-9286-4 · Cited by 147
Pair programming productivity: Novice–novice vs. expert–expert
Lui, K. M., & Chan, K. C. C. (2006) · International Journal of Human-Computer Studies · doi:10.1016/j.ijhcs.2006.04.010 · Cited by 133
Metadata
- Authors
- Müller, M. M.
- Affiliations
- Karlsruhe Institute of Technology (DE)
- Corresponding author
- Müller, Matthias M.
- ORCID
- Müller, Matthias M.
- Venue
- Empirical Software Engineering
- Published
- 2004-12
- Volume
- 9
- Issue
- 4
- Pages
- 335-351
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W2018982342
- Cited by
- 61
- References
- 11
- Citations by year
- 2025: 2 · 2024: 1 · 2021: 3 · 2019: 4 · 2015: 7 · 2014: 1 · 2013: 5 · 2012: 6
- FWCI
- 17.55
- Type
- journal article
- Language
- en
- Open access
- closed
- Licence
- Locations
- Empirical Software Engineering (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
- Keywords
- code review, pair programming, Extreme Programming, software development costs, code quality, software development process
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.
