paperbot · PL 论文追踪

全部论文 待读 收藏

P2 An Empirical Study of the Content and Quality of Sprint Retrospectives in Undergraduate Team Software Projects

本科团队软件项目中冲刺回顾(Sprint Retrospective)的内容与质量:一项实证研究
ICSE Proceedings of the 46th International Conference on Software Engineering: Software Engineering Education and Training2024匹配度 0/10 · 该论文研究本科团队敏捷冲刺回顾的内容与质量,属于软件工程教育/团队协作实证研究,与用户关注的静态分析、Agentic 程序、LLM 与程序分析/形式化验证交叉、浮点或贝叶斯程序分析等方向均无直接关联。引用 6 inbox
Christopher Hundhausen, Phillip Conrad, Ahsun Tariq, Surya Pugal, Brian Zamora Flores
crossref: 2026-09-12dblp: 2026-09-12

AI 速览

一句话:通过分析32个本科团队963条冲刺回顾陈述,揭示学生反思的内容、质量及团队差异。

该研究关注本科团队软件项目中的冲刺回顾:学生反思什么、质量如何、团队间有何差异。作者对两所北美大学四门课程中32个团队(182名学生)的963条回顾陈述进行内容分析,并按是否为停止、继续或开始某策略提供理由评估质量。结果显示,团队最常反思工作、沟通与协作;近三分之一聚焦一般工作实践,近一半聚焦软件开发生命周期具体领域,尤以 pull request、issue 和编码/测试/调试为主。仅13%的反思为策略提供理由;团队间内容与质量差异显著。作者与已有学术和工业研究比较,并讨论对软件工程教育的启示。

问题
研究本科团队软件项目中冲刺回顾的内容与质量:学生反思什么、反思质量如何、以及团队间差异。
方法
对两所北美大学四门软件工程课程中32个团队(182名学生)的963条回顾陈述进行内容分析,并评估策略是否有理由支撑。
评估
发现团队最常反思工作、沟通与协作,仅13%为策略提供理由,且团队间内容与质量差异显著;与已有学术/工业研究比较并讨论教育启示。
原文摘要(Abstract)

The retrospective, or retro, is a fundamental component of the Agile process, widely used in both software engineering courses and industry. In a retro, teams come together at the end of a sprint to reflect on their team's performance. We conducted an empirical study to explore three research questions concerning retros in undergraduate team projects: (1) What do students reflect on? (2) What is the quality of their reflections? (3) How do teams' retros vary in terms of content and quality? Our study analyzed a corpus of 963 statements documented in the retros of 32 undergraduate software teams (n = 182 students) enrolled in four software engineering courses at two North American universities. A content analysis revealed that teams reflected most often on their work, communication, and collaboration practices. Nearly a third of teams' reflections focused on their general work practices, while nearly half focused on specific areas of the software development lifecycle-most prominently, pull requests, issues, and coding/testing/debugging. An analysis of the quality of teams' retro reflections showed that only 13% provided justification for a strategy to be stopped, continued, or started. An analysis of team-by-team results indicated significant differences in teams' retro content and quality. We compare these results to previous studies of retros in academia and industry, and consider their implications for software engineering education.

链接与引用

DOI 原文 · PDF(开放获取) · DBLP

BibTeX
@inproceedings{HundhausenCTPF24,
  title = {An Empirical Study of the Content and Quality of Sprint Retrospectives in Undergraduate Team Software Projects},
  author = {Christopher Hundhausen and Phillip Conrad and Ahsun Tariq and Surya Pugal and Brian Zamora Flores},
  booktitle = {ICSE},
  year = {2024},
  doi = {10.1145/3639474.3640074}
}