CoChat
Sign Up
Cited by 401Software Engineering Techniques and PracticesSoftware Engineering ResearchUsability and User Interface Design

People, organizations, and process improvement

Perry, D.E., Staudenmayer, N.A., Votta, L.G.·1994·IEEE Software
DOI 10.1109/52.300082
Open this paper in CoChat — free account

Abstract

In their efforts to determine how technology affects the software development process, researchers often overlook organizational and social issues. The authors report on two experiments to discover how developers spend their time. They describe how noncoding activities can use up development time and how even a reluctance to use e-mail can influence the development process. The first experiment was to see how programmers thought they spent their time by having them fill out a modified time card reporting their activities, which we called a time diary. In the second experiment, we used direct observation to calibrate and validate the use of time diaries, which helped us evaluate how time was actually being used.>

Integrity signals

Registry

Crossref · 10.1109/52.300082

Cites

12 of 12 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

  • Software developers constantly switch between a broad variety of tasks, each requiring its own set of artifacts and applications.

    “T O successfully perform their work, software developers are required to constantly switch between a broad variety of tasks, such as implementing a new feature, answering an email or attending a meeting, with each task requiring its own set of artifacts and applications [1], [2], [3].”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [1]

  • Non-development work can account for 39 percent up to 91 percent of the time developers spend at work.

    “which can account for 39 percent up to 91 percent of the time developers spend at work [1], [3], [19], [20], [21].”

    From Detecting Developers' Task Switches and Types (2022) · cites this paper as [1]

Cites

Flagged first, then by citations

1 of the 13 references couldn’t be matched to a known paper.

Cited by

Sorted by citations

Related

Authors
Perry, D. E., Staudenmayer, N. A., & Votta, L. G.
Affiliations
  • AT&T (United States) (US)
  • Massachusetts Institute of Technology (US)
ORCID
Votta, L.G.
Venue
IEEE Software
Publisher
Institute of Electrical and Electronics Engineers (IEEE)
Published
1994-07
Volume
11
Issue
4
Pages
36-45
ISSN
0740-7459 (ISSN-L)
DOI
10.1109/52.300082
OpenAlex
W1979465005
Cited by
401
References
13
Citations by year
2026: 2 · 2025: 5 · 2024: 3 · 2023: 5 · 2022: 10 · 2021: 8 · 2020: 8 · 2019: 11 · 2018: 6 · 2017: 14 · 2016: 11 · 2015: 13 · 2014: 14 · 2013: 12 · 2012: 25
FWCI
31.51
Type
journal article
Language
en
Open access
closed
Licence
ieeexplore.ieee.org/Xplorehelp/downloads/license-information/IEEE.html (vor)
Locations
IEEE Software (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
Keywords
software development process, time diaries, email use, organizational factors, process improvement

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