@inproceedings {Simula.simula.386,
	title = {A Literature Review of Agile Practices and Their Effects in Scientific Software Development},
	journal = {Proceedings of SE-CSE11},
	year = {2011},
	pages = {1-9},
	type = {Workshop},
	abstract = {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.},
	author = {Magnus Thorstein {Sletholt} and Jo Erskine {Hannay} and Pfahl, Dietmar and Hans Christian {Benestad} and Hans Petter {Langtangen}},
	editor = {Carver, J.}
}
@article {Simula.simula.722,
	title = {What Do We Know About Agile Practices in Scientific Software Development?},
	journal = {Computing in Science \& Engineering},
	volume = {14},
	number = {2},
	year = {2011},
	month = {June},
	pages = {24-37},
	abstract = {The development of scientific software has similarities with processes that follow the software engineering Agile Manifesto: responsiveness to change and collaboration are of 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? To find out, the authors conducted a literature review of past projects and a multiple case study of three ongoing scientific software development projects.},
	author = {Magnus Thorstein {Sletholt} and Jo Erskine {Hannay} and Pfahl, Dietmar and Hans Petter {Langtangen}}
}
@inproceedings {Simula.simula.50,
	title = {Making Modern Scientific Software Development Explicitly Agile},
	journal = {The Changing Dynamics of Scientific Collaborations},
	year = {2010},
	type = {Workshop},
	abstract = {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? As a representative for a modern scientific software project, we briefly outline the FEniCS project whose objective is to automate solution of differential equations. Based on initial investigations, we propose a casestudy where we investigate how the development process in FEniCS can be mapped to agile development methods, and whether SCRUM can be suitable to administer such a project. The case study will use another project, the more traditional Dalton project, as a contrast.},
	author = {Magnus Thorstein {Sletholt} and Jo Erskine {Hannay} and Hans Petter {Langtangen} and Pfahl, Dietmar}
}
