2021
DOI: 10.1109/tse.2019.2900308
|View full text |Cite
|
Sign up to set email alerts
|

What Predicts Software Developers’ Productivity?

Abstract: Organizations have a variety of options to help their software developers become their most productive selves, from modifying office layouts, to investing in better tools, to cleaning up the source code. But which options will have the biggest impact? Drawing from the literature in software engineering and industrial/organizational psychology to identify factors that correlate with productivity, we designed a survey that asked 622 developers across 3 companies about these productivity factors and about self-ra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

2
36
0
1

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 53 publications
(39 citation statements)
references
References 41 publications
2
36
0
1
Order By: Relevance
“…Since the survey was anonymous and no personal identifiable information was collected (to encourage more candid responses), we were unable to triangulate responses from members of the same team, which would have further improved the validity of the findings. 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].…”
Section: Th R E a T S T O Va L I D I T Ymentioning
confidence: 97%
See 2 more Smart Citations
“…Since the survey was anonymous and no personal identifiable information was collected (to encourage more candid responses), we were unable to triangulate responses from members of the same team, which would have further improved the validity of the findings. 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].…”
Section: Th R E a T S T O Va L I D I T Ymentioning
confidence: 97%
“…(Team-Q3) The items and response formats for Team-Q2 and Team-Q3 can be found in Tables I and II. The items for Team-Q2 and Team-Q3 were derived from a combination of the WFH-Survey and previous literature [12].…”
Section: B Team-surveymentioning
confidence: 99%
See 1 more Smart Citation
“…job satisfaction, stress level) [44], [45]. On productive days, developers generally manage to make a lot of progress on their tasks, are supported by their co-workers or other peers, and have a minimum amount of context switches [43], [46], [47]. Contrary, some of the biggest impediments to productive work are regular external interruptions, selfdistractions and meetings, since they can make it difficult to focus on and make progress on coding tasks for an extended time (e.g.…”
Section: Developers' Work and Productivitymentioning
confidence: 99%
“…While software development contains tasks not captured by these metrics, the number of commits and lines of code have been widely used as proxy measures for productivity in software engineering (Mockus et al 2002;Boehm and et al 1981). Recent work has noted lines of code having the highest correlation with self-evaluated productivity (Murphy-Hill et al 2019). Entropy has been used to quantify the complexity of code changes in previous literature (Hassan 2009).…”
Section: Version Control Systemmentioning
confidence: 99%