Extreme programming explained: embrace change
Extreme programming explained: embrace change
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Exploring XP for Scientific Research
IEEE Software
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
Information and Software Technology
Developing Scientific Software
IEEE Software
Dealing with Risk in Scientific Software Development
IEEE Software
Scientific Software Development at a Research Facility
IEEE Software
A literature review of agile practices and their effects in scientific software development
Proceedings of the 4th International Workshop on Software Engineering for Computational Science and Engineering
Hi-index | 0.00 |
A number of recent studies reported on the success of applying agile methods in scientific software development projects. These studies found that agile methods are well suited to the exploratory, iterative, and collaborative nature of scientific inquiry. However, these findings might not be applicable in all situations pertaining to scientific software development projects. In addition, they only constitute a subset of the important factors while deciding which development methods and practices should be adopted. Therefore, it becomes important to conduct further research before making recommendations regarding the adoption of certain development methods and practices in this domain. In this progress report, we discuss our on-going research that will empirically study the characteristics of various scientific software development projects according to a model suggested by Boehm and Turner. We plan to conduct interviews and collect data from various scientific software development projects in the Baltimore-Washington area. We expect that our qualitative results will increase our understanding of the characteristics in those projects favoring plan-driven approaches or agile methods, and the needs and conditions associated with those characteristics. Our research provides guidance to scientific software developers by enhancing their capacity to evaluate and understand their own project characteristics and select effective software practices. As a long-term benefit in the same direction, our qualitative results will generate a set of hypotheses that can be tested in different project environments to better understand and categorize scientific software development projects. Consequently, in the future, more generalizable and actionable recommendations can be made for scientific software development projects.