Abstract
Clinical research laboratories, bioinformatics core facilities, and health science organizations often rely on heavy planning based software development models to propose, build, and distribute software as a consumable product. Projects in non-agile software life cycles tend to have rigid “plan-design-build” milestones, increasing the amount of time needed for software development completion. Though the classic software development approach is needed for large-scale and organizational projects, clinical research laboratories can expedite software development while maintaining quality by using lean prototyping as a condition of project advancement to a committed adaptive software development cycle. Software projects benefit from an agile methodology due to the active and changing requirements often guided by experimental data driven models. We describe a lean to adaptive method used in parallel with laboratory bench work to develop quality software quickly that meets the requirements of a fast-paced research environment and reducing time to production, providing immediate value to the end user, and limiting unnecessary development practices in favor of results.
Highlights
Clinical research laboratories often use rapid application development and agile software methods [1,2] for computationally intensive tasks related to health science and biological data analysis, collection, modeling and simulation
Though the classic software development approach is needed for large-scale and organizational projects, clinical research laboratories can expedite software development while maintaining quality by using lean prototyping as a condition of project advancement to a committed adaptive software development cycle
We describe a lean to adaptive method used in parallel with laboratory bench work to develop quality software quickly that meets the requirements of a fast-paced research environment and reducing time to production, providing immediate value to the end user, and limiting unnecessary development practices in favor of results
Summary
Clinical research laboratories often use rapid application development and agile software methods [1,2] for computationally intensive tasks related to health science and biological data analysis, collection, modeling and simulation These tasks, are often done ad hoc and the development process is selected in a similar manner, increasing the amount of time needed to complete the project, limiting user feedback, and producing poor documentation. Though many health science researchers are unfamiliar with the best practices of agile software development, previous work suggest a core set of practices does exist that can be adopted by similar biomedical, bioinformatics, and health science professionals to produce quality software in a reasonable time frame [2,3,4,5,6] From this previous work, our software development team has implemented an agile methodology that has been successful [7] in creating, distributing, and improving internal and external software projects
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
