Papers for

software development managers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

AI use varies widely and policy awareness is low in software teams

Uneven Self-Reported AI Use: An Embedded Case Study Across Eleven Teams in a Software Organization

Abstract: This paper presents a descriptive, embedded single-case study examining self-reported AI use within a software organization. The study draws on 98 structured interview records collected across 11 teams, using ten standardized team-level instruments (n = 65) and one instrument with distinct response anchors (n = 33). Among respondents assessed using standardized instruments, 36 of 65 (55.4%) reported AI-use frequency scores of 4 or 5 on a five-point scale. Team-level proportions varied from 20.0% (1/5) to 71.4% (5/7). A record-level cross-tabulation revealed limited awareness or understanding of organizational AI policies across both frequency groups: 86.1% (31/36) of respondents scoring 4-5 and 96.6% (28/29) of those scoring 0-3 reported either no policy awareness or uncertainty about policy details. In the group assessed using the distinct instrument, 31 of 33 respondents (93.9%) scored 4 or 5. Although the pooled proportion reached 68.4% (67/98), differences in response anchors limit direct comparability, making the standardized-instrument results the primary analytical reference. Interviewer-recorded observations provide qualitative context on reported practices and constraints but do not support estimates of their prevalence or causal explanations for differences in AI-use frequency. The findings characterize AI-use patterns and policy awareness within the interviewed sample, without supporting inferences about organization-wide adoption, policy compliance, or the effectiveness of AI use. The study contributes an empirically grounded organizational case and an explicit account of the methodological boundaries of cross-team comparisons using heterogeneous interview instruments.

Tue 10 NovHuman-Computer InteractionComputers and Society
The gist
The paper studies how often software teams say they use AI tools and how aware they are of company policies about AI. It finds that while some teams frequently use AI, others use it much less. Most team members don’t know much about their organization’s AI policies. The paper does not claim the results apply to the whole company or explain why AI use differs. It mainly gives a careful snapshot of AI use and understanding in these teams.
Open → 2611.14154v1

Deliberate pacing balances human oversight and autonomous software development

Deliberate Pacing for Human Oversight in Agentic Software Development

Abstract: Agentic AI increasingly enables software development activities to proceed without continuous human involvement. While this autonomy may accelerate development, it also raises questions about when developers can meaningfully oversee software development done by agents. We propose deliberate pacing: intentionally adjusting when and how autonomous development proceeds to preserve opportunities for meaningful oversight. Drawing on an exploratory multivocal literature review of 20 sources, we identify three factors motivating this vision: changing relative costs of human involvement, the timing of oversight opportunities, and interdependencies between pacing decisions across the software development life cycle. We argue that neither uninterrupted autonomy nor frequent human intervention is universal. Instead, pacing should balance opportunities to understand and influence consequential decisions against costs in human attention, development time, and rework. We outline a research agenda to investigate when deliberate pacing is beneficial, how intervention timing affects oversight, and how pacing decisions interact across development activities.

Fri 6 NovSoftware Engineering
The gist
Software development is increasingly done by AI agents working on their own. This raises the problem of how and when humans can effectively check the work and make decisions. The authors propose a strategy called deliberate pacing, where the speed and timing of autonomous development are controlled intentionally. This approach aims to keep chances for human oversight meaningful without slowing down development too much or causing extra work. They identify factors like timing of review, cost of human attention, and dependencies across development stages that affect how pacing should be done.
Open → 2611.09550v1

AI systems produce varying economic value per unit of energy used

Joules-to-GDP: How Much Economic Value Do AI Systems Produce per Unit of Energy?

Abstract: An AI system can produce more economically valuable work while delivering less value for the energy it consumes. We therefore ask: How much economic value does an AI system create per unit of energy consumed? We formalize economic value in two ways: (1) net dollar value, the output's dollar value minus AI-system execution cost, and (2) time saving, the expert's completion time minus the AI system's completion time. Dividing each by measured end-to-end energy yields Net Value per Joule (NVJ) and Time Saving per Joule (TSJ), reported in USD/MJ and hours/MJ. We study 220 public GDPval tasks across 44 occupations, serving five open-weight models locally and evaluating four accelerator types. First, the occupation groups where AI systems succeed most often, deliver the greatest dollar value, or save the most time do not necessarily provide the greatest economic return per joule. For example, among the tested tasks, engineering work delivers about 10% more net dollar value per task than software development. Yet software development delivers about 27% more net value per joule. Second, GLM 5.2 delivers the highest average net dollar value, at $72.27 per task using 0.430 MJ, equivalent in energy to about four hours of active laptop use. By contrast, Gemma 4 31B delivers 56% of that net dollar value using just 23% of the energy, achieving approximately 2.5 times the NVJ and 2.8 times the TSJ. Third, across four single-accelerator deployments, Qwen3.6-27B's NVJ varies by a factor of 4.32 and TSJ by 9.27, with B200 leading both. Additionally, one and eight H100s deliver similar net dollar value, but eight reduce completion time by 22% at 3.24 times the energy. Our framework makes output value and expert time saving under an energy budget explicit objectives for improving models, accelerators, and software, while offering a new basis for assessing AI's potential economic effect on occupational work.

