Rethinking Productivity in Software Engineering

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit

Rethinking Productivity in Software Engineering

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit

Happiness and the productivity of software engineers

Software companies and startups often follow the idea of flourishing happiness among developers. Perks, playground rooms, free breakfast, remote office options, sports facilities near the companies, company retreats, you name it. The rationale is that happy developers should be more productive and also retained. But is it the case that happy software engineers are more productive? Moreover, are perks the way to go to make developers happy? Are developers happy at all? What are the consequences of unhappiness among software engineers? These questions are important to ask both from the perspective of productivity and from the perspective of sustainable software development and well-being in the workplace. Managers, team leaders, as well as team members should be interested in these concerns. This chapter provides an overview of our studies on the happiness of software developers. You will learn why it is important to make software developers happy, how happy they really are, what makes them unhappy, and what is expected regarding happiness and productivity while developing software.Comment: 12 pages, 2 figures. To appear in Rethinking Productivity in Software Engineering, edited by Caitlin Sadowski and Thomas Zimmermann. arXiv admin note: text overlap with arXiv:1707.0043

Improving productivity through corporate hackathons: A multiple case study of two large-scale agile organizations

Software development companies organize hackathons to encourage innovation. Despite many benefits of hackathons, in large-scale agile organizations where many teams work together, stopping the ongoing work results in a significant decrease in the immediate output. Motivated by the need to understand whether and how to run hackathons, we investigated how the practice affects productivity on the individual and organizational levels. By mapping the benefits and challenges to an established productivity framework, we found that hackathons improve developers' satisfaction and well-being, strengthen the company culture, improve performance (as many ideas are tested), increase activity (as the ideas are developed quickly), and improve communication and collaboration (because the social network is strengthened). Addressing managerial concerns, we found that hackathons also increase efficiency and flow because people learn to complete work and make progress quickly, and they build new competence. Finally, with respect to virtual hackathons we found that developers work more in isolation because tasks are split between team members resulting in less collaboration. This means that some important, expected hackathon values in virtual contexts require extra effort and cannot be taken for granted

Pair Programming Practiced in Hybrid Work

Pair programming (PP) has been a widespread practice for decades and is known for facilitating knowledge exchange and improving the quality of software. Many agilists advocated the importance of collocation, face-to-face interaction, and physical artifacts incorporated in the shared workspace when pairing. After a long period of forced work-from-home, many knowledge workers prefer to work remotely two or three days per week, which is affecting practices such as PP. In this revelatory single-case study, we aimed to understand how PP is practiced during hybrid work when team members alternate between on-site days and working from home. We collected qualitative and quantitative data through 11 semi-structured interviews, observations, feedback sessions, and self-reported surveys. The interviewees were members of an agile software development team in a Norwegian fintech company. The results presented in this paper indicate that PP can be practiced through on-site, remote, and mixed sessions, where the mixed mode seems to be the least advantageous. The findings highlight the importance of adapting the work environment to suit individual work mode preferences when it comes to PP. In the future, we will build on these findings to explore PP in other teams and organizations practicing hybrid work

Digital intrusions or distraction at work and work-Life conflict

Internet usage for non-work activities during work hours is an increasingly common concern among management scholars and practitioners as well as for employees, particularly in relation to its impact on work-life conflict and individual well-being. Drawing on memory for goals theory, this study investigates the distinction between digital intrusions and digital interruptions during work and their concomitant impact on work-life conflict. Using a set-theoretic approach to analyse data gathered from information technology (IT) professionals in Germany and Australia, we explain how a 2 * 2 matrix comprising non-work online messaging, or personal digital communication, during work and intrusion contributes to work-life conflict. A key finding is that employees reported work-life conflict only if they perceived private messaging as a source of intrusion rather than as a distraction. From a practical perspective, this finding suggests that employers may provide employees with micro-breaks to attend to perceived intrusions and thus reduce sources of work-life conflict. Contributions and suggestions for future studies are discussed

Developers’ Diverging Perceptions of Productivity

