no code implementations • 19 Jan 2021 • A. L. Baxter, S. Y. BenZvi, W. Bonivento, A. Brazier, M. Clark, A. Coleiro, D. Collom, M. Colomer-Molla, B. Cousins, A. Delgado Orellana, D. Dornic, V. Ekimtcov, S. ElSayed, A. Gallo Rosso, P. Godwin, S. Griswold, A. Habig, S. Horiuchi, D. A. Howell, M. W. G. Johnson, M. Juric, J. P. Kneller, A. Kopec, C. Kopper, V. Kulikovskiy, M. Lamoureux, R. F. Lang, S. Li, M. Lincetto, W. Lindstrom, M. W. Linvill, C. McCully, J. Migenda, D. Milisavljevic, S. Nelson, R. Novoseltseva, E. O'Sullivan, D. Petravick, B. W. Pointon, N. Raj, A. Renshaw, J. Rumleskie, R. Tapia, J. C. L. Tseng, C. D. Tunnell, C. F. Vigorito, C. J. Virtue, C. Weaver, L. Winslow, R. Wolski, X. J. Xu, Y. Xu
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.
Software Engineering Instrumentation and Methods for Astrophysics