Thu 22 OctMachine Learning
The gist
AI systems can do valuable work but use energy, so it matters how much economic value they produce for each unit of energy consumed. The authors measure this by comparing the money value and time saved by AI against the energy it uses. They find that some AI tasks and models provide more value per energy unit than others, like software development offering better returns than engineering. They also show different AI models and hardware setups vary greatly in energy efficiency and speed. This work helps guide future improvements to AI in terms of energy use and economic impact.
Open → 2610.30858v1

Software architectural degradation measured widely but fixes lag behind

Architectural Degradation: How to Measure and to Remediate

Abstract: Context. Architectural degradation undermines software maintainability, evolvability, and quality. However, existing research remains fragmented across measurement approaches, metrics, tools, and remediation strategies, limiting our understanding of how these elements relate across the degradation lifecycle. Aim. We consolidate the state of the art on architectural degradation by examining how researchers measure it, which metrics and tools support its assessment, and how existing approaches address remediation. Method. We conducted a Multivocal Literature Review of 284 peer-reviewed and grey-literature studies. We supported screening, data extraction, and classification with a locally executed LLM-assisted pipeline combining Retrieval-Augmented Generation, multi-model validation, and human adjudication. We then analyzed the resulting taxonomies and their cross-dimensional relationships. Results and Conclusions. We identified 277 measurement approaches, 357 metrics, 238 tools, and 395 remediation approaches. Research strongly concentrates on static and structural analysis, structural metrics, and detection-oriented tools. In contrast, remediation spans heterogeneous code-level, architectural, and organizational interventions and shows substantially less consolidation. Overall, the field has developed a mature diagnostic apparatus but has made less progress in connecting degradation detection with effective remediation. Our results provide a structured view of the available techniques and identify the diagnosis-remediation gap as a key direction for future research.

Thu 1 OctSoftware Engineering
The gist
Architectural degradation in software makes it harder to maintain and improve programs over time. The authors examined hundreds of studies to see how this problem is measured, what tools and metrics are used, and how people try to fix it. They found many ways to detect degradation but fewer agreed-upon methods to fix it effectively. This means while developers can spot problems well, there is less clear guidance on how to repair architectural issues. Their work highlights that connecting detection to practical fixes is an important direction for future research.
Open → 2610.01611v1

Developers’ cognitive load varies with genAI use and task context

Beyond Productivity: Measuring Developers' Cognitive Load During GenAI-Supported Software Development

Abstract: Generative AI (GenAI) is changing software development workflows and how developers work. Industry evaluations of GenAI adoption often monitor productivity gains, usage, and output quality, but limited attention is paid to the interaction experience and cognitive load of the actual adopters and drivers of GenAI technology - the software developers. Understanding whether GenAI changes or shifts developers' cognitive demands during everyday development is important for a developer-centered evaluation of GenAI-supported software development. It can inform organizations in designing and evaluating effective AI-supported workflows. In this work, we study how GenAI use and task context relate to professional developers' perceived cognitive load and whether wearable-derived physiological characteristics provide additional information beyond this context. In a four-day industrial field study at two SAP sites, 21 developers documented their tasks, task duration, GenAI use, and perceived cognitive load while wearing an EmbracePlus wristband. The results show that perceived cognitive load is associated with both GenAI use and task context, while physiological measures provide only limited additional information. These findings suggest that developers' perceived cognitive load during GenAI-supported software development should be evaluated in relation to the concrete work context, with wearable physiological data used as complementary rather than standalone information.

