"How Was Your Weekend?" Software Development Teams Working From Home During COVID-19
Open accessThe DOI matches its Crossref record; 12 of the 12 references it cites were found in a registry or an index.
Abstract
The mass shift to working at home during the COVID-19 pandemic radically changed the way many software development teams collaborate and communicate. To investigate how team culture and team productivity may also have been affected, we conducted two surveys at a large software company. The first, an exploratory survey during the early months of the pandemic with 2,265 developer responses, revealed that many developers faced challenges reaching milestones and that their team productivity had changed. We also found through qualitative analysis that important team culture factors such as communication and social connection had been affected. For example, the simple phrase "How was your weekend?" had become a subtle way to show peer support. In our second survey, we conducted a quantitative analysis of the team cultural factors that emerged from our first survey to understand the prevalence of the reported changes. From 608 developer responses, we found that 74% of these respondents missed social interactions with colleagues and 51% reported a decrease in their communication ease with colleagues. We used data from the second survey to build a regression model to identify important team culture factors for modeling team productivity. We found that the ability to brainstorm with colleagues, difficulty communicating with colleagues, and satisfaction with interactions from social activities are important factors that are associated with how developers report their software development team's productivity. Our findings inform how managers and leaders in large software companies can support sustained team productivity during times of crisis and beyond.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Five misunderstandings about case-study research
Flyvbjerg, B. (2006) · Qualitative Inquiry · doi:10.1177/1077800405284363 · Cited by 14,266
Qualitative Content Analysis in Practice
Schreier, M. (2012) · doi:10.4135/9781529682571 · Cited by 5,801
Likert scales, levels of measurement, and the “laws” of statistics
Norman, G. (2010) · Advances in Health Sciences Education · doi:10.1007/s10459-010-9222-y · Cited by 4,850
Analyzing and Interpreting Data From Likert-Type Scales
Sullivan, G. M., & Artino, A. R. (2013) · Journal of Graduate Medical Education · doi:10.4300/jgme-5-4-18 · Cited by 3,044
Early predictors of job burnout and engagement.
Maslach, C., & Leiter, M. P. (2008) · Journal of Applied Psychology · doi:10.1037/0021-9010.93.3.498 · Cited by 2,397
Mechanisms to improve labor productivity by performing telework.
Kazekami, S. (2020) · Telecommunications Policy · doi:10.1016/j.telpol.2019.101868 · Cited by 375 · cited 1×
“Kazekami found that when remote work hours are too long, worker productivity is reduced [45].”
The 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
Self-citationToday was a good day: The daily life of software developers
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2904957 · Cited by 123
Self-citationWhat Predicts Software Developers’ Productivity?
Murphy-Hill, E., Jaspan, C., Sadowski, C., Shepherd, D., Phillips, M., Winter, C., Knight, A., Smith, E., & Jorde, M. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2900308 · Cited by 100 · cited 3×
“While there are advantages and disadvantages to selecting self-reported measures of productivity versus automated technical ones, our choice aligns similar recent work [7], [12], [28].”
Towards a Theory of Software Developer Job Satisfaction and Perceived Productivity
Storey, M.-A., Zimmermann, T., Bird, C., Czerwonka, J., Murphy, B., & Kalliamvakou, E. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2944354 · Cited by 90
Self-citation
Cited by
Work-from-home is here to stay: Call for flexibility in post-pandemic work policies
Smite, D., Moe, N. B., Hildrum, J., Gonzalez-Huerta, J., & Mendez, D. (2023) · Journal of Systems and Software · doi:10.1016/j.jss.2022.111552 · Cited by 271
Das, M., Tang, J., Ringland, K. E., & Piper, A. M. (2021) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3449282 · Cited by 142
An Actionable Framework for Understanding and Improving Developer Experience
Greiler, M., Storey, M.-A., & Noda, A. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3175660 · Cited by 57
Self-citationTeam Creativity in a Hybrid Software Development World: Eight Approaches
Jackson, V., Prikladnicki, R., van der Hoek, A., & Marshall, L. (2023) · IEEE Software · doi:10.1109/ms.2022.3229353 · Cited by 9
Metadata
- Authors
- Miller, C., Rodeghero, P., Storey, M.-A., Ford, D., & Zimmermann, T.
- Venue
- 2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2021-05
- Pages
- 624-636
- OpenAlex
- W3121714971
- Cited by
- 126
- References
- 12
- FWCI
- 23.62
- Type
- conference paper
- Language
- en
- Open access
- green
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: "How Was Your Weekend?" Software Development Teams Working From Home During COVID-19. https://app.cochat.ai/papers/10.1109/icse43902.2021.00064
- The paper
- Miller, C., Rodeghero, P., Storey, M.-A., Ford, D., & Zimmermann, T. (2021). "How Was Your Weekend?" Software Development Teams Working From Home During COVID-19. 2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE). https://doi.org/10.1109/icse43902.2021.00064
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.