Collaborative Experience between Scientific Software Projects using Agile Scrum Development. (arXiv:2101.07779v3 [cs.SE] UPDATED)

Collaborative Experience between Scientific Software Projects using Agile Scrum Development. (arXiv:2101.07779v3 [cs.SE] UPDATED)
<a href="http://arxiv.org/find/cs/1/au:+Baxter_A/0/1/0/all/0/1">A. L. Baxter</a>, <a href="http://arxiv.org/find/cs/1/au:+BenZvi_S/0/1/0/all/0/1">S. Y. BenZvi</a>, <a href="http://arxiv.org/find/cs/1/au:+Bonivento_W/0/1/0/all/0/1">W. Bonivento</a>, <a href="http://arxiv.org/find/cs/1/au:+Brazier_A/0/1/0/all/0/1">A. Brazier</a>, <a href="http://arxiv.org/find/cs/1/au:+Clark_M/0/1/0/all/0/1">M. Clark</a>, <a href="http://arxiv.org/find/cs/1/au:+Coleiro_A/0/1/0/all/0/1">A. Coleiro</a>, <a href="http://arxiv.org/find/cs/1/au:+Collom_D/0/1/0/all/0/1">D. Collom</a>, <a href="http://arxiv.org/find/cs/1/au:+Colomer_Molla_M/0/1/0/all/0/1">M. Colomer-Molla</a>, <a href="http://arxiv.org/find/cs/1/au:+Cousins_B/0/1/0/all/0/1">B. Cousins</a>, <a href="http://arxiv.org/find/cs/1/au:+Orellana_A/0/1/0/all/0/1">A. Delgado Orellana</a>, <a href="http://arxiv.org/find/cs/1/au:+Dornic_D/0/1/0/all/0/1">D. Dornic</a>, <a href="http://arxiv.org/find/cs/1/au:+Ekimtcov_V/0/1/0/all/0/1">V. Ekimtcov</a>, <a href="http://arxiv.org/find/cs/1/au:+ElSayed_S/0/1/0/all/0/1">S. ElSayed</a>, <a href="http://arxiv.org/find/cs/1/au:+Rosso_A/0/1/0/all/0/1">A. Gallo Rosso</a>, <a href="http://arxiv.org/find/cs/1/au:+Godwin_P/0/1/0/all/0/1">P. Godwin</a>, <a href="http://arxiv.org/find/cs/1/au:+Griswold_S/0/1/0/all/0/1">S. Griswold</a>, <a href="http://arxiv.org/find/cs/1/au:+Habig_A/0/1/0/all/0/1">A. Habig</a>, <a href="http://arxiv.org/find/cs/1/au:+Horiuchi_S/0/1/0/all/0/1">S. Horiuchi</a>, <a href="http://arxiv.org/find/cs/1/au:+Howell_D/0/1/0/all/0/1">D. A. Howell</a>, <a href="http://arxiv.org/find/cs/1/au:+Johnson_M/0/1/0/all/0/1">M. W. G. Johnson</a>, <a href="http://arxiv.org/find/cs/1/au:+Juric_M/0/1/0/all/0/1">M. Juric</a>, <a href="http://arxiv.org/find/cs/1/au:+Kneller_J/0/1/0/all/0/1">J. P. Kneller</a>, <a href="http://arxiv.org/find/cs/1/au:+Kopec_A/0/1/0/all/0/1">A. Kopec</a>, <a href="http://arxiv.org/find/cs/1/au:+Kopper_C/0/1/0/all/0/1">C. Kopper</a>, <a href="http://arxiv.org/find/cs/1/au:+Kulikovskiy_V/0/1/0/all/0/1">V. Kulikovskiy</a>, <a href="http://arxiv.org/find/cs/1/au:+Lamoureux_M/0/1/0/all/0/1">M. Lamoureux</a>, <a href="http://arxiv.org/find/cs/1/au:+Lang_R/0/1/0/all/0/1">R. F. Lang</a>, <a href="http://arxiv.org/find/cs/1/au:+Li_S/0/1/0/all/0/1">S. Li</a>, <a href="http://arxiv.org/find/cs/1/au:+Lincetto_M/0/1/0/all/0/1">M. Lincetto</a>, <a href="http://arxiv.org/find/cs/1/au:+Lindstrom_W/0/1/0/all/0/1">W. Lindstrom</a>, <a href="http://arxiv.org/find/cs/1/au:+Linvill_M/0/1/0/all/0/1">M. W. Linvill</a>, <a href="http://arxiv.org/find/cs/1/au:+McCully_C/0/1/0/all/0/1">C. McCully</a>, <a href="http://arxiv.org/find/cs/1/au:+Migenda_J/0/1/0/all/0/1">J. Migenda</a>, <a href="http://arxiv.org/find/cs/1/au:+Milisavljevic_D/0/1/0/all/0/1">D. Milisavljevic</a>, <a href="http://arxiv.org/find/cs/1/au:+Nelson_S/0/1/0/all/0/1">S. Nelson</a>, <a href="http://arxiv.org/find/cs/1/au:+Novoseltseva_R/0/1/0/all/0/1">R. Novoseltseva</a>, <a href="http://arxiv.org/find/cs/1/au:+OSullivan_E/0/1/0/all/0/1">E. O'Sullivan</a>, <a href="http://arxiv.org/find/cs/1/au:+Petravick_D/0/1/0/all/0/1">D. Petravick</a>, <a href="http://arxiv.org/find/cs/1/au:+Pointon_B/0/1/0/all/0/1">B. W. Pointon</a>, <a href="http://arxiv.org/find/cs/1/au:+Raj_N/0/1/0/all/0/1">N. Raj</a>, <a href="http://arxiv.org/find/cs/1/au:+Renshaw_A/0/1/0/all/0/1">A. Renshaw</a>, <a href="http://arxiv.org/find/cs/1/au:+Rumleskie_J/0/1/0/all/0/1">J. Rumleskie</a>, <a href="http://arxiv.org/find/cs/1/au:+Tapia_R/0/1/0/all/0/1">R. Tapia</a>, <a href="http://arxiv.org/find/cs/1/au:+Tseng_J/0/1/0/all/0/1">J. C. L. Tseng</a>, <a href="http://arxiv.org/find/cs/1/au:+Tunnell_C/0/1/0/all/0/1">C. D. Tunnell</a>, <a href="http://arxiv.org/find/cs/1/au:+Vigorito_C/0/1/0/all/0/1">C. F. Vigorito</a>, <a href="http://arxiv.org/find/cs/1/au:+Virtue_C/0/1/0/all/0/1">C. J. Virtue</a>, <a href="http://arxiv.org/find/cs/1/au:+Weaver_C/0/1/0/all/0/1">C. Weaver</a>, <a href="http://arxiv.org/find/cs/1/au:+Winslow_L/0/1/0/all/0/1">L. Winslow</a>, <a href="http://arxiv.org/find/cs/1/au:+Wolski_R/0/1/0/all/0/1">R. Wolski</a>, <a href="http://arxiv.org/find/cs/1/au:+Xu_X/0/1/0/all/0/1">X. J. Xu</a>, <a href="http://arxiv.org/find/cs/1/au:+Xu_Y/0/1/0/all/0/1">Y. Xu</a>

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.

http://arxiv.org/icons/sfx.gif