Tue 29 SeptSoftware EngineeringHuman-Computer Interaction
The gist
Understanding how using generative AI affects software developers’ mental effort is important as AI tools become common. The authors studied 21 developers over four days, tracking their tasks, use of AI, and how hard they felt their work was. They also measured physical signals with wristbands but found these added little extra insight. The study shows that how demanding a developer’s work feels depends mainly on the kind of task and whether AI is used, with physical data serving only as a small extra clue. This helps focus on the real work context when assessing AI’s impact on developers.
Open → 2609.37645v1

Embedded software firms prepare for AI agents to reshape teams and tasks

Developing a Roadmap to an AI-first Organization: A Case Study in Embedded Software Development

Abstract: The emergence of AI agents is expected to reshape software engineering by moving beyond AI as assistants towards systems capable of planning, executing, and evaluating development tasks with increasing autonomy. This transition is particularly significant for embedded software organizations, where strict requirements for quality, traceability, verification, and long-term maintainability often apply. This paper presents a case study of a large embedded systems company and its transition toward becoming an AI-first organization. Through a mixed method, we analyzed data collected from a semi-structured workshop with 40 participants, including scrum masters, architects, management, and product owners. The findings show that the participants expect agentic AI to affect team structure, required competencies, organizational strategies, and developers' roles within the organization. Based on these findings, the paper discusses implications for federated AI team formation, human-in-the-loop practices in such an organization, and the sustainable adoption of AI agents in embedded software engineering. We also present a concrete roadmap for the organization towards becoming an AI-first organization.

Fri 25 SeptSoftware EngineeringArtificial Intelligence
The gist
AI tools are becoming more than just helpers for programmers—they are starting to take on tasks like planning and checking software development work on their own. This change is important for companies that build software embedded in devices, which require very careful quality checks and long-term support. The authors studied a large company moving to put AI agents at the center of its work. They found that AI will change how teams are structured, what skills people need, and how organizations plan their work, and they created a detailed plan to help the company become AI-first.
Open → 2609.30863v1

Software development adapts itself as projects and conditions change

Rethinking Software Development as a Self-Adaptive Socio-Technical System

Abstract: Agentic AI is expanding across various software engineering activities, yet human-agent organization is typically treated as fixed, which is problematic because development configurations may become suboptimal as development context evolves. We propose viewing software development as a self-adaptive socio-technical system in which both the software project and the development configuration (participants, responsibilities, authority, information, and verification) adapt as goals, evidence, uncertainty, and risk evolve. This yields two coupled forms of adaptation: evolving the software and reconfiguring how subsequent engineering is performed. We illustrate the idea with a proof of concept, outlining challenges and future plans.

Fri 11 SeptSoftware Engineering
The gist
Software development teams usually follow a set plan for who does what, but this plan can stop working well when things change. The authors suggest thinking about software development as a living system that changes both the software and how the team works as new goals, information, and risks appear. This means the people and their roles in the development can adjust alongside the software itself. They provide an initial example of how this idea could work and discuss challenges ahead.
Open → 2609.13461v1

Framework assesses software business risks and strengths with ai

AI Exposure and AI Resilience: A Two-Dimensional Assessment Framework for Software and Software-Based Business Model

Abstract: Artificial intelligence is changing both software production and the economics of software-based business models. Classical technology due diligence mainly examines technical properties such as architecture, scalability, and technical debt. These criteria do not fully capture how AI can affect a company's value proposition, competitive position, margins, or access to customers. This paper develops Artificial Intelligence Exposure and Resilience (AI-ER) as a two-dimensional assessment framework. AI exposure describes the pressure for change that AI creates for a business model. AI resilience describes the company's ability to absorb that pressure, adapt to changed conditions, and use AI in an economically viable way. Metrics for both dimensions are derived from current AI capabilities, their deployment conditions, and relevant research on business models and organizational adaptability. The model keeps exposure and resilience separate and adds an explicit assessment of evidence quality and confidence. It can be applied first with public information and later refined with internal evidence. The result is a traceable company profile that supports comparison without concealing uncertainty in the underlying evidence. The paper also specifies an initial score logic and a procedure for empirical validation.

Thu 10 SeptArtificial Intelligence
The gist
Software companies face challenges and opportunities from artificial intelligence (AI) that go beyond usual technical checks. The authors created a tool called AI Exposure and Resilience (AI-ER) to measure how much AI pressures a business to change and how well the company can handle those changes. This two-part tool looks separately at the risks from AI and the company’s ability to adapt, using public and internal data. It aims to help compare companies clearly while showing how strong the evidence is for each assessment. The paper also suggests ways to score companies and plans to test the tool in real settings.
Open → 2609.11321v1