Reviewing Literature on Time Pressure in Software Engineering and Related Professions - Computer Assisted Interdisciplinary Literature Review

During the past years, psychological diseases related to unhealthy work environments, such as burnouts, have drawn more and more public attention. One of the known causes of these affective problems is time pressure. In order to form a theoretical background for time pressure detection in software repositories, this paper combines interdisciplinary knowledge by analyzing 1270 papers found on Scopus database and containing terms related to time pressure. By clustering those papers based on their abstract, we show that time pressure has been widely studied across different fields, but relatively little in software engineering. From a literature review of the most relevant papers, we infer a list of testable hypotheses that we want to verify in future studies in order to assess the impact of time pressures on software developers mental health.

💡 Research Summary

The paper addresses the growing concern over psychological disorders such as burnout that are linked to unhealthy work environments, focusing specifically on time pressure as a key driver. Its primary goal is to build a theoretical foundation for detecting time pressure in software development repositories by drawing on interdisciplinary literature.

To achieve this, the authors performed a large‑scale literature search on Scopus using a comprehensive set of keywords (e.g., “time pressure”, “schedule pressure”, “deadline pressure”, “speed‑accuracy tradeoff”). The initial query returned 1,378 records; after manual and automated cleaning—removing irrelevant topics such as thermodynamics and space‑time studies—the final corpus comprised 1,270 papers. Each record included title, abstract, and citation data.

The corpus was then subjected to topic modeling. Using the R package topicmodels, the authors applied Latent Dirichlet Allocation (LDA) with Gibbs sampling. Model selection based on log‑likelihood indicated that 79 topics provided the best fit. These topics were qualitatively coded into nine high‑level categories: Safety, Workplace, Solutions/Tasks, Commerce, Communication/Organization, Mind/Brain, Measures, Demographics, and Health/Medical. A single paper could belong to multiple categories.

Within the “Workplace” umbrella, sub‑categories such as Occupations and Wellbeing were identified. The “Software Engineering” topic emerged with the five most probable words “software”, “engineering”, “technical”, “testing”, and “developers”. Although 21 papers were assigned to this cluster, the terms “time” and “pressure” appeared with relatively low frequency, indicating that time‑pressure research is scarce in software engineering compared with other domains. Most of these papers treat time pressure as a peripheral factor rather than the main focus; however, a notable subset (six papers) examined testing and code quality, suggesting that time pressure may be especially salient in those phases.

The authors also reviewed literature from other fields that have extensively studied time pressure. Key theoretical frameworks include:

1. Yerkes‑Dodson Law – a U‑shaped relationship between arousal (induced by time pressure) and performance.
2. Job Demands‑Resources (JDR) Model – posits that strain arises when job demands (e.g., tight schedules) exceed available resources.
3. Speed‑Accuracy Trade‑off – faster decisions tend to be less accurate, a phenomenon observed across many tasks.

Empirical findings from auditing, project management, healthcare, and transportation consistently show that high time pressure reduces quality, increases errors, and can impair ethical decision‑making. For example, audit studies report a negative link between “time‑budget pressure” and audit quality, while some experiments fail to replicate the full Yerkes‑Dodson curve, highlighting context‑dependence. Project‑management simulations reveal that early‑stage urgency drives narrow focus on technical solutions and heightened emotional responses. In healthcare, physicians under higher organizational pressure report lower job satisfaction and higher turnover intentions.

Based on this interdisciplinary evidence, the paper proposes five testable hypotheses tailored to software development:

1. U‑shaped effort relationship – both excessive and insufficient schedule/budget pressure will reduce development effort, mirroring Yerkes‑Dodson.
2. Sprint‑level deadlines – weekly agile ceremonies act as micro‑deadlines that boost motivation but also increase strain.
3. Testing vulnerability – time pressure during testing phases will correlate with higher defect density.
4. Demand‑resource imbalance – teams with limited resources relative to imposed deadlines will exhibit a speed‑accuracy trade‑off, producing faster but less reliable code.
5. Control as buffer – granting developers higher autonomy (control over task pacing) will mitigate the negative impact of time pressure on engagement and performance.

The authors argue that these hypotheses can be empirically examined using software repository data: commit timestamps, issue‑tracking metrics, code review turnaround, and communication logs (e.g., Slack). By operationalizing time pressure (e.g., variance in task completion rates, proximity to release dates) and linking it to outcome variables (effort, defect rates, code churn, developer sentiment), future work can validate or refute the proposed relationships.

In conclusion, the study demonstrates that while time pressure is a well‑studied construct across many disciplines, its investigation within software engineering remains limited. The interdisciplinary literature review not only maps the existing knowledge landscape but also translates robust findings from psychology, management, and auditing into concrete, repository‑driven research questions for the software community. This groundwork paves the way for developing automated detection tools and intervention strategies aimed at maintaining optimal pressure levels, thereby enhancing developer well‑being and productivity.