Abstract
Medical device software development is subject to high regulations due to the potential risk of harming patients with unsafe medical devices. These regulations require software development to be performed with high discipline and evidence to be provided for auditory purposes. It’s not easy to manage both conformance to regulations and efficiency in medical device development. Therefore, there is a transition towards agility in safety critical systems development, to build high quality systems, shorten time to market, improve customer and employee satisfaction and ensure both safety and reliability. In this study, we evaluated one of the most highly adopted agile software development methods, Scrum from a regulatory perspective. We investigated to what extend the regulatory requirements defined in MDevSPICE® are met with implementation of the Scrum method and what additional processes and practices have to be performed to ensure safety and regulatory compliance in the healthcare domain.
Keywords
- MDevSPICE®
- Scrum
- Regulatory compliance
- Safety critical domain
- Agile software development
This is a preview of subscription content, access via your institution.
Buying options


References
FDA: Chapter I - Food and drug administration, department of health and human services subchapter H - Medical devices, Part 820 - Quality system regulation, May 2015. http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfcfr/CFRSearch.cfm?CFRPart=820
Directive 93/42/EEC of the European Parliament and of the Council concerning medical devices (1993)
Council directive 90/385/EEC on active implantable medical devices (AIMDD) (1990)
Directive 98/79/EC of the European parliament and of the council of 27 October 1998 on in vitro diagnostic medical devices (1998)
Directive 2007/47/EC of the European Parliament and of the Council concerning medical devices (2007)
Mc Hugh, M., Cawley, O., McCaffcry, F., Richardson, I., Wang, X.: An agile v-model for medical device software development to overcome the challenges with plan-driven software development lifecycles. In: 2013 5th International Workshop on Software Engineering in Health Care (SEHC), pp. 12–19. IEEE (2013)
Abrahamsson, P., Salo, O., Ronkainen, J., Warsta, J.: Agile Software Development Methods: Review and Analysis. VTT Finland (2002)
Schwaber, K.: Scrum development process. In: Sutherland, J., Casanave, C., Miller, J., Patel, P., Hollowell, G. (eds.) Business Object Design and Implementation, pp. 117–134. Springer, London (1997). doi:10.1007/978-1-4471-0947-1_11
Schwaber, K., Sutherland, J.: Software in 30 days: How Agile Managers Beat the Odds, Delight their Customers, and Leave Competitors in the Dust. Wiley, Hoboken (2012)
Rubin, K.S.: Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley Professional, Boston (2012)
Wolff, S.: Scrum goes formal: agile methods for safety-critical systems. In: Proceedings of the First International Workshop on Formal Methods in Software Engineering: Rigorous and Agile Approaches, pp. 23–29. IEEE Press (2012)
Fitzgerald, B., Stol, K.-J., O’Sullivan, R., O’Brien, D.: Scaling agile methods to regulated environments: an industry case study. In: 2013 35th International Conference on Software Engineering (ICSE), pp. 863–872. IEEE (2013)
Ahmad, E., Raza, B., Feldt, R., Nordebäck, T.: ECSS standard compliant agile software development: an industrial case study. In: Proceedings of the 2010 National Software Engineering Conference, p. 6. ACM (2010)
Kircher, M., Hofman, P.: Combining systematic reuse with agile development: experience report. In: Proceedings of the 16th International Software Product Line Conference, vol. 1, pp. 215–219. ACM (2012)
Faber, R.: Architects as service providers. IEEE Softw. 27(2), 33–40 (2010)
Spence, J.W.: There has to be a better way![software development]. In: 2005 Proceedings of Agile Conference, pp. 272–278. IEEE (2005)
Sutherland, J., Schwaber, K.: The scrum guide. The Definitive Guide to Scrum: The Rules of the Game. Scrum.org (2013)
Acknowledgement
This research is supported by Science Foundation Ireland under a co-funding initiative by the Irish Government and European Regional Development Fund through Lero - the Irish Software Research Centre (http://www.lero.ie) grant 13/RC/2094. This research is also partially supported by the EU Ambient Assisted Living project – Maestro.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this paper
Cite this paper
Özcan-Top, Ö., McCaffery, F. (2017). How Does Scrum Conform to the Regulatory Requirements Defined in MDevSPICE®?. In: Mas, A., Mesquida, A., O'Connor, R., Rout, T., Dorling, A. (eds) Software Process Improvement and Capability Determination. SPICE 2017. Communications in Computer and Information Science, vol 770. Springer, Cham. https://doi.org/10.1007/978-3-319-67383-7_19
Download citation
DOI: https://doi.org/10.1007/978-3-319-67383-7_19
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-67382-0
Online ISBN: 978-3-319-67383-7
eBook Packages: Computer ScienceComputer Science (R0)