The DOI matches its Crossref record, with a small difference in title or year; 16 of the 16 references it cites were found in a registry or an index; 2 of the 21 sources its claims cite were checked for support.
Two Sides of the Same Coin
Abstract
In the constantly evolving world of software development, switching back and forth between tasks has become the norm. While task switching often allows developers to perform tasks effectively and may increase creativity via the flexible pathway, there are also consequences to frequent task-switching. For high-momentum tasks like software development, "flow", the highly productive state of concentration, is paramount. Each switch distracts the developers' flow, requiring them to switch mental state and an additional immersion period to get back into the flow. However, the wasted time due to time fragmentation caused by task switching is largely invisible and unnoticed by developers and managers. We conducted a survey with 141 software developers to investigate their perceptions of differences between task switching and task interruption and to explore whether they perceive task switchings as disruptive as interruptions. We found that practitioners perceive considerable similarities between the disruptiveness of task switching (either planned or unplanned) and random interruptions. The high level of cognitive cost and low performance are the main consequences of task switching articulated by our respondents. Our findings broaden the understanding of flow change among software practitioners in terms of the characteristics and categories of disruptive switches as well as the consequences of interruptions caused by daily meetings.
Overview
CoChat Summary
## TL;DR
The paper reports a survey of 141 professional software developers and finds that most see task switching as similarly disruptive to task interruption, mainly because of cognitive cost and reduced performance. It also finds that daily stand-up meetings are often perceived as disruptive, though many respondents prefer scheduling them in the morning before focused work begins.
## Key findings
- 141 valid responses were collected from 10 countries; respondents were 80% male, and the average professional software development experience was 10.9 years.
- On task interruption, 80 (57%) said it is anything that breaks their flow of thought, and 97% agreed that interruptions require extra time to regain focus; 95% agreed they need extra time to complete the task, and 91% agreed they lose track of their work.
- On task switching, 115 (81%) participants answered that task switching is a type of interruption; 83 (59%) cited cognitive cost and 51 (36%) cited low performance as reasons.
- For daily stand-up meetings, 64 (45%) said switching to them has a negative or very negative impact on primary-task performance, while 32 (23%) said the impact is positive and 45 (31%) said it has no impact; 100 (71%) thought morning meetings are least disruptive.
## Methods
- The study used an online survey with 15 questions (multiple choice, Likert scale, and open-ended items) sent to professional software developers at eight software development companies.
- The final sample was 141 valid answers from 10 countries; the paper reports company size, gender, job roles, and years of experience for the respondents.
- Open-ended responses were analyzed with grounded theory coding (open, axial, selective coding) in NVivo; survey associations were examined with Spearman’s rank test, and response distributions were compared with kernel density plots plus skew/kurtosis.
## Limitations
- The paper does not state explicit study limitations in the provided text.
- Evident from the text: the data are self-reported survey perceptions from a convenience sample of developers at eight companies, so the findings reflect reported perceptions rather than measured performance or causal effects.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Figures





