paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Eagle: a team practices audit framework for agile software development

Eagle:面向敏捷软件开发的团队实践审计框架
FSE Proceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering2019匹配度 0/10 · 该论文研究敏捷/XP 团队实践遵从度的监测与仪表盘反馈,属于软件工程过程与团队协作分析,与用户关注的程序静态分析、LLM/Agent、浮点程序分析或贝叶斯程序分析均无直接关联。引用 8 inbox
Alejandro Guerrero, Rafael Fresno, An Ju, Armando Fox, Pablo Fernandez, Carlos Muller, Antonio Ruiz-Cortés
crossref: 2026-09-12

AI 速览

一句话:提出 Eagle 框架,利用工具数据监测敏捷/XP 团队实践遵从度并提供仪表盘反馈。

论文针对敏捷/XP 团队实践中难以持续监测的问题,提出将团队实践(Team Practice)类比为服务等级目标(SLO)来表达,并改造原本用于监测和可视化 SLA 遵从度的系统,构建 Eagle 审计框架。Eagle 消费 GitHub、Pivotal Tracker 等常用工具产生的“数据尾气”,分析并展示各团队对估算、分支与拉取请求、站会、回顾等实践的遵从情况,向团队和教练提供仪表盘。作者在四轮冲刺的软件工程课程中对二十个学生团队进行了初步定性评估,发现与以往采用敏捷/XP 方法的经验相比,团队实践遵从度有所提升,学生对团队实践的自我评价也更积极。

问题
敏捷/XP 团队需遵循估算、分支与拉取请求、站会、回顾等实践,但团队和教练缺乏持续、自动化的监测手段。
方法
将团队实践表达为类似 SLO 的可度量目标,并改造 SLA 监测与可视化系统,从 GitHub 和 Pivotal Tracker 等工具的数据尾气中分析实践遵从度并生成仪表盘。
评估
在四轮冲刺的软件工程课程中部署给二十个学生团队,进行初步定性研究;结果显示实践遵从度提升,学生自我评价更积极(与以往经验相比)。
原文摘要(Abstract)

Agile/XP (Extreme Programming) software teams are expected to follow a number of specific practices in each iteration, such as estimating the effort (”points”) required to complete user stories, properly using branches and pull requests to coordinate merging multiple contributors’ code, having frequent ”standups” to keep all team members in sync, and conducting retrospectives to identify areas of improvement for future iterations. We combine two observations in developing a methodology and tools to help teams monitor their performance on these practices. On the one hand, many Agile practices are increasingly supported by web-based tools whose ”data exhaust” can provide insight into how closely the teams are following the practices. On the other hand, some of the practices can be expressed in terms similar to those developed for expressing service level objectives (SLO) in software as a service; as an example, a typical SLO for an interactive Web site might be ”over any 5-minute window, 99% of requests to the main page must be delivered within 200ms” and, analogously, a potential Team Practice (TP) for an Agile/XP team might be ”over any 2-week iteration, 75% of stories should be ’1-point’ stories”. Following this similarity, we adapt a system originally developed for monitoring and visualizing service level agreement (SLA) compliance to monitor selected TPs for Agile/XP software teams. Specifically, the system consumes and analyzes the data exhaust from widely-used tools such as GitHub and Pivotal Tracker and provides team(s) and coach(es) a ”dashboard” summarizing the teams’ adherence to various practices. As a qualitative initial investigation of its usefulness, we deployed it to twenty student teams in a four-sprint software engineering project course. We find an improvement of the adherence to team practice and a positive students’ self-evaluations of their team practices when using the tool, compared to previous experiences using an Agile/XP methodology. The demo video is located at https://youtu.be/A4xwJMEQh9c and a landing page with a live demo at https://isa-group.github.io/2019-05-eagle-demo/.

链接与引用

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

BibTeX
@inproceedings{paperbot5131,
  title = {Eagle: a team practices audit framework for agile software development},
  author = {Alejandro Guerrero and Rafael Fresno and An Ju and Armando Fox and Pablo Fernandez and Carlos Muller and Antonio Ruiz-Cortés},
  booktitle = {FSE},
  year = {2019},
  doi = {10.1145/3338906.3341181}
}