Collaborative experience between scientific software projects using Agile Scrum development
Collaborative experience between scientific software projects using Agile Scrum development
复制标题
DOI：
10.1002/spe.3120
复制
发表时间：
2021-01
期刊：
影响因子：
--
通讯作者：
Amanda L. Baxter;S. BenZvi;W. Bonivento;Adam Brazier;Michael Clark;A. Coleiro;D. Collom;M. Colomer-Molla;B. Cousins;Aliwen Delgado Orellana;D. Dornic;V. Ekimtcov;Shereen ElSayed;A. Gallo Rosso;P. Godwin;S. Griswold;A. Habig;Remington Hill;S. Horiuchi;D. A. Howell;Margaret W. G. Johnson;M. Jurić;J. Kneller;A. Kopec;C. Kopper;V. Kulikovskiy;M. Lamoureux;R. Lang;S. Li;M. Lincetto;Lindy Lindstrom;M. Linvill;C. McCully;J. Migenda;D. Milisavljevic;S. Nelson;R. Novoseltseva;E. O’Sullivan;D. Petravick;B. Pointon;N. Raj;A. Renshaw;J. Rumleskie;T. Sonley;R. Tapia;J. Tseng;C. Tunnell;G. Vannoye;C. Vigorito;C. Virtue;Christopher N. Weaver;K. Weil;L. Winslow;R. Wolski;Xun-Jie Xu;Y. Xu
中科院分区：
文献类型：
--
作者：
Amanda L. Baxter;S. BenZvi;W. Bonivento;Adam Brazier;Michael Clark;A. Coleiro;D. Collom;M. Colomer-Molla;B. Cousins;Aliwen Delgado Orellana;D. Dornic;V. Ekimtcov;Shereen ElSayed;A. Gallo Rosso;P. Godwin;S. Griswold;A. Habig;Remington Hill;S. Horiuchi;D. A. Howell;Margaret W. G. Johnson;M. Jurić;J. Kneller;A. Kopec;C. Kopper;V. Kulikovskiy;M. Lamoureux;R. Lang;S. Li;M. Lincetto;Lindy Lindstrom;M. Linvill;C. McCully;J. Migenda;D. Milisavljevic;S. Nelson;R. Novoseltseva;E. O’Sullivan;D. Petravick;B. Pointon;N. Raj;A. Renshaw;J. Rumleskie;T. Sonley;R. Tapia;J. Tseng;C. Tunnell;G. Vannoye;C. Vigorito;C. Virtue;Christopher N. Weaver;K. Weil;L. Winslow;R. Wolski;Xun-Jie Xu;Y. Xu
为科学界开发可持续的软件需要软件工程和领域科学方面的专业知识。由于科学软件的独特需求，科学界软件工程实践的资源不足，以及为不断发展的科学环境开发的复杂性，这可能是具有挑战性的。虽然开源软件可以部分解决这些问题，但它可能会引入复杂的依赖关系并延迟开发。如果科学家和软件开发人员合作，这些问题可以减少。我们提出了一个案例研究，其中来自超新星预警系统的科学家与来自多信使天体物理学项目的可扩展网络基础设施的软件开发人员合作。这种合作解决了开源软件开发的困难，但也给每个团队带来了额外的风险。对于科学家来说，他们担心依赖外部系统和在开发过程中缺乏控制。对于开发者来说，在维护核心开发的同时支持一个用户组是有风险的。通过与开发人员正在进行的敏捷Scrum流程并行创建第二个敏捷Scrum框架，这些问题得到了缓解。这种敏捷协作促进了沟通，确保科学家在开发中发挥积极作用，并允许开发人员评估和实现科学家的软件需求。合作为每个小组提供了好处：科学家通过使用现有的平台来驱动他们的开发，开发人员利用科学家的用例来改进他们的系统。这个案例研究表明，科学家和软件开发人员可以通过协作来避免科学计算问题，敏捷Scrum方法可以解决紧急问题。
Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.