Student or educator? Sign up with your school email and get 6 months of Pro free.

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

Abad, Zahra Shakeri Hossein, Noaeen, Mohammad, Zowghi, Didar, Far, Behrouz H., Barker, Ken · 2018 · Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018

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

Crossref · 10.1145/3210459.3214170

Cites

16 of 16 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Flow Change Flow Change Figure 1: Clarification of the concepts of "task switching", "problem state" and "goal memory". ©Shakeri H.A et al.
Flow Change Flow Change Figure 1: Clarification of the concepts of "task switching", "problem state" and "goal memory". ©Shakeri H.A et al.From the PDF
Image 2
From the PDF
Figure 3 RQ1- Perceived consequences of task interruption
Figure 3 RQ1- Perceived consequences of task interruptionFrom the PDF
Image 4
From the PDF
len len Figure 5: Coding frequency for open-ended question about the most disruptive interruption
len len Figure 5: Coding frequency for open-ended question about the most disruptive interruptionFrom the PDF
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.
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.From the PDF

Verification

Claims the paper makes

1 Valid · 0 Not valid · 16 Not checked · 67 Own results and interpretations

37 more claims

Create a free account to see all 84 claims and every source verdict.

See all claims — free account
  • Probably not a substantial claim. 34
  • It may state two separate claims as one. 14
  • The quote only partly states this claim. 1

Create a free account to see these claims.

Citations

Cites

Show all 13 references

Research works printed but not linked: 3

  1. 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.
  2. Graham R Gibbs . 2002. Qualitative data analysis: Explorations with NVivo . Open University . Graham R Gibbs. 2002. Qualitative data analysis: Explorations with NVivo. Open University.
  3. 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

See all 13

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.