How Developers and Managers Define and Trade Productivity for Quality
Margaret-Anne Storey, Brian Houck, Thomas Zimmermann

TL;DR
This study explores how developers and managers define and trade off productivity and quality in software development, revealing misalignments and proposing a new framework for understanding quality.
Contribution
It introduces the TRUCE framework for describing software quality and highlights the need for better communication on quality and productivity trade-offs.
Findings
Developers view productivity as activity, managers see it as performance.
Both groups largely agree quality is about robustness.
Over half see quality as tradeable for productivity.
Abstract
In this paper, we present the findings from a survey study to investigate how developers and managers define and trade-off developer productivity and software quality (two related lenses into software development). We found that developers and managers, as cohorts, are not well aligned in their views of what it means to be productive (developers think of productivity in terms of activity, while more managers think of productivity in terms of performance). We also found that developers are not accurate at predicting their managers' views of productivity. In terms of quality, we found that individual developers and managers have quite varied views of what quality means to them, but as cohorts they are closely aligned in their different views, with the majority in both groups defining quality in terms of robustness. Over half of the developers and managers reported that quality can be…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
