Collaborative experience between scientific software projects using Agile Scrum development

Simple item page
dc.citation.firstpage2077en_US
dc.citation.issueNumber10en_US
dc.citation.journalTitleSoftware: Practice and Experienceen_US
dc.citation.lastpage2096en_US
dc.citation.volumeNumber52en_US
dc.contributor.authorBaxter, Amanda L.en_US
dc.contributor.authorBenZvi, Segev Y.en_US
dc.contributor.authorBonivento, Walteren_US
dc.contributor.authorBrazier, Adamen_US
dc.contributor.authorClark, Michaelen_US
dc.contributor.authorColeiro, Alexisen_US
dc.contributor.authorCollom, Daviden_US
dc.contributor.authorColomer-Molla, Martaen_US
dc.contributor.authorCousins, Bryceen_US
dc.contributor.authorDelgado Orellana, Aliwenen_US
dc.contributor.authorDornic, Damienen_US
dc.contributor.authorEkimtcov, Vladislaven_US
dc.contributor.authorElSayed, Shereenen_US
dc.contributor.authorGallo Rosso, Andreaen_US
dc.contributor.authorGodwin, Patricken_US
dc.contributor.authorGriswold, Spenceren_US
dc.contributor.authorHabig, Alecen_US
dc.contributor.authorHill, Remingtonen_US
dc.contributor.authorHoriuchi, Shunsakuen_US
dc.contributor.authorHowell, D. Andrewen_US
dc.contributor.authorJohnson, Margaret W.G.en_US
dc.contributor.authorJurić, Marioen_US
dc.contributor.authorKneller, James P.en_US
dc.contributor.authorKopec, Abigailen_US
dc.contributor.authorKopper, Claudioen_US
dc.contributor.authorKulikovskiy, Vladimiren_US
dc.contributor.authorLamoureux, Mathieuen_US
dc.contributor.authorLang, Rafael F.en_US
dc.contributor.authorLi, Shengchaoen_US
dc.contributor.authorLincetto, Massimilianoen_US
dc.contributor.authorLindstrom, Lindyen_US
dc.contributor.authorLinvill, Mark W.en_US
dc.contributor.authorMcCully, Curtisen_US
dc.contributor.authorMigenda, Josten_US
dc.contributor.authorMilisavljevic, Dannyen_US
dc.contributor.authorNelson, Spenceren_US
dc.contributor.authorNovoseltseva, Ritaen_US
dc.contributor.authorO'Sullivan, Erinen_US
dc.contributor.authorPetravick, Donalden_US
dc.contributor.authorPointon, Barry W.en_US
dc.contributor.authorRaj, Nirmalen_US
dc.contributor.authorRenshaw, Andrewen_US
dc.contributor.authorRumleskie, Janeten_US
dc.contributor.authorSonley, Tomen_US
dc.contributor.authorTapia, Ronen_US
dc.contributor.authorTseng, Jeffrey C.L.en_US
dc.contributor.authorTunnell, Christopher D.en_US
dc.contributor.authorVannoye, Godefroyen_US
dc.contributor.authorVigorito, Carlo F.en_US
dc.contributor.authorVirtue, Clarence J.en_US
dc.contributor.authorWeaver, Christopheren_US
dc.contributor.authorWeil, Kathryn E.en_US
dc.contributor.authorWinslow, Lindleyen_US
dc.contributor.authorWolski, Richen_US
dc.contributor.authorXu, Xun- Jieen_US
dc.contributor.authorXu, Yiyangen_US
dc.contributor.authorThe SCiMMA and SNEWS Collaborationsen_US
dc.date.accessioned2022-09-29T15:06:31Zen_US
dc.date.available2022-09-29T15:06:31Zen_US
dc.date.issued2022en_US
dc.description.abstractDeveloping 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.en_US
dc.identifier.citationBaxter, Amanda L., BenZvi, Segev Y., Bonivento, Walter, et al.. "Collaborative experience between scientific software projects using Agile Scrum development." <i>Software: Practice and Experience,</i> 52, no. 10 (2022) Wiley: 2077-2096. https://doi.org/10.1002/spe.3120.en_US
dc.identifier.digitalSoftwPractExp-2022-Baxteren_US
dc.identifier.doihttps://doi.org/10.1002/spe.3120en_US
dc.identifier.urihttps://hdl.handle.net/1911/113437en_US
dc.language.isoengen_US
dc.publisherWileyen_US
dc.rightsThis is an open access article under the terms of the Creative Commons Attribution-NonCommercial License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited and is not used for commercial purposes.en_US
dc.rights.urihttps://creativecommons.org/licenses/by-nc/4.0/en_US
dc.titleCollaborative experience between scientific software projects using Agile Scrum developmenten_US
dc.typeJournal articleen_US
dc.type.dcmiTexten_US
dc.type.publicationpublisher versionen_US
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
SoftwPractExp-2022-Baxter.pdf
Size:
2.27 MB
Format:
Adobe Portable Document Format
Download
Collections
Faculty Publications
Physics and Astronomy Publications