发表机构
Lund University; Ericsson AB; Mälardalen University; Carleton University; KTH Royal Institute of Technology（隆德大学; 爱立信公司; 马尔默达尔大学; 卡尔顿大学; 皇家理工学院）
机构由 AI 辅助整理，请以论文原文为准。AI 中文总结
本研究通过瑞典电信公司12名开发者的访谈，揭示AI开发工具协调部署中管理层与开发者期望差距及感知风险的重要性，指出工具价值受组织期望、系统规模和技能影响。
AI 中文摘要
AI赋能的软件开发工具（AI开发工具）正在强烈的生产力提升预期下被工业界采用，然而开发者对此类部署的经验却鲜有探索。组织在信息不全的情况下投入预算、评估员工并修订实践，因为现有证据基础主要是工具评估、生产力指标和调查，缺乏对正在进行的、协调式部署的定性实地记录。我们报告了一项在瑞典一家大型电信公司进行的AI开发工具协调式部署的案例研究，调查开发者如何体验该部署以及他们预期自己的职业将如何变化。我们对三个地点的12名软件专业人士进行了半结构化访谈，采用过程编码和主题分析进行分析，并通过扩展技术接受模型（TAM2）作为事后分析视角进行解读。我们关于用例、生产力、挫败感和工具局限性的发现证实了先前的调查研究。除证实外，访谈还揭示了管理层与开发者之间的期望差距，该差距映射到TAM2的主观规范和自愿性构念上，并表明参与者高度重视感知风险，这是TAM2及类似接受模型未代表的因素。AI开发工具表现为有帮助但有缺陷的助手，其价值受组织期望、系统规模和开发者技能的影响。
英文摘要
AI-enabled software development tools (AI-devtools) are being industrially adopted under strong expectations of productivity gains, yet developers' experiences of such roll-outs are underexplored. Organizations commit budgets, evaluate staff, and revise practice on a partial picture, since the evidence base is mainly tool evaluations, productivity metrics, and surveys, with few qualitative in-situ accounts of ongoing, coordinated roll-outs. We report a case study of a coordinated roll-out of AI-devtools at a large Swedish telecommunications company, investigating how developers experience the roll-out and how they anticipate their profession will change. We conducted semi-structured interviews with 12 software professionals across three sites, analyzed with process coding and thematic analysis, and interpreted through the extended Technology Acceptance Model (TAM2) as a post-hoc analytical lens. Our findings on use cases, productivity, frustrations, and tool limitations corroborate prior survey work. Beyond corroboration, the interviews surface a management-developer expectation gap that maps onto the TAM2 constructs of subjective norm and voluntariness, and show that participants weigh perceived risk heavily, a factor that TAM2 and similar acceptance models do not represent. AI-devtools emerge as helpful but fallible assistants whose value is shaped by organizational expectations, system scale, and developers' skills.
