The DOI matches its Crossref record; 16 of the 16 references it cites were found in a registry or an index.
Investigating the Impact of Personality Types on Communication and Collaboration-Viability in Pair Programming – An Empirical Study
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 significant challenge of pair programming is the potential mismatch in skill levels between partners. When there is a considerable disparity in programming abilities, the collaboration may become less effective, with the more skilled student potentially dominating the process or becoming frustrated with their partner's pace (Sfetsos et al., 2006).”
From The impact of AI-assisted pair programming on student motivation, programming anxiety, collaborative learning, and programming performance: a comparative study with traditional pair programming and individual approaches (2025) · cites this paper as Sfetsos et al., 2006
Citations
Cites
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
Experimentation in Software Engineering: An Introduction
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2011) · Lund University Publications (Lund University) · Cited by 2,214
Cockburn, A. (2001) · UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno · Cited by 1,858
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000) · Kluwer international series in software engineering · doi:10.1007/978-1-4615-4625-2 · Cited by 1,775
Work teams: Applications and effectiveness.
Sundstrom, E. D., Meuse, K. P. D., & Futrell, D. (1990) · American Psychologist · doi:10.1037//0003-066x.45.2.120 · Cited by 1,593
The TAME Project: Towards Improvement-Oriented Software Environments
Basili, V. R., & Rombach, H. D. (2005) · Foundations of Empirical Software Engineering · doi:10.1007/3-540-27662-9_8 · Cited by 1,411
A Methodology for Collecting Valid Software Engineering Data
Basili, V. R., & Weiss, D. M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010301 · Cited by 1,149
Agile Software Development Ecosystems
Highsmith, J. (2002) · International Linear Collider · Cited by 874
Software Metrics. A Rigorous Approach
(1991) · Journal of Information Technology · doi:10.1177/0268396291006003-421 · Cited by 843
Practical guidelines for measurement-based process improvement
Briand, L., Differding, C. M., & Rombach, H. (1996) · Software Process: Improvement and Practice · doi:10.1002/(sici)1099-1670(199612)2:4<253::aid-spip53>3.0.co;2-g · Cited by 238
On understanding compatibility of student pair programmers
Katira, N., Williams, L. A., Wiebe, E., Miller, C., Balik, S. P., & Gehringer, E. F. (2004) · ACM SIGCSE Bulletin · doi:10.1145/1028174.971307 · Cited by 112
Briand, L., Arisholm, E., Counsell, S., Houdek, F. G., & Thévenod-Fosse, P. (1999) · Empirical Software Engineering · doi:10.1023/a:1009825923070 · Cited by 91
Communication metrics for software development
Dutoit, A. H., & Bruegge, B. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.707697 · Cited by 63
An empirical study of communication in code inspections
Seaman, C. B., & Basili, V. R. (1997) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/253228.253248 · Cited by 50
Investigating the extreme programming system–An empirical study
Sfetsos, P., Angelis, L., & Stamelos, I. G. (2006) · Empirical Software Engineering · doi:10.1007/s10664-006-6404-6 · Cited by 45
Self-citationSaeki, M. (2002) · Proceedings - Asia Pacific Software Engineering Conference/Proceedings · doi:10.1109/apsec.1995.496949 · Cited by 22
Research works printed but not linked: 5
- Cockburn, A.: The Coffee Machine Design Problem: Part 1 & 2. C/C++ User’s Journal (May/June 1998)
- Cockburn, A.: Agle Software Development. Addison-Wesley, Reading (2002)
- Highsmith, J.: Agle Software Development Ecosystems. Addison Wesley, Reading (2002)
- Keirsey, D., Bates, M.: Please Understand Me, Del Mar. Prometheus Book Company, California (1984)
- Myers, Isabel: Manual: The Myers-Briggs Type Indicator. Consulting Psychologists Press, Palo Alto (1975)
Cited by
Wei, X., Lin, L., Meng, N., Tan, W., Kong, S.-C., & Kinshuk (2021) · Computers & Education · doi:10.1016/j.compedu.2020.104023 · Cited by 241
Fan, G., Liu, D., Zhang, R., & Pan, L. (2025) · International Journal of STEM Education · doi:10.1186/s40594-025-00537-3 · Cited by 109
“When there is a considerable disparity in programming abilities, the collaboration may become less effective, with the more skilled student potentially dominating the process or becoming frustrated with their partner’s pace (Sfetsos et al., 2006).”
The role and value of replication in empirical software engineering results
Shepperd, M., Ajienka, N., & Counsell, S. (2018) · Information and Software Technology · doi:10.1016/j.infsof.2018.01.006 · Cited by 60
Metadata
- Authors
- Sfetsos, P., Stamelos, I., Angelis, L., & Deligiannis, I.
- Affiliations
- Aristotle University of Thessaloniki (GR)
- Alexander Technological Educational Institute of Thessaloniki (GR)
- Venue
- Lecture Notes in Computer Science
- Publisher
- Springer Berlin Heidelberg
- Published
- 2006
- Pages
- 43-52
- ISSN
- 0302-9743 (ISSN-L)
- 1611-3349
- OpenAlex
- W1546394965
- Cited by
- 49
- References
- 16
- Citations by year
- 2025: 2 · 2024: 1 · 2023: 1 · 2022: 2 · 2021: 2 · 2020: 2 · 2018: 1 · 2017: 2 · 2016: 2 · 2015: 4 · 2014: 1 · 2013: 5 · 2012: 6
- FWCI
- 2.56
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Lecture notes in computer science (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Psychology › Social Psychology › Team Dynamics and Performance
- Social Sciences › Psychology › Clinical Psychology › Personality Traits and Psychology
- Keywords
- pair programming, personality types, temperament, developer communication, developer satisfaction, knowledge acquisition, software productivity
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.
