Barriers to Adopting Agile Practices When Developing Medical Device Software

  • Martin McHugh
  • Fergal McCaffery
  • Valentine Casey
Conference paper

DOI: 10.1007/978-3-642-30439-2_13

Part of the Communications in Computer and Information Science book series (CCIS, volume 290)
Cite this paper as:
McHugh M., McCaffery F., Casey V. (2012) Barriers to Adopting Agile Practices When Developing Medical Device Software. In: Mas A., Mesquida A., Rout T., O’Connor R.V., Dorling A. (eds) Software Process Improvement and Capability Determination. SPICE 2012. Communications in Computer and Information Science, vol 290. Springer, Berlin, Heidelberg

Abstract

Agile methodologies such as XP and Scrum are founded upon the four values and twelve principles of agile software development. A software development project is only considered to be truly agile if these values and principles are followed. However, software developed for use in medical devices must be regulatory compliant and this can make the process of following a single agile methodology such as XP difficult to achieve. This paper outlines how we identified the barriers to agile adoption in the medical device software domain through performing a survey. These barriers include: lack of documentation; maintaining traceability; regulatory compliance; lack of up front planning and the process of managing multiple releases. Based on this research recommendations are also made as to how these barriers can be overcome.

Keywords

Safety Critical Agile Plan Driven XP Scrum Barriers Medical 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Martin McHugh
    • 1
  • Fergal McCaffery
    • 1
  • Valentine Casey
    • 1
  1. 1.Regulated Software Research Group, Department of Computing and MathematicsDundalk Institute of Technology & LeroDundalk Co.Ireland

Personalised recommendations