HT CHALLENGE 2019

AGILE DEVELOPMENT AND MEDICAL DEVICE

AGILE DEVELOPMENT AND MEDICAL  DEVICE  

AUTORE PRINCIPALE
Giorgia Picci

AFFILIAZIONE
Dedalus spa

VALUTA IL CHALLENGE

Vota

GRUPPO DI LAVORO
Giorgia Picci – Dedalus spa, Toscana
Giorgia Picci – Dedalus spa, Emilia Romagna
Claudia Boarini – Dedalus Italia spa, Emilia Romagna

AREA TEMATICA
ICT ed informatica medica

ABSTRACT

The project goal is to develop a complete new product for clinical diagnostic laboratories. During the evolution of the product we have joined an Agile lifecycle model  working with stakeholders to continuously add features allowing them to give us early feedback as the project develops. Dedalus has decided to adopt SCRUM as core development practice. In order to implement the Methodology Dedalus use a JIRA extension: JIRA AGILE.In this model we use a series of short system iterations each of which defines builds and verifies some new and valuable user functionality. Within each iteration we will define some new requirements and write and test the code that fulfils them. During the course of the iteration teams first plan the iteration breaking the stories into tasks and then commit to completing some number of stories. The team then implements the stories driving each towards a definition of done. The definition of done establishes policy for what constitutes story completion which assures that the story is properly coded reviewed tested and accepted into the product baseline. As the team works on delivering solutions that meet the sprint goals Agile by nature promotes testing early. Unit implementation verification and testing should be done in each sprint.It is very important in a high assurance environment that the definition of done include all quality safety security and regulatory requirements that need to be satisfied for completeness. Furthermore the verification and validation for definition of done is traced through to the acceptance criteria for each user story and then originating the product requirement. Once the Scrum team finishes sprint planning and agrees on the content of the next sprint the development team guided by the ScrumMaster’s coaching performs all of the task-level work necessary to get the features done where done means there is a high degree of confidence that all of the work necessary for producing good-quality features has been completed.The hardening sprint is an extension of the sprint process but the main focus revolves around verification and validation. This is the final step prior to the software release. Integration and regression testing is another a task that should be done in the hardening sprint.The hardening iteration has an empty backlog implying no new user stories. The hardening sprint is a high value focusing on elimination of accumulated technical debt. 

 

 

 

Torna su »

Condividi