Studying documentation requirements for quality assurance in healthcare software development environments following Scrum practices : a thesis submitted for examination for the degree of MPhil in Engineering at Massey University, New Zealand

dc.contributor.authorWickramasinghe, Shanuka G
dc.date.accessioned2017-06-15T23:00:23Z
dc.date.available2017-06-15T23:00:23Z
dc.date.issued2016
dc.description.abstractOver the past decade software development has expanded into almost every sector of business and technology. Currently, Agile software development methods are much preferred over traditional software development methods which rely on heavy documentation. Agile methodologies such as Scrum (the focus of the study) rely on minimal documentation. However, software development organizations who seek accreditation against an internationally recognized quality management system (QMS) standard such as ISO 9001:2008 need to maintain a certain level of documentation to meet the requirements stipulated in the QMS standard. This study was undertaken to answer the following overall research question, in relation to healthcare software development: what would be the minimum level of documentation that would be acceptable for a Health-IT organization pursuing Scrum, if they are to maintain an internationally recognized QMS standard such as ISO 9001:2008? This overarching research question was first investigated through in-depth literature synthesis and subsequently discussed with a panel of experts. An iterative research design utilizing Delphi-like problem solving method was used to gather insights from Scrum practitioners. The study identified 23 documents to have varying levels of usefulness and importance to three categories of Scrum users, specifically Scrum Master, Product Owner, and Development Team. The study further identified the level of conciseness required in each document (to suit each category of Scrum users) and the stage in which each document should be prepared to add maximum value in using documentation. The study identified seven negative experiences Scrum practitioners come across: documents being difficult to understand by nontechnical customers; purpose of documents not being explicit; no follow-up with client’s feedback; excessive re-work on documents; deficiencies in document validation; lack of risk analysis reports and disruptions in software development. The study also identified seven problems practitioners face in creating important documents: lack of skilled document writers; last minute/hasty document preparation; misunderstanding the purpose/intent of Agile; lack of a common documentation standard; perceiving document creation as a burden; poor tooling for documentation and lack of right staff. It is expected that the study would benefit both the academia and the practitioner in gaining greater insights on the issue of documentation in Scrum.en_US
dc.identifier.urihttp://hdl.handle.net/10179/11219
dc.language.isoenen_US
dc.publisherMassey Universityen_US
dc.rightsThe Authoren_US
dc.subjectScrum (Computer software development)en_US
dc.subjectAgile software developmenten_US
dc.subjectQuality assuranceen_US
dc.subjectMedical informaticsen_US
dc.subjectHealth careen_US
dc.subjectEngineeringen_US
dc.subjectResearch Subject Categories::TECHNOLOGY::Information technology::Computer engineeringen_US
dc.titleStudying documentation requirements for quality assurance in healthcare software development environments following Scrum practices : a thesis submitted for examination for the degree of MPhil in Engineering at Massey University, New Zealanden_US
dc.typeThesisen_US
massey.contributor.authorWickramasinghe, Shanuka Gen_US
thesis.degree.disciplineEngineeringen_US
thesis.degree.grantorMassey Universityen_US
thesis.degree.levelMastersen_US
thesis.degree.nameMaster of Philosophy (MPhil)en_US
Files
Original bundle
Now showing 1 - 2 of 2
Loading...
Thumbnail Image
Name:
01_front.pdf
Size:
137.29 KB
Format:
Adobe Portable Document Format
Description:
Loading...
Thumbnail Image
Name:
02_whole.pdf
Size:
2.08 MB
Format:
Adobe Portable Document Format
Description:
License bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
license.txt
Size:
3.32 KB
Format:
Item-specific license agreed upon to submission
Description: