“It’s all about time and timing”: nursing staffs’ experiences with an agile development process, from its initial requirements to the deployment of its outcome of ICT solutions to support discharge planning

Abstract

BackgroundAgile projects are statistically more likely to succeed then waterfall projects. The overall aim of this study was to explore the nursing staffs’ experiences with an agile development process, from its initial requirements to the deployment of its outcome of ICT solutions aimed at supporting discharge planning.MethodsAn explorative design with quantitative and qualitative methods was used. Qualitative data was collected through seven focus group interviews. Quantitative data was collected via an ICT-system, and with an evaluation form submitted by fourteen registered nurses and nine district nurses.ResultsQualitative result of the experiences with the agile development process and its outcome resulted in one theme, four categories, and ten subcategories. The theme was found to be about time and timing, namely the amount of time for the different activities and the timing of activities within and between organisations. The agile development process increased the participants’ readiness for change by offering time to learn, practice, engage and reflect, and then adopt the ICT as a support to daily practice. Quantitative results showed a variated adoption of the ICT.ConclusionThere is a need for time to prepare, understand and adopt new tools, services and procedures and a need for additional time to prepare, understand and adopt the new among individuals, collectives, organizations, and sometimes even between different collectives or organizations. The agile development process offered the end-users involvement through the development process, which gave them time to change it both individually and collectively. However, there is a need for close collaboration between the development project team and management to reach an organizational change that is timely for both the individual and the collective change. When time or timing fails in the development or implementation process, there is a huge risk of non-adoption of new tools, services, or procedures or among the end-users.