Software Development Waste
The DOI matches its Crossref record; 8 of the 8 references it cites were found in a registry or an index.
Abstract
Context: Since software development is a complex socio-technical activity that involves coordinating different disciplines and skill sets, it provides ample opportunities for waste to emerge. Waste is any activity that produces no value for the customer or user. Objective: The purpose of this paper is to identify and describe different types of waste in software development. Method: Following Constructivist Grounded Theory, we conducted a two-year five-month participant-observation study of eight software development projects at Pivotal, a software development consultancy. We also interviewed 33 software engineers, interaction designers, and product managers, and analyzed one year of retrospection topics. We iterated between analysis and theoretical sampling until achieving theoretical saturation. Results: This paper introduces the first empirical waste taxonomy. It identifies nine wastes and explores their causes, underlying tensions, and overall relationship to the waste taxonomy found in Lean Software Development. Limitations: Grounded Theory does not support statistical generalization. While the proposed taxonomy appears widely applicable, organizations with different software development cultures may experience different waste types. Conclusion: Software development projects manifest nine types of waste: building the wrong feature or product, mismanaging the backlog, rework, unnecessarily complex solutions, extraneous cognitive load, psychological distress, waiting/multitasking, knowledge loss, and ineffective communication.
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
Cognitive Load During Problem Solving: Effects on Learning
Sweller, J. (1988) · Cognitive Science · doi:10.1016/0364-0213(88)90023-7 · Cited by 11,048 · cited 2×
“Overcomplicated stories—user stories that are unnecessarily long, complex, unclear, or replete with pointers to other necessary information—are precisely the sort of task materials that Cognitive Load Theory predicts will overburden working memory.”
BackgroundMonsell, S. (2003) · Trends in Cognitive Sciences · doi:10.1016/s1364-6613(03)00028-7 · Cited by 2,984
Jost, J. T., Banaji, M. R., & Nosek, B. A. (2004) · Political Psychology · doi:10.1111/j.1467-9221.2004.00402.x · Cited by 2,883
Cognitive Load Theory and Complex Learning: Recent Developments and Future Directions
van Merriënboer, J. J. G., & Sweller, J. (2005) · Educational Psychology Review · doi:10.1007/s10648-005-3951-0 · Cited by 2,206
Lean Thinking—Banish Waste and Create Wealth in your Corporation
Womack, J. P., & Jones, D. T. (1997) · Journal of the Operational Research Society · doi:10.1057/palgrave.jors.2600967 · Cited by 2,122
Element Interactivity and Intrinsic, Extraneous, and Germane Cognitive Load
Sweller, J. (2010) · Educational Psychology Review · doi:10.1007/s10648-010-9128-5 · Cited by 2,020
A Study of the Toyota Production System From an Industrial Engineering Viewpoint
Shingo, S., & Bodek, N. (2019) · doi:10.4324/9781315136509 · Cited by 1,064
Grounded theory in software engineering research: a critical review and guidelines
Stol, K.-J., Ralph, P., & Fitzgerald, B. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884833 · Cited by 470
Self-citation
Cited by
Socio-Technical Grounded Theory for Software Engineering
Hoda, R. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3106280 · Cited by 204
The SPACE of Developer Productivity: There's more to it than you think.
Forsgren, N., Storey, M.-A., Maddila, C., Zimmermann, T., Houck, B., & Butler, J. (2021) · Queue · doi:10.1145/3454122.3454124 · Cited by 164
Construct Validity in Software Engineering Research and Software Metrics
Ralph, P., & Tempero, E. (2018) · Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018 · doi:10.1145/3210459.3210461 · Cited by 78
“For example, the nine types of software development waste (e.g. rework, psychological distress, ineffective communication) proposed by Sedano et al. [29] are classes.”
BackgroundSelf-citationRazzaq, A., Buckley, J., Lai, Q., Yu, T., & Botterweck, G. (2025) · ACM Computing Surveys · doi:10.1145/3687299 · Cited by 36
The SPACE of developer productivity
Forsgren, N., Storey, M.-A., Maddila, C., Zimmermann, T., Houck, B., & Butler, J. (2021) · Communications of the ACM · doi:10.1145/3453928 · Cited by 21
Metadata
- Authors
- Sedano, T., Ralph, P., & Peraire, C.
- Venue
- 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2017-05
- Pages
- 130-140
- OpenAlex
- W2618269984
- Cited by
- 120
- References
- 8
- FWCI
- 10.59
- Type
- conference paper
- Language
- en
- Open access
- closed
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: Software Development Waste. https://app.cochat.ai/papers/10.1109/icse.2017.20
- The paper
- Sedano, T., Ralph, P., & Peraire, C. (2017). Software Development Waste. 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE). https://doi.org/10.1109/icse.2017.20
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.