The DOI matches its Crossref record; 33 of the 34 references it cites were found in a registry or an index.
Interruptions on software teams: a comparison of paired and solo programmers
Abstract
This study explores interruption patterns among software developers who program in pairs versus those who program solo. Ethnographic observations indicate that interruption length, content, type, occurrence time, and interrupter and interruptee strategies differed markedly for radically collocated pair programmers versus the programmers who primarily worked alone. After presenting an analysis of 242 interruptions drawn from more than 40 hours of observation data, we discuss how team configuration and work setting influenced how and when developers handled interruptions. We then suggest ways that CSCW systems might better support pair programming and, more broadly, provide interruption-handling support for workers in knowledge-intensive occupations.
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
“Chong and Siino [8] compared interruption patterns among paired and solo programmers. Their study indicates significant differences between the pair programmers and solo programmers in terms of the length, type, time, context and strategies for handling task interruptions.”
From Two Sides of the Same Coin (2018) · cites this paper as [8]
In the citing paper
“They proposed that as a substantial number of interruptions are self-initiated, working in pairs may have potential support for interruption handling.”
From Two Sides of the Same Coin (2018) · cites this paper as [8]
Citations
Cites
Exchange and Power in Social Life.
Bierstedt, R., & Blau, P. M. (1965) · American Sociological Review · doi:10.2307/2091154 · Cited by 13,624
Research in Organizational Behavior
Hammer, E. R., Cummings, L. L., & Staw, B. M. (1984) · The Academy of Management Review · doi:10.2307/258300 · Cited by 10,806
Hutchins, E. (1995) · doi:10.7551/mitpress/1881.001.0001 · Cited by 10,801 · cited 1×
“Speech and gesture may also provide information to the returning programmer in a more accessible and potentially more parsimonious representational state [16].”
BackgroundExtreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
Plans and Situated Actions: The Problem of Human-Machine Communication
Kantowitz, B., & Suchman, L. A. (1990) · The American Journal of Psychology · doi:10.2307/1423221 · Cited by 5,299 · cited 1×
“Much the same way that conversational partners work “moment by moment, to identify and remedy inevitable troubles that arise” in conversation [26], pair programmer interactions provide a natural and seamless means for interruption recovery.”
BackgroundThe contracts of individuals and organizations
Parks, J. M. (1993) · Cited by 1,145
The Time Famine: Toward a Sociology of Work Time
Perlow, L. A. (1999) · Administrative Science Quarterly · doi:10.2307/2667031 · Cited by 989 · cited 2×
“In Perlow’s [22] ethnography of software engineers, interruptions were also found to be critical to work, but the high volume of interruptions coupled with a lack of control over interruption incidence led workers to report high levels of stress and frustration.”
BackgroundProceedings of the 26th annual conference of the cognitive science society
Dieussaert, K., Ford, M., & Horsten, L. (2004) · Cited by 853
A diary study of task switching and interruptions
Czerwinski, M., Horvitz, E., & Wilhite, S. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985715 · Cited by 830 · cited 5×
“Czerwinski, Horvitz and Wilhite’s [10] participants reported an estimated 0.”
BackgroundInfluentialProceedings of the 16th International Conference Information Systems 2023
(2023) · doi:10.33965/is2023 · Cited by 828
Research works printed but not linked: 8
- Bailey B.P., 2001, The Proceedings of INTERACT 2001
- Beck K., 2000, Addison Wesley
- Blau P., 1964, Wiley
- Clifford J.D., 2004, Proceedings of the 26th annual conference of the Cognitive Science Society
- Hutchins E., 1995, The MIT Press
- Hutchins E., 1996, Cognition and communication at work
- 10.5465/amr.2003.10196791 · doi:10.5465/amr.2003.10196791 · Paper page
- Speier C., 1997, Proceedings of the 18th international conference on information systems
Cited by
Information Needs in Collocated Software Development Teams
Ko, A. J., DeLine, R., & Venolia, G. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.45 · Cited by 499
(2009) · doi:10.1145/1518701.1518944 · Cited by 447
“examined collaboration between programmers during solo and pair programming [6]).”
BackgroundPuranik, H., Koopman, J., & Vough, H. C. (2020) · Journal of Management · doi:10.1177/0149206319887428 · Cited by 210
“They may even time their arrival/departure from the workplace, choose specific work shifts or work locations, and manage coworker interactions and relationships to regulate exposure to interruptions (Chong & Siino, 2006).”
BackgroundThe Work Life of Developers: Activities, Switches and Perceived Productivity
Meyer, A. N., Barton, L. E., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2656886 · Cited by 170
“This 2 minute mark was chosen as a reasonable boundary based on previous research that found an average time of 2 min 11 sec being spent on any device or paper before switching [10], as well as research by Chong and Siino [26] who found that a typical interruption for one work team lasted 1 min 55 sec, and 2 min 45 se…”
BackgroundMethodInfluentialWhy do i keep interrupting myself?: environment, habit and self-interruption
Dabbish, L., Mark, G., & González, V. M. (2011) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1978942.1979405 · Cited by 132
“In-situ studies of attention in the workplace suggest that almost half of the interruptions individuals experience are self-initiated, or what is termed selfinterruption [3, 4, 5, 8].”
Background
Metadata
- Authors
- Chong, J., & Siino, R.
- Affiliations
- Stanford University (US)
- Venue
- Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
- Publisher
- ACM
- Published
- 2006-11-04
- Pages
- 29-38
- OpenAlex
- W2080787992
- Cited by
- 58
- References
- 34
- Citations by year
- 2025: 3 · 2024: 3 · 2023: 3 · 2022: 2 · 2021: 2 · 2020: 4 · 2019: 2 · 2018: 4 · 2017: 6 · 2016: 2 · 2015: 3 · 2014: 2 · 2013: 1 · 2012: 3
- FWCI
- 3.22
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- ACM Conference on Computer Supported Cooperative Work (CSCW) (publishedVersion)
- Funders
- Microsoft
- Topics
- Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
- Keywords
- interruptions, pair programming, solo programming, software developers, team structure, collocations, knowledge-intensive work, work environment
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Interruptions on software teams: a comparison of paired and solo programmers. https://app.cochat.ai/papers/10.1145/1180875.1180882
- The paper
- Chong, J., & Siino, R. (2006). Interruptions on software teams: a comparison of paired and solo programmers. Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work. https://doi.org/10.1145/1180875.1180882
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.