![Figure 6 Answers to question: 'On a typical working day, how often you switch your software development tasks?' [1]: Less than every 10 minutes, [2]: Every 10-30 minutes, [3]: Every 30-60 minutes, [4]: Every 1-2 hours, [5]: Every 2-4 hours, [6]: Others.](/paper-figures/4b44930e413e4f93b7fe4af5ba569ab2/two-sides-of-the-same-coin-figure-6.png)
Verification
Claims the paper makes
1 Valid · 0 Not valid · 16 Not checked · 67 Own results and interpretations
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“83 (59%) of the participants stated that task switchings, no matter if they are planned or ad-hoc, are a type of interruption because they cause an extra cognitive load”
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Switching to a different task with a different context (context switching) and averting attention to another task (new task) are the next most frequent characteristics we noted for task interruption (context switching: 36 [26%]; new task: 25 [18%])”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“We found that practitioners perceive considerable similarities between the disruptiveness of task switching (either planned or unplanned) and random interruptions.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Extra memory load was perceived by 25 (18%) of the respondents as a source of cognitive cost which makes task switchings as disruptive as task interruptions”
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Of 141 responses to the statement 'A disruptive task interruption negatively impacts my performance after resuming the primary task by ...', 97% agreed or strongly agreed that 'the need for extra time to regain the focus', 95% that 'the need for extra time to complete the task', and 91% that 'losing the track of work' are the consequences of interruptions on their performance (Figure 3).”
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
37 more claims
Create a free account to see all 84 claims and every source verdict.
- Probably not a substantial claim. 34
- It may state two separate claims as one. 14
- The quote only partly states this claim. 1
Citations
Cites
On optimal and data-based histograms
SCOTT, D. W. (1979) · Biometrika · doi:10.1093/biomet/66.3.605 · Cited by 1,819 · cited 1×
“tion by Kitchenham et al. [12], to compare the distribution of responses between different categories of respondents, we used kernel density plot instead of boxplots and used Skew and Kurtosis scores [15] to interpret these plots. 4 RESULTS AND DISCUSSION In this section, we detail and discuss the results of our inves…”
MethodInfluentialMemory for goals: an activation‐based model
Altmann, E. M., & Trafton, J. G. (2002) · Cognitive Science · doi:10.1207/s15516709cog2601_2 · Cited by 795
Chisholm, C. D., Collison, E. K., Nelson, D. R., & Cordell, W. H. (2000) · Academic Emergency Medicine · doi:10.1111/j.1553-2712.2000.tb00469.x · Cited by 610
Robust Statistical Methods for Empirical Software Engineering
Kitchenham, B., Madeyski, L., Budgen, D., Keung, J., Brereton, P., Charters, S., Gibbs, S., & Pohthong, A. (2017) · Empirical Software Engineering · doi:10.1007/s10664-016-9437-5 · Cited by 257 · cited 1×
“[12], to compare the distribution of responses between different categories of respondents, we used kernel density plot instead of boxplots and used Skew and Kurtosis scores [15] to interpret these plots.”
MethodUsing grounded theory to study the experience of software development
Adolph, S., Hall, W., & Kruchten, P. (2011) · Empirical Software Engineering · doi:10.1007/s10664-010-9152-6 · Cited by 235 · cited 2×
“question: “On a typical working day, how often you switch your software development tasks?” [1]: Less than every 10 minutes, [2]: Every 10-30 minutes, [3]: Every 30-60 minutes, [4]: Every 1-2 hours, [5]: Every 2-4 hours, [6]: Others. whereadeveloperjustinitiatedatask)todelayreceiving/addressing notifications, as state…”
BackgroundMethodInfluentialThe daily stand-up meeting: A grounded theory study
Stray, V., Sjøberg, D. I. K., & Dybå, T. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2016.01.004 · Cited by 139
Interrupts: just a minute never is
van Solingen, R., Berghout, E., & van Latum, F. (1998) · IEEE Software · doi:10.1109/52.714843 · Cited by 104 · cited 2×
“real work" in 2-hour blocks and anything less will just be "busy work" like responding to emails and helping others”. This is consistent with what Stray et al. [16] and Solingen et al. [10] found: developers found the time of daily meetings disruptive (as it results in an undesirable long resumption lag…”
ResultResumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103 · cited 2×
“Participants of this study described the interrelationships and dependencies between projects as the most common reason for their task switchings. Regarding resumption strategies, Parnin and Rugaber [13] conducted an analysis on 86 programmers to understand the various strategies and coping mechanisms that developers…”
BackgroundMethodThe sky is not the limit: multitasking across GitHub projects
Vasilescu, B., Blincoe, K., Xuan, Q., Casalnuovo, C., Damian, D., Devanbu, P., & Filkov, V. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884875 · Cited by 77 · cited 1×
“[18] studied the effects of task switchings on developers’ productivity.”
BackgroundInterruptions on software teams: a comparison of paired and solo programmers
Chong, J., & Siino, R. (2006) · Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work · doi:10.1145/1180875.1180882 · Cited by 58 · cited 1×
“Chong and Siino [8] compared interruption patterns among paired and solo programmers.”
Background
Research works printed but not linked: 3
- Tom DeMarco and Tim Lister . 2013 . Peopleware: Productive Projects and Teams . Addison-Wesley . Tom DeMarco and Tim Lister. 2013. Peopleware: Productive Projects and Teams. Addison-Wesley.
- Graham R Gibbs . 2002. Qualitative data analysis: Explorations with NVivo . Open University . Graham R Gibbs. 2002. Qualitative data analysis: Explorations with NVivo. Open University.
- Dario D Salvucci and Niels A Taatgen . 2010. The multitasking mind . Oxford University Press . Dario D Salvucci and Niels A Taatgen. 2010. The multitasking mind. Oxford University Press.
Cited by
Abad, Z. S. H., Karras, O., Schneider, K., Barker, K., & Bauer, M. (2018) · Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018 · doi:10.1145/3210459.3210471 · Cited by 32
“[2] Zahra Shakeri Hossein Abad, Guenther Ruhe, and Mike Bauer.”
BackgroundSelf-citationAssessing the Risk of Software Development in Agile Methodologies Using Simulation
Lunesu, M. I., Tonelli, R., Marchesi, L., & Marchesi, M. (2021) · IEEE Access · doi:10.1109/access.2021.3115941 · Cited by 44
Supporting Analysts by Dynamic Extraction and Classification of Requirements-Related Knowledge
Abad, Z. S. H., Gervasi, V., Zowghi, D., & Far, B. (2019) · International Conference on Software Engineering · doi:10.1109/icse.2019.00057 · Cited by 18
“Moreover, the proposed approach can assist analysts to manage the issues of memory recall [78]– [80] after resuming an interrupted elicitation task.”
BackgroundSelf-citationBreaking the Flow: A Study of Interruptions During Software Engineering Activities
Ma, Y., Huang, Y., & Leach, K. (2024) · Proceedings of the IEEE/ACM 46th International Conference on Software Engineering · doi:10.1145/3597503.3639079 · Cited by 12
Flow Experience in Software Engineering
Ritonummi, S., Siitonen, V., Salo, M., Pirkkalainen, H., & Sivunen, A. E. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616263 · Cited by 13
“…of developers’ productivity have found that developers tend to feel productive when they have attainable, clearly defined goals or requirements and the possibility of working without excessive distractions, interruptions, or context switches, which can help reach flow (e.g., [15][61][62][63][64]).”
Background
Metadata
- Authors
- Abad, Z. S. H., Noaeen, M., Zowghi, D., Far, B. H., & Barker, K.
- Affiliations
- University of Calgary (CA)
- University of Technology Sydney (AU)
- Venue
- Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018
- Publisher
- ACM
- Published
- 2018-06-28
- Pages
- 175-180
- OpenAlex
- W7214196441
- Cited by
- 0
- References
- 13
- FWCI
- 0.00
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- International Conference on Evaluation and Assessment in Software Engineering (EASE) (publishedVersion)
- 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
- Social Sciences › Psychology › Developmental and Educational Psychology › Flow Experience in Various Fields
- Keywords
- task switching, task interruption, flow experience, software developers, cognitive cost, time fragmentation, developer productivity, developer perceptions
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.
A language model drew the claims from the paper on 2026-09-30, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-09-30 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
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: Two Sides of the Same Coin. https://app.cochat.ai/papers/10.1145/3210459.3214170
- The paper
- Abad, Z. S. H., Noaeen, M., Zowghi, D., Far, B. H., & Barker, K. (2018). Two Sides of the Same Coin. Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018. https://doi.org/10.1145/3210459.3214170
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.