To overcome the ever-growing demand for software, software development organizations strive to enhance the productivity of their developers. But what does productivity mean in the context of software development? A substantial amount of work on developer productivity has been undertaken over the past four decades. The majority of this work considered productivity from a top-down perspective (the manager view) in terms of the artifacts and code created per unit of time. Common examples of such productivity measures are the lines of source code modified per hour, the resolution time for modification requests, or function points created per month. These productivity measures focus on a single, output-oriented factor for quantifying productivity, and do not take into account developers’ individual work roles, practices and other factors that might affect their productivity, such as work fragmentation, the tools used, or the work/office environment. In our research, we investigated how productivity could be quantified from the bottom-up, following a mixed-methods approach that involved more than 800 software developers. By investigating developers’ individual productivity, it is possible to better understand the individual work habits and patterns, how they relate to the productivity perceptions and also which factors are most relevant for a developer’s productivity

Phase 2: Investigation of Leading Indicators for Systems Engineering Effectiveness in Model-Centric Programs

Acquisition Research Program Sponsored Report SeriesSponsored Acquisition Research & Technical ReportsThis technical report summarizes the work conducted by Massachusetts Institute of Technology under contract award HQ0034-20-1-0008 during the performance period May 22, 2020 – July 31, 2021. Digital engineering transformation changes the practice of systems engineering, and drives the need to re-examine how engineering effectiveness is measured and assessed. Early engineering metrics were primarily lagging measures. More recently leading indicators have emerged that draw on trend information to allow for more predictive analysis of technical and programmatic performance of the engineering effort. By analyzing trends (e.g., requirements volatility) in context of the program’s environment and known factors, predictions can be forecast on the outcomes of certain activities (e.g., probability of successfully passing a milestone review), thereby enabling preventative or corrective action during the program. Augmenting a companion research study under contract HQ0034-19-1-0002 on adapting and extending existing systems engineering leading indicators, this study takes a future orientation. This report discusses how base measures can be extracted from a digital system model and composed as leading indicators. An illustrative case is used to identify how the desired base measures could be obtained directly from a model-based toolset. The importance of visualization and interactivity for future leading indicators is discussed, especially the potential role of visual analytics and interactive dashboards. Applicability of leading edge technologies (automated collection, visual analytics, augmented intelligence, etc.) are considered as advanced mechanisms for collecting and synthesizing measurement data from digital artifacts. This research aims to provide insights for the art of the possible for future systems engineering leading indicators and their use in decision-making on model-centric programs. Several recommendations for future research are proposed extending from the study.Approved for public release; distribution is unlimited.Approved for public release; distribution is unlimited

Colliding Identities During COVID-19: Identifying and Addressing the Challenges of Being an Academic Mother During a Global Pandemic

Academic workloads require a careful balance of teaching, research, supervision, and administrative responsibilities. Being an academic parent adds an additional level of responsibility to this, which has traditionally been successfully managed with organisation, careful planning and support. For many academic parents the Covid-19 pandemic disrupted this carefully curated balance, forcing them to work from home while also dealing with the loss of childcare and the requirement to provide homeschooling. The pre-existing gender disparity in childcare and housework was exacerbated by lockdown, with a disproportionate impact on academic mothers who were often forced to take on additional childcare and housework responsibilities, alongside remote schooling. The gender disparity further affected job stability, with women losing a greater number of paid working hours during the pandemic and having greater employment instability. This article reflects upon the impact of gender disparity in academic parents during the Covid-19 pandemic, and considers potential barriers to productivity and progression, including the role of interruptions, delivering sensitive materials in a workspace shared with children and technological challenges

An Eye Gaze Heatmap Analysis of Uncertainty Head-Up Display Designs for Conditional Automated Driving

This paper reports results from a high-fidelity driving simulator study (N=215) about a head-up display (HUD) that conveys a conditional automated vehicle's dynamic "uncertainty" about the current situation while fallback drivers watch entertaining videos. We compared (between-group) three design interventions: display (a bar visualisation of uncertainty close to the video), interruption (interrupting the video during uncertain situations), and combination (a combination of both), against a baseline (video-only). We visualised eye-tracking data to conduct a heatmap analysis of the four groups' gaze behaviour over time. We found interruptions initiated a phase during which participants interleaved their attention between monitoring and entertainment. This improved monitoring behaviour was more pronounced in combination compared to interruption, suggesting pre-warning interruptions have positive effects. The same addition had negative effects without interruptions (comparing baseline & display). Intermittent interruptions may have safety benefits over placing additional peripheral displays without compromising usability.Comment: Accepted for publication at the 2024 ACM Conference on Human Factors in Computing Systems (CHI'24