Exploring XP for Scientific Research
IEEE Software
Introducing Agile Development into Bioinformatics: An Experience Report
ADC '03 Proceedings of the Conference on Agile Development
Test Driven Development and the Scientific Method
ADC '03 Proceedings of the Conference on Agile Development
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
Software Development Environments for Scientific and Engineering Software: A Series of Case Studies
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Computing in Science and Engineering
Applying Systematic Reviews to Diverse Study Types: An Experience Report
ESEM '07 Proceedings of the First International Symposium on Empirical Software Engineering and Measurement
Dealing with Risk in Scientific Software Development
IEEE Software
How do scientists develop and use scientific software?
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
Succeeding with Agile: Software Development Using Scrum
Succeeding with Agile: Software Development Using Scrum
Engineering the Software for Understanding Climate Change
IEEE Design & Test
Proceedings of the companion publication of the 17th ACM conference on Computer supported cooperative work & social computing
Hi-index | 0.00 |
The nature of scientific research and the development of scientific software have similarities with processes that follow the agile manifesto: responsiveness to change and collaboration are of the utmost importance. But how well do current scientific software development processes match the practices found in agile development methods, and what are the effects of using agile practices in such processes? In order to investigate this, we conduct a literature review, focusing on evaluating the agility present in a selection of scientific software projects. Both projects with intentionally agile practices and projects with a certain degree of agile elements are taken into consideration. In the agility assessment, we define and utilize an agile mapping chart. The elements of the mapping chart are based on Scrum and XP, thus covering two of the most prominent agile reference models. We compared the findings of the literature review to results of a previously conducted survey. The comparison indicates that scientific software development projects adopting agile practices perceive their testing to be better than average. No difference to average projects was perceived regarding requirements-related activities. Future work includes an in-depth case study to further investigate the existence and impact of agility in three large scientific software projects, ultimately aiming at a better understanding of the particularities involved in developing scientific software.