Collaborative experience between scientific software projects using Agile Scrum development

dc.citation.firstpage2077
dc.citation.issueNumber10
dc.citation.journalTitleSoftware: Practice and Experience
dc.citation.lastpage2096
dc.citation.volumeNumber52
dc.contributor.authorBaxter, Amanda L.
dc.contributor.authorBenZvi, Segev Y.
dc.contributor.authorBonivento, Walter
dc.contributor.authorBrazier, Adam
dc.contributor.authorClark, Michael
dc.contributor.authorColeiro, Alexis
dc.contributor.authorCollom, David
dc.contributor.authorColomer-Molla, Marta
dc.contributor.authorCousins, Bryce
dc.contributor.authorDelgado Orellana, Aliwen
dc.contributor.authorDornic, Damien
dc.contributor.authorEkimtcov, Vladislav
dc.contributor.authorElSayed, Shereen
dc.contributor.authorGallo Rosso, Andrea
dc.contributor.authorGodwin, Patrick
dc.contributor.authorGriswold, Spencer
dc.contributor.authorHabig, Alec
dc.contributor.authorHill, Remington
dc.contributor.authorHoriuchi, Shunsaku
dc.contributor.authorHowell, D. Andrew
dc.contributor.authorJohnson, Margaret W.G.
dc.contributor.authorJurić, Mario
dc.contributor.authorKneller, James P.
dc.contributor.authorKopec, Abigail
dc.contributor.authorKopper, Claudio
dc.contributor.authorKulikovskiy, Vladimir
dc.contributor.authorLamoureux, Mathieu
dc.contributor.authorLang, Rafael F.
dc.contributor.authorLi, Shengchao
dc.contributor.authorLincetto, Massimiliano
dc.contributor.authorLindstrom, Lindy
dc.contributor.authorLinvill, Mark W.
dc.contributor.authorMcCully, Curtis
dc.contributor.authorMigenda, Jost
dc.contributor.authorMilisavljevic, Danny
dc.contributor.authorNelson, Spencer
dc.contributor.authorNovoseltseva, Rita
dc.contributor.authorO'Sullivan, Erin
dc.contributor.authorPetravick, Donald
dc.contributor.authorPointon, Barry W.
dc.contributor.authorRaj, Nirmal
dc.contributor.authorRenshaw, Andrew
dc.contributor.authorRumleskie, Janet
dc.contributor.authorSonley, Tom
dc.contributor.authorTapia, Ron
dc.contributor.authorTseng, Jeffrey C.L.
dc.contributor.authorTunnell, Christopher D.
dc.contributor.authorVannoye, Godefroy
dc.contributor.authorVigorito, Carlo F.
dc.contributor.authorVirtue, Clarence J.
dc.contributor.authorWeaver, Christopher
dc.contributor.authorWeil, Kathryn E.
dc.contributor.authorWinslow, Lindley
dc.contributor.authorWolski, Rich
dc.contributor.authorXu, Xun- Jie
dc.contributor.authorXu, Yiyang
dc.contributor.authorThe SCiMMA and SNEWS Collaborations
dc.date.accessioned2022-09-29T15:06:31Z
dc.date.available2022-09-29T15:06:31Z
dc.date.issued2022
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.
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.
dc.identifier.digitalSoftwPractExp-2022-Baxter
dc.identifier.doihttps://doi.org/10.1002/spe.3120
dc.identifier.urihttps://hdl.handle.net/1911/113437
dc.language.isoeng
dc.publisherWiley
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.
dc.rights.urihttps://creativecommons.org/licenses/by-nc/4.0/
dc.titleCollaborative experience between scientific software projects using Agile Scrum development
dc.typeJournal article
dc.type.dcmiText
dc.type.publicationpublisher version
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
SoftwPractExp-2022-Baxter.pdf
Size:
2.27 MB
Format:
Adobe Portable Document Format