Karl F Kuhlmman
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Karl F Kuhlmman has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
- David Kane
SRA International, Fairfax, VA, USA
1 shared publication - Ethan Cerami
11Computational Biology Center, Memorial Sloan-Kettering Cancer Center 1275 York Avenue, Box 460, New York, NY, USA
1 shared publication - Jeff A Byrd
Vanderbilt Medical Center, 2209 Garland Avenue, 416 Eskind Biomedical Library, Nashville, TN 37232-8340, USA
1 shared publication - Michael W McCormick
Fred Hutchinson Cancer Research Center, 1100 Fairview Avenue North, Seattle, WA 98109, USA
1 shared publication - Moses M Hohman
Center for Functional Genomics, Northwestern University, 2205 Tech Drive #2-160, Evanston, Illinois 60208, USA
1 shared publication
Latest Publications
- Open Access
- 30 May 2006
- Published by Springer Nature in BMC Bioinformatics
- Vol. 7 (1) , 273
Agile methods in biomedical software development: a multi-site experience report
Background: Agile is an iterative approach to software development that relies on strong collaboration and automation to keep pace with dynamic environments. We have successfully used agile development approaches to create and maintain biomedical software, including software for bioinformatics. This paper reports on a qualitative study of our experiences using these methods. Results: We have found that agile methods are well suited to the exploratory and iterative nature of scientific inquiry. They provide a robust framework for reproducing scientific results and for developing clinical support systems. The agile development approach also provides a model for collaboration between software engineers and researchers. We present our experience using agile methodologies in projects at six different biomedical software development organizations. The organizations include academic, commercial and government development teams, and included both bioinformatics and clinical support applications. We found that agile practices were a match for the needs of our biomedical projects and contributed to the success of our organizations. Conclusion: We found that the agile development approach was a good fit for our organizations, and that these practices should be applicable and valuable to other biomedical software development efforts. Although we found differences in how agile methods were used, we were also able to identify a set of core practices that were common to all of the groups, and that could be a focus for others seeking to adopt these methods.
- 30 May 2006
- Published by Springer Nature in BMC Bioinformatics
- Vol. 7 (1) , 273
Open AccessAgile methods in biomedical software development: a multi-site experience report
Background: Agile is an iterative approach to software development that relies on strong collaboration and automation to keep pace with dynamic environments. We have successfully used agile development approaches to create and maintain biomedical software, including software for bioinformatics. This paper reports on a qualitative study of our experiences using these methods. Results: We have found that agile methods are well suited to the exploratory and iterative nature of scientific inquiry. They provide a robust framework for reproducing scientific results and for developing clinical support systems. The agile development approach also provides a model for collaboration between software engineers and researchers. We present our experience using agile methodologies in projects at six different biomedical software development organizations. The organizations include academic, commercial and government development teams, and included both bioinformatics and clinical support applications. We found that agile practices were a match for the needs of our biomedical projects and contributed to the success of our organizations. Conclusion: We found that the agile development approach was a good fit for our organizations, and that these practices should be applicable and valuable to other biomedical software development efforts. Although we found differences in how agile methods were used, we were also able to identify a set of core practices that were common to all of the groups, and that could be a focus for others seeking to adopt these methods.