The DOI matches its Crossref record; 41 of the 44 references it cites were found in a registry or an index.
Software developers' perceptions of productivity
Open accessAbstract
The better the software development community becomes at creating software, the more software the world seems to demand. Although there is a large body of research about measuring and investigating productivity from an organizational point of view, there is a paucity of research about how software developers, those at the front-line of software construction, think about, assess and try to improve their productivity. To investigate software developers' perceptions of software development productivity, we conducted two studies: a survey with 379 professional software developers to help elicit themes and an observational study with 11 professional software developers to investigate emergent themes in more detail. In both studies, we found that developers perceive their days as productive when they complete many or big tasks without significant interruptions or context switches. Yet, the observational data we collected shows our participants performed significant task and activity switching while still feeling productive. We analyze such apparent contradictions in our findings and use the analysis to propose ways to better support software developers in a retrospection and improvement of their productivity through the development of new tools and the sharing of best practices.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“We used common categories typical for software developers that had previously been identified by Meyer et al. [56].”
From Sensing Interruptibility in the Office: A Field Study on the Use of Biometric and Computer Interaction Sensors (2018) · cites this paper as [56]
In the citing paper
“since developers spend on average only 1 to 2 minutes in an application before switching to another [2], [3], [23]”
From Detecting Developers' Task Switches and Types (2022) · cites this paper as [23]
In the citing paper
“Developers' task switch behaviors are similar to previous work [2], [23].”
From Detecting Developers' Task Switches and Types (2022) · cites this paper as [23]
In the citing paper
“This is in line with a survey with 379 developers that showed the most-often mentioned measurement of interest when reflecting about productivity are the tasks developers made progress on and completed in a workday [23].”
From Detecting Developers' Task Switches and Types (2022) · cites this paper as [23]
In the citing paper
“However, we grounded our survey design in well-established productivity frameworks and prior validated measures used in related work [4, 16, 36].”
From The Fast and Spurious: Developer Productivity with GenAI (2025) · cites this paper as [16]
1 more claim about this paper
Create a free account to see every claim other papers make about this one.
Citations
Cites
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
Using Pedometers to Increase Physical Activity and Improve Health: A Systematic Review
Bravata, D. M., Smith-Spangler, C., Sundaram, V., Gienger, A. L., Lin, N., Lewis, R., Stave, C. D., Olkin, I., & Sirard, J. R. (2007) · JAMA · doi:10.1001/jama.298.19.2296 · Cited by 2,064 · cited 1×
“For example, goal-setting has been shown to be successful in motivating people to be more active, in particular in combination with self-monitoring (e.g. [10, 7]).”
BackgroundTwo case studies of open source software development: Apache and Mozilla
Mockus, A., Fielding, R. T., & Herbsleb, J. D. (2002) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/567793.567795 · Cited by 1,685
Persuasive technology: using computers to change what we think and do
Fogg, B. J. (2002) · Ubiquity · doi:10.1145/764008.763957 · Cited by 1,554
Activity sensing in the wild: a field trial of ubifit garden
Consolvo, S., McDonald, D. W., Toscos, T., Chen, M. Y., Froehlich, J., Harrison, B., Klasnja, P., LaMarca, A., LeGrand, L., Libby, R., et al. (2008) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1357054.1357335 · Cited by 1,131
Extreme Programming Explained: Embrace Change (2nd Edition)
Beck, K. L., & Andres, C. (2004) · Addison-Wesley Professional eBooks · Cited by 929
Mintzberg, H. (1980) · International Linear Collider · Cited by 798
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
(2013) · doi:10.1145/2470654 · Cited by 753
"Constant, constant, multi-tasking craziness": managing multiple working spheres
González, V. M., & Mark, G. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985707 · Cited by 715
Dijkstra, E. W. (1972) · Communications of the ACM · doi:10.1145/355604.361591 · Cited by 705
Research works printed but not linked: 3
- 10.5555/1076267 · doi:10.5555/1076267
- P. Naur and B. Randell . Software engineering: Report of a conference sponsored by the nato science committee. Scientific Affairs Division , NATO , 1969 . P. Naur and B. Randell. Software engineering: Report of a conference sponsored by the nato science committee. Scientific Affairs Division, NATO, 1969.
- O. U. Press. Oxford dictionary. www.oxforddictionaries.com/us/definition/american english/productivity. O. U. Press. Oxford dictionary. www.oxforddictionaries.com/us/definition/american english/productivity.
Cited by
A Tale of Two Cities: Software Developers Working from Home during the COVID-19 Pandemic
Ford, D., Storey, M.-A., Zimmermann, T., Bird, C., Jaffe, S., Maddila, C., Butler, J. L., Houck, B., & Nagappan, N. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3487567 · Cited by 217
“[14] investigated how developers perceive and think about their own productivity.”
BackgroundSelf-citationThe Work Life of Developers: Activities, Switches and Perceived Productivity
Meyer, A. N., Barton, L. E., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2656886 · Cited by 170
“’s and our previous observations [5], [10], [11].”
BackgroundMethodResultInfluentialSelf-citationWhen, how, and why developers (do not) test in their IDEs
Beller, M., Gousios, G., Panichella, A., & Zaidman, A. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786843 · Cited by 162
“found that 47 out of 379 surveyed software engineering professionals perceive tasks such as testing as unproductive [39].”
BackgroundSensecape: Enabling Multilevel Exploration and Sensemaking with Large Language Models
Suh, S., Min, B., Palani, S., & Xia, H. (2023) · Proceedings of the 36th Annual ACM Symposium on User Interface Software and Technology · doi:10.1145/3586183.3606756 · Cited by 151
“Furthermore, since the tools in which users take notes and work with this information are separate from the tools we use to explore information, it can be distracting to switch attention back and forth between the search and sensemaking tools [9, 35].”
BackgroundLin, Y.-T. (2018) · Computers in Human Behavior · doi:10.1016/j.chb.2018.11.036 · Cited by 181
Sensecape: Enabling Multilevel Exploration and Sensemaking with Large Language Models
Suh, S., Min, B., Palani, S., & Xia, H. (2023) · arXiv · doi:10.48550/arxiv.2305.11483 · Cited by 151
Stuck and Frustrated or in Flow and Happy: Sensing Developers' Emotions and Progress
Muller, S. C., & Fritz, T. (2015) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2015.334 · Cited by 267
“5 minutes during their work [36].”
Self-citationHow practitioners perceive the relevance of software engineering research
Lo, D., Nagappan, N., & Zimmermann, T. (2015) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2786805.2786809 · Cited by 149
“Other work has focussed on how practitioners perceived specific software enginerring concepts such as coupling [22], bad smells [23], and productivity [24].”
BackgroundSelf-citationNot all bugs are the same: Understanding, characterizing, and classifying bug types
Catolino, G., Palomba, F., Zaidman, A., & Ferrucci, F. (2019) · Journal of Systems and Software · doi:10.1016/j.jss.2019.03.002 · Cited by 151
“less important than bugs appearing in production [51, 83], our data shows that developers react pretty fast to their reporting: both mean and median are equal to 7, meaning that the reaction of developers is observed within one week.”
BackgroundSupervised vs Unsupervised Models: A Holistic Look at Effort-Aware Just-in-Time Defect Prediction
Huang, Q., Xia, X., & Lo, D. (2017) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsme.2017.51 · Cited by 133
“[15] conducted a survey with 379 professional software developers and they found that developers perceive their days as productive when they complete many or big tasks without significant interruptions or context switches.”
BackgroundInfluentialRevisiting supervised and unsupervised models for effort-aware just-in-time defect prediction
Huang, Q., Xia, X., & Lo, D. (2018) · Empirical Software Engineering · doi:10.1007/s10664-018-9661-2 · Cited by 134
“However, it is not reasonable to expect developers to inspect too many changes due to the additional effort required for frequent context switches (Meyer et al. 2014).”
BackgroundInfluentialToday was a good day: The daily life of software developers
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2904957 · Cited by 123
“bad overall [9], [14], [21], [22], [23], [61].”
BackgroundInfluentialSelf-citationMeasuring GitHub Copilot's Impact on Productivity
Ziegler, A., Kalliamvakou, E., Li, X. A., Rice, A., Rifkin, D., Simister, S., Sittampalam, G., & Aftandilian, E. (2024) · Communications of the ACM · doi:10.1145/3633453 · Cited by 124
“˲ In addition, developers’ perspective on what affects their productivity 12 and what metrics might reflect it 14 differs from the inputs/ outputs view.”
BackgroundBao, L., Li, T., Xia, X., Zhu, K., Li, H., & Yang, X. (2022) · Science China Information Sciences · doi:10.1007/s11432-020-3278-4 · Cited by 207
(2016) · doi:10.1145/2950290.2983989 · Cited by 153
“Tools like Slack can be integrated with issue tracking systems such as GitHub and Trac, and through these integrations, developers can gain awareness of commits without necessarily being interrupted, potentially improving their productivity as they can stay in the “flow” [4].”
BackgroundMethod(2015) · doi:10.5555/2818754.2818838 · Cited by 111
Self-citationDeveloper Testing in the IDE: Patterns, Beliefs, and Behavior
Beller, M., Gousios, G., Panichella, A., Proksch, S., Amann, S., & Zaidman, A. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2776152 · Cited by 112
“found similar numbers when presenting developers with a report of their productivity [90].”
BackgroundHow Practitioners Perceive Automated Bug Report Management Techniques
Zou, W., Lo, D., Chen, Z., Xia, X., Feng, Y., & Xu, B. (2018) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2870414 · Cited by 121
“the characteristics of software development and developers’ behavior [49], [53], [26], [27], [81].”
BackgroundResultInfluentialRevisiting Supervised and Unsupervised Methods for Effort-Aware Cross-Project Defect Prediction
Ni, C., Xia, X., Lo, D., Chen, X., & Gu, Q. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.3001739 · Cited by 103
“For example, Meyer et al. [36] conducted a survey with 379 professional software developers and they found that developers perceive their days as productive when they complete many or big tasks without significant interruptions or context switches.”
BackgroundResultInfluentialTowards a Theory of Software Developer Job Satisfaction and Perceived Productivity
Storey, M.-A., Zimmermann, T., Bird, C., Czerwonka, J., Murphy, B., & Kalliamvakou, E. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2944354 · Cited by 90
“Using a different lens, Meyer et al. [6] looked at how developers perceive and think about their own productivity.”
BackgroundSelf-citationŠmite, D., Tkalich, A., Moe, N. B., Papatheocharous, E., Klotins, E., & Buvik, M. P. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2021.111197 · Cited by 108
“Productivity generally refers to the rate of produced output per unit of time (Meyer et al., 2014; de Lemos Meira et al., 2010).”
Current and Future Bots in Software Development
Erlenhov, L., Neto, F. G. D. O., Scandariato, R., & Leitner, P. (2019) · IEEE/ACM International Workshop on Bots in Software Engineering (BotSE) · doi:10.1109/botse.2019.00009 · Cited by 82
“Even though research on developer productivity is gaining traction [1], it is unlikely that we will be able to keep up with the increasing demand for software without making more, and better, use of artificial intelligence (AI) and automation.”
What Predicts Software Developers’ Productivity?
Murphy-Hill, E., Jaspan, C., Sadowski, C., Shepherd, D., Phillips, M., Winter, C., Knight, A., Smith, E., & Jorde, M. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2900308 · Cited by 100
The sky is not the limit: multitasking across GitHub projects
Vasilescu, B., Blincoe, K., Xuan, Q., Casalnuovo, C., Damian, D., Devanbu, P., & Filkov, V. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884875 · Cited by 77
“Furthermore, a recent study found that developers associate minimal interruptions and context switches with higher productivity; however, they also reportedly feel productive when significant task switching occurs [35].”
BackgroundThe Effect of Work Environments on Productivity and Satisfaction of Software Engineers
Johnson, B., Zimmermann, T., & Bird, C. (2019) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2903053 · Cited by 88
“A significant amount of research investigated how to measure productivity in software development [82], [96], [97], [105], [118], [124].”
BackgroundSelf-citationA Study of Visual Studio Usage in Practice
Amann, S., Proksch, S., Nadi, S., & Mezini, M. (2016) · 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2016.39 · Cited by 77
“However, previous studies show that expensive background computations, such as static analyses or builds, often slow down a developer’s work in the IDE or make her digress [12], [17].”
BackgroundInfluentialTowards an Autonomous Bot for Automatic Source Code Refactoring
Wyrich, M., & Bogner, J. (2019) · IEEE/ACM International Workshop on Bots in Software Engineering (BotSE) · doi:10.1109/botse.2019.00015 · Cited by 78
“In a study on developer productivity by Meyer et al. [22], getting into a “flow” with no or few interruptions was the second most mentioned reason for a developer to perceive a workday as productive.”
Recognizing developers' emotions while programming
Girardi, D., Novielli, N., Fucci, D., & Lanubile, F. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377811.3380374 · Cited by 87
“minutes as it represents the average time for which developers stay focused on a single task [41, 42].”
BackgroundWhat Makes a Great Manager of Software Engineers?
Kalliamvakou, E., Bird, C., Zimmermann, T., Begel, A., DeLine, R. A., & Germán, D. M. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2768368 · Cited by 90
“oper and team productivity [80], [81], [82].”
Self-citationZüger, M., Müller, S. C., Meyer, A. N., & Fritz, T. (2018) · Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3173574.3174165 · Cited by 66
“We used common categories typical for software developers that had previously been identified by Meyer et al. [56].”
MethodSelf-citationErlenhov, L., Neto, F. G. D. O., & Leitner, P. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3409680 · Cited by 92
“y “on call” to react to production issues [11]. Unsurprisingly, previous work has reported that developers often feel distracted and unproductive, especially if they have to change context frequently [20]. Partly as a reaction, more and more software projects employ software development bots (DevBots), automated tools…”
MethodThe Daily Life of Software Engineers During the COVID-19 Pandemic
Russo, D., Hanel, P. H. P., Altnickel, S., & van Berkel, N. (2021) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip52600.2021.00048 · Cited by 67
“researchers propose a self-reflection measure with developers’ self-reporting their daily productivity [36].”
BackgroundContext-aware conversational developer assistants
Bradley, N. C., Fritz, T., & Holmes, R. (2018) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3180155.3180238 · Cited by 68
“Empirical studies have shown that developers have to perform a broad variety of development tasks, frequently switching applications and contexts [5, 13, 14].”
BackgroundSelf-citationThe Perpetual Work Life of Crowdworkers: How Tooling Practices Increase Fragmentation in Crowdwork
Williams, A. C., Mark, G. J., Milland, K., Lank, E., & Law, E. (2019) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3359126 · Cited by 89
“Our approach is heavily inspired by prior studies of information work [79, 103] that share the goal of identifying opportunities for improving peoples’ efficiency in their work [51].”
MethodDesign Recommendations for Self-Monitoring in the Workplace: Studies in Software Development
Meyer, A. N., Murphy, G. C., Zimmermann, T., & Fritz, T. (2017) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3134714 · Cited by 60
“…been identified towards the adoption of self-tracking technologies at the workplace, including not fully understanding users’ needs [43], not knowing in what measures users are interested in [54, 59, 67], and not providing users with a holistic understanding of their work behavior [2, 7, 27, 33].”
BackgroundMethodResultInfluentialSelf-citationGraziotin, D., Wang, X., & Abrahamsson, P. (2015) · PeerJ Computer Science · doi:10.7717/peerj-cs.18 · Cited by 77
“…of the distance towards the completion of such task, and to re-define the goal683 during the work day.684 Our findings are in line with those of Meyer et al. (2014), where the participants in a survey685 perceived a productive day as a day where “they complete their tasks, achieve a planned…”
MethodResultInfluentialSignificant Productivity Gains through Programming with Large Language Models
Weber, T., Brandmaier, M., Schmidt, A., & Mayer, S. (2024) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3661145 · Cited by 64
“For this reason, we include the correctness of the code that participants created during the task, which corresponds to the number of work items (bugs, tasks) closed [31] and the absence of bugs [17].”
How Developers Engineer Test Cases: An Observational Study
Aniche, M. F., Treude, C., & Zaidman, A. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3129889 · Cited by 83
Unakite: Scaffolding Developers' Decision-Making Using the Web
Liu, M. X., Hsieh, J., Hahn, N., Zhou, A., Deng, E., Burley, S., Taylor, C., Kittur, A., & Myers, B. A. (2019) · ACM Symposium on User Interface Software and Technology (UIST) · doi:10.1145/3332165.3347908 · Cited by 66
“Such frequent context switches are tedious and have been shown to harm developers’ productivity [29, 34, 47].”
BackgroundA conceptual replication of continuous integration pain points in the context of Travis CI
Widder, D. G., Hilton, M. L., Kästner, C., & Vasilescu, B. (2019) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3338906.3338922 · Cited by 66
“Thirdly, infrequent changes were a commonly cited reason for CI abandonment, but our model showed the opposite: less active projects were less likely to abandon CI.”
ResultKwarteng, S., Frimpong, S. O., Asare, R., & Wiredu, T. J. N. (2023) · Current Psychology · doi:10.1007/s12144-023-04708-9 · Cited by 52
Leveraging Biometric Data to Boost Software Developer Productivity
Fritz, T., & Muller, S. C. (2016) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2016.107 · Cited by 57
“Interruptions were one of the most commonly named reasons for decreasing developer productivity [73].”
BackgroundInfluentialSelf-citationEnabling Good Work Habits in Software Developers through Reflective Goal-Setting
Meyer, A. N., Murphy, G. C., Zimmermann, T., & Fritz, T. (2019) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2938525 · Cited by 50
“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].”
BackgroundSelf-citationSummarizing and measuring development activity
Treude, C., Filho, F. F., & Kulesza, U. (2015) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2786805.2786827 · Cited by 44
“Looking at different conceptualizations of developer productivity in the literature, Meyer et al. [39] found a long list of defini-tions: the number of tasks [59], function points [30], lines of code [17, 44], modification requests [42], or logical source statements [34] in a given time frame or…”
BackgroundInfluentialCode and commit metrics of developer productivity: a study on team leaders perceptions
de Oliveira, E. C. C., Fernandes, E., Steinmacher, I., de Cristo, M. A. P., Conte, T. U., & Garcia, A. (2020) · Empirical Software Engineering · doi:10.1007/s10664-020-09820-z · Cited by 62
“Differently from both studies [35] [36], our current work targets the perceptions of developer productivity from the viewpoint of team leaders.”
BackgroundInfluentialAn Empirical Study on Recommendations of Similar Bugs
Rocha, H., Valente, M. T., Marques-Neto, H. T., & Murphy, G. C. (2016) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2016.87 · Cited by 45
“The negative impacts of context switches on productivity are well-known [26].”
BackgroundSelf-citationTrustworthy and Synergistic Artificial Intelligence for Software Engineering: Vision and Roadmaps
Lo, D. (2023) · IEEE/ACM International Conference on Software Engineering: Future of Software Engineering (ICSE-FoSE) · doi:10.1109/icse-fose59343.2023.00010 · Cited by 90
“This state has been proven crucial for the productivity of software practitioners [60], [61].”
BackgroundException handling bug hazards in Android: Results from a mining study and an exploratory survey
Coelho, R. D. S., de Almeida, L. M. G., Gousios, G., Arie Van Deursen, A., & Treude, C. (2016) · Empirical Software Engineering · doi:10.1007/s10664-016-9443-7 · Cited by 42
“Exploratory surveys have been used in the software engineering context to discover the user perspective regarding a broad range of topics such as: assessing the developers’ perceptions on productivity [40]; how GitHub developers use pull-requests [26]; how the testing culture of open-source projects can be characteriz…”
MethodMoletsane, M. R., Tefera, O., & Migiro, S. O. (2019) · African Journal of Business and Economic Research · doi:10.31920/1750-4562/2019/v14n1a6 · Cited by 74
Large-Scale Empirical Studies on Effort-Aware Security Vulnerability Prediction Methods
Chen, X., Zhao, Y., Cui, Z., Meng, G., Liu, Y., & Wang, Z. (2019) · IEEE Transactions on Reliability · doi:10.1109/tr.2019.2924932 · Cited by 44
“It means that the additional efforts required due to context switches and additional communication overhead among developers should not be ignored [64].”
BackgroundCho, J., Beck, S., & Voida, S. (2022) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3492843 · Cited by 51
“As we have seen from other recent papers [59, 78], the cultural norm of busyness is ingrained in how people evaluate their own performance.”
BackgroundWeisz, J. D., Kumar, S. V., Muller, M., Browne, K.-E., Goldberg, A., Heintze, K. E., & Bajpai, S. (2025) · Proceedings of the Extended Abstracts of the CHI Conference on Human Factors in Computing Systems · doi:10.1145/3706599.3706670 · Cited by 37
“However, Meyer et al. [34] considers “when software developers perceive themselves to be productive and... unproductive” [34, p.1] as an important aspect of productivity.”
Razzaq, A., Buckley, J., Lai, Q., Yu, T., & Botterweck, G. (2025) · ACM Computing Surveys · doi:10.1145/3687299 · Cited by 36
“This means developers are less interested in co-workers’ activities until their work cross-cuts with them [S74].”
InfluentialGray links in the use of requirements traceability
Niu, N., Wang, W., & Gupta, A. (2016) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2950290.2950354 · Cited by 43
“Finally, we are interested in extending, expanding, and enhancing the gray links toward developers’ daily tasks (e.g., refactoring and code review), which are not only commonly assigned to them but are also integral to their own perceptions of productivity [42].”
BackgroundCharacterizing Software Developers by Perceptions of Productivity
Meyer, A. N., Zimmermann, T., & Fritz, T. (2017) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2017.17 · Cited by 36
“We prompted users for two keywords each to foster more than one precise definition of productivity, similar to what we applied in a previous study [9].”
BackgroundMethodInfluentialSelf-citationBezerra, C. I. M., Filho, J. C. D. S., Coutinho, E. F., Gama, A., Ferreira, A. L., de Andrade, G. L., & Feitosa, C. (2020) · Brazilian Symposium on Software Engineering · doi:10.1145/3422392.3422417 · Cited by 41
“Software productivity has been discussed by several studies in software engineering [16, 22, 24].”
MethodWyrich, M., Ghit, R., Haller, T., & Müller, C. A. (2021) · IEEE/ACM International Workshop on Bots in Software Engineering (BotSE) · doi:10.1109/botse52550.2021.00009 · Cited by 36
“We already knew from a study by Meyer et al. [10] that developers perceive their workday as productive if they could complete tasks without significant interruptions.”
Optimal Group Size for Software Change Tasks: A Social Information Foraging Perspective
Bhowmik, T., Niu, N., Wang, W., Cheng, J.-R. C., Li, L., & Cao, X. (2015) · IEEE Transactions on Cybernetics · doi:10.1109/tcyb.2015.2420316 · Cited by 43
“For example, a developer may achieve individual productivity gain by reducing social interactions [48].”
BackgroundMethodInfluentialAssessing developer contribution with repository mining-based metrics
de Lima, J. R. F., Treude, C., Filho, F. F., & Kulesza, U. (2015) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2015.7332509 · Cited by 39
“[13], we asked project and team leaders rather than developers for their input, considering that it is usually individuals in leading roles who need to assess the contribution of developers.”
BackgroundRevisiting Heterogeneous Defect Prediction: How Far Are We?
Chen, X., Mu, Y.-Z., Liu, K., Cui, Z.-Q., & Ni, C. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2020.106441 · Cited by 27
“It means that the additional efforts required due to context switches and additional communication overhead among developer [53].”
BackgroundEffort-aware just-in-time defect identification in practice: a case study at Alibaba
Yan, M. L., Xia, X., Fan, Y., Lo, D., Hassan, A. E., & Zhang, X. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3417048 · Cited by 36
“As a result, the additional effort might be required due to the context switches between changes and the additional communication overhead among developers [12, 27].”
BackgroundAbad, Z. S. H., Karras, O., Schneider, K., Barker, K., & Bauer, M. (2018) · Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018 · doi:10.1145/3210459.3210471 · Cited by 32
“Research into developers’ productivity and multitasking provide evidence on how multitasking and interruptions can impact productivity in soware development teams [22, 24, 36].”
BackgroundA context model for IDE-based recommendation systems
Gašparič, M., Murphy, G. C., & Ricci⋆, F. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2016.09.012 · Cited by 33
“Meyer et al. decribe six primary activity categories with related sub-categories: oding (reading, editing, and navigating), debugging, using version ontrol (reading, accepting, submitting changes), testing performed utside the IDE, reviewing code, and other ( Meyer et al., 2014 ).”
BackgroundMethodSelf-citationHow Practitioners Perceive the Relevance of ESEM Research
Carver, J. C., Dieste, Ó., Kraft, N. A., Lo, D., & Zimmermann, T. (2016) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/2961111.2962597 · Cited by 31
“[13] investigated developer perception on productivity.”
BackgroundSelf-citationAn empirical study of work fragmentation in software evolution tasks
Sanchez, H., Robbes, R., & González, V. M. (2015) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2015.7081835 · Cited by 40
“They found that developers perceived they were more productive on days where they accomplished significant tasks, and when they were not significantly interrupted [12].”
BackgroundHow Practitioners Perceive Coding Proficiency
Xia, X., Wan, Z., Kochhar, P. S., & Lo, D. (2019) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2019.00098 · Cited by 27
“Same demographic categories are also used by previous studies [14], [15], [26]– [31].”
BackgroundMethodResultA gamification solution for improving Scrum adoption
Marques, R., da Costa, G. F., da Silva, M. M., Gonçalves, D. J. V., & Gonçalves, P. (2020) · Empirical Software Engineering · doi:10.1007/s10664-020-09816-9 · Cited by 32
“…success of the project; having feedback regarding team and individual performance, based on data collected and relevant metrics; and receive rewards and incentives (Mahaney and Lederer 2006; Beecham et al. 2008; França et al. 2011; DeMarco and Lister 2013; Meyer et al. 2014; Verner et al. 2014).”
BackgroundLeveraging organizational climate theory for understanding industry-academia collaboration
Sherman, S., Hadar, I., & Luria, G. (2017) · Information and Software Technology · doi:10.1016/j.infsof.2017.12.006 · Cited by 37
Enriching in-IDE process information with fine-grained source code history
Proksch, S., Nadi, S., Amann, S., & Mezini, M. (2017) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2017.7884626 · Cited by 25
“Several researchers have conducted such observation studies to, for example, assess developer productivity [35], evaluate the user interface of particular tools [43], or study software evolution [11].”
BackgroundGolzadeh, M., Legay, D., Decan, A., & Mens, T. (2020) · doi:10.1145/3387940.3391503 · Cited by 24
Stettina, C. J., Garbajosa, J., & Kruchten, P. (2023) · Lecture notes in business information processing · doi:10.1007/978-3-031-33976-9 · Cited by 25
The New Future of Work: Research from Microsoft into the Pandemic’s Impact on Work Practices
Teevan, J. B., Hecht, B. J., Jaffe, S., Baym, N. K., rachel-bergmann, Brodsky, M., Buxton, B., Butler, J., Coleman, A., Czerwinski, M. P., et al. (2021) · Cited by 63
Leveraging developer information for efficient effort-aware bug prediction
Qu, Y., Chi, J., & Yin, H. (2021) · Information and Software Technology · doi:10.1016/j.infsof.2021.106605 · Cited by 27
Automated unearthing of dangerous issue reports
Pan, S., Zhou, J., Cogo, F. R., Xia, X., Bao, L., Hu, X., Li, S., & Hassan, A. E. (2022) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3540250.3549156 · Cited by 27
“Since our approach monitors hundreds of OSS ITSs, detecting numerous emerging IRs, a low precision will undermine users’ confidence and eventually cause the approach to be abandoned [53].”
BackgroundDeveloper recommendation on bug commenting: a ranking approach for the developer crowd
Xuan, J., Jiang, H., Zhang, H., & Ren, Z. (2017) · Science China Information Sciences · doi:10.1007/s11432-015-0582-8 · Cited by 23
A tale from the trenches: cognitive biases and software development
Chattopadhyay, S., NELSON, N. M., Au, A., Morales, N., Sanchez, C. A., Pandita, R., & Sarma, A. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377811.3380330 · Cited by 45
“stand developer work practices [31, 32], where they struggle [2, 11], and what information they need [23, 44].”
BackgroundHernandez, R. H., Song, Q., Kou, Y., & Gui, X. (2024) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3613904.3642151 · Cited by 33
“Workplace tracking researchers have similarly raised concerns surrounding increased surveillance in the workplace, drawing comparisons to Foucault’s panopticon [3, 89].”
BackgroundSoftware Project Managers' Perceptions of Productivity Factors: Findings from a Qualitative Study
de Oliveira, E. C. C., Conte, T. U., de Cristo, M. A. P., & Mendes, E. (2016) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/2961111.2962626 · Cited by 25
“[11] also investigated software developers’ perceptions regarding their productivity using a survey and an observational study.”
BackgroundMethodInfluentialProductivity in Agile Software Development: A Systematic Mapping Study
Ramírez‐Mora, S. L., & Oktaba, H. (2017) · International Conference in Software Engineering Research and Innovation (CONISOFT) · doi:10.1109/conisoft.2017.00013 · Cited by 24
“• The results in [5] indicate that productivity is often related with the number of tasks or completed work items.”
BackgroundWriting Code vs. Shipping Code: Productivity Effects Across Generations of AI Coding Tools
Demirer, M., Musolff, L., & Yang, L. (2026) · doi:10.3386/w35275 · Cited by 22
Ahmetoglu, Y., Brumby, D. P., & Cox, A. L. (2021) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3432921 · Cited by 21
“We celebrate the days in which we manage to complete all the tasks we set out to achieve that day [1].”
BackgroundLatent Patterns in Activities: A Field Study of How Developers Manage Context
Chattopadhyay, S., NELSON, N. M., Gonzalez, Y. R., Leon, A. A., Pandita, R., & Sarma, A. (2019) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2019.00051 · Cited by 19
“[6] found that developers organized their development tasks into smaller, basic units of work.”
BackgroundInfluentialEndres, M., Fansher, M., Shah, P., & Weimer, W. R. (2021) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3468264.3468583 · Cited by 27
How developers and managers define and trade productivity for quality
Storey, M.-A. D., Houck, B., & Zimmermann, T. (2022) · International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE) · doi:10.1145/3528579.3529177 · Cited by 26
“[12] investigated how developers perceive and think about their own productivity.”
BackgroundSelf-citationNextBug: a Bugzilla extension for recommending similar bugs
Rocha, H., de Oliveira, G., Marques-Neto, H. T., & Valente, M. T. (2015) · Journal of Software Engineering Research and Development · doi:10.1186/s40411-015-0018-x · Cited by 19
“For example, in a recent survey with developers of the industry, more than 50% of the participants answered that a productive workday is one that flows without context-switches and having no or few interruptions (Meyer et al. 2014).”
BackgroundInterdisciplinary programming language design
Coblenz, M. J., Aldrich, J., Myers, B. A., & Sunshine, J. S. (2018) · ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software (Onward!) · doi:10.1145/3276954.3276965 · Cited by 24
“Some pragmatists think in terms of productivity [39], but others think in terms of exploration [31, 59].”
BackgroundWhat improves developer productivity at google? code quality
Cheng, L., Murphy-Hill, E. R., Canning, M., Jaspan, C. N. C., Green, C., Knight, A., Zhang, N., & Kammer, E. (2022) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3540250.3558940 · Cited by 26
“commonly mentioned reasons for a productive workday was having clear goals and requirements [34].”
BackgroundMethodResultInfluentialWhat constitutes debugging? An exploratory study of debugging episodes
Alaboudi, A., & LaToza, T. D. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10352-5 · Cited by 58
“Developers may be interrupted, either by developers watching live or by others in their physical space, mirroring the typical interruptions developers face in their day-to-day work (Meyer et al. 2014; Abad et al. 2018).”
BackgroundInfluentialDo Bots Modify the Workflow of GitHub Teams?
Saadat, S., Colmenares, N., & Sukthankar, G. (2021) · IEEE/ACM International Workshop on Bots in Software Engineering (BotSE) · doi:10.1109/botse52550.2021.00008 · Cited by 18
“Research on improving the productivity and workflow of software engineering teams has gained traction in recent years [15], [20].”
BackgroundKhatri, Y., & Singh, S. K. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2022.106980 · Cited by 17
An exploratory study of productivity perceptions in software teams
Ruvimova, A., Lill, A., Gugler, J., Howe, L. C., Huang, E. M., Murphy, G. C., & Fritz, T. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510081 · Cited by 23
“Well-run and structured meetings have been shown to support engagement [40], but it remains challenging for meetings to successfully engage people in projects despite advice and protocols being available on how to best structure and run such meetings.”
BackgroundResultInfluentialSelf-citationThe effect of noise on software engineers' performance
Romano, S., Scanniello, G., Fucci, D., Juristo, N., & Turhan, B. (2018) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/3239235.3240496 · Cited by 18
“[27] found that developers feel productive when they do not need to switch between tasks and are not interrupted.”
BackgroundWorkforce Analytics in Teleworking
Kifor, C. V., Nicolaescu, S. Ş., Florea, A., Săvescu, R. F., Receu, I., Țîrlea, A. V., & Dănuţ, R. E. (2021) · IEEE Access · doi:10.1109/access.2021.3129248 · Cited by 19
“[33] reviewed the relevant literature for software development companies and indicated a commonly accepted list of key performance indicators (KPIs): number of modification requests and added lines of code per year, number of tasks per month, number of function points per month, number of source lines of code per hour…”
BackgroundDetecting Developers' Task Switches and Types
Meyer, A. N., Satterfield, C., Zuger, M., Kevic, K., Murphy, G. C., Zimmermann, T., & Fritz, T. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.2984086 · Cited by 14
“an appropriate time window with minimal prediction delay, since developers spend on average only 1 to 2 minutes in an application before switching to another [2], [3], [23], and”
BackgroundResultInfluentialSelf-citationUsing biometric data in software engineering: a systematic mapping study
Menzen, J. P., Farias, K., & Bischoff, V. (2020) · Behaviour and Information Technology · doi:10.1080/0144929x.2020.1734086 · Cited by 14
“However, Meyer developed an application to monitor daily tasks (Meyer et al. 2017), and came to a categorisation of activities similar to those obtained in previous surveys (Meyer et al. 2014).”
MethodResultUddin, G., Alam, O., & Serebrenik, A. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10156-z · Cited by 17
“In general, developers’ are not happy when they are interrupted (Meyer et al. 2014).”
BackgroundInfluentialMurazvu, G., Parkinson, S., Khan, S., Liu, N., & Allen, G. (2024) · Software · doi:10.3390/software3010001 · Cited by 22
“Another recent research study focused on acquiring the perception of productivity by software developers [46].”
BackgroundWhat Flows through a Software Value Stream?
Kersten, M. A. (2018) · IEEE Software · doi:10.1109/ms.2018.2801538 · Cited by 21
Dimensions of Consistency in GSD: Social Factors, Structures and Interactions
Sievi-Korte, O., Fagerholm, F., Systä, K., & Mikkonen, T. (2020) · Lecture notes in computer science · doi:10.1007/978-3-030-64148-1_20 · Cited by 13
“In general, it is known that developers’ views on productivity varies [19] and that they communicate with their managers in different ways, so it is not surprising that issues arise in GSD when the communication bandwidth is limited or trust has not yet been built.”
BackgroundAn effective software cross-project fault prediction model for quality improvement
Khatri, Y., & Singh, S. K. (2023) · Science of Computer Programming · doi:10.1016/j.scico.2022.102918 · Cited by 13
Metadata
- Authors
- Meyer, A. N., Fritz, T., Murphy, G. C., & Zimmermann, T.
- Affiliations
- University of Zurich (CH)
- University of British Columbia (CA)
- Microsoft (United States) (US)
- Venue
- Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2014-11-11
- Pages
- 19-29
- OpenAlex
- W2010985317
- Cited by
- 224
- References
- 44
- Citations by year
- 2026: 12 · 2025: 23 · 2024: 16 · 2023: 18 · 2022: 12 · 2021: 26 · 2020: 24 · 2019: 25 · 2018: 15 · 2017: 19 · 2016: 16 · 2015: 17 · 2014: 1
- FWCI
- 15.07
- Type
- conference paper
- Language
- en
- Open access
- green
- www.zora.uzh.ch
- Locations
- ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) (publishedVersion)
- Zurich Open Repository and Archive (University of Zurich) (acceptedVersion, other-oa)
- Zurich Open Repository and Archive (University of Zurich)
- Funders
- Natural Sciences and Engineering Research Council of Canada
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Keywords
- software productivity, developer perceptions, task switching, context switching, interruptions, productivity improvement, developer support tools, best practice sharing, retrospection
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
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.