“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

Background Agile 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. Methods An 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. Results Qualitative 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. Conclusion There 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.

Solving Problems of Plant Physiology during Periods of Confinement or Online University Education

“…del Hierro et al (2016) applied the Moodle platform to improve performance in General Chemistry problems. ICTs have improved planning and success among nursing staff (Nordmark et al, 2022) and have enabled distance training for older adults living alone (Oba et al, 2022). E-Learning methodologies have also been used to acquire knowledge about pain neurophysiology, increasing the learners' motivation after using them (Valenzuela-Pascual et al, 2022).…”

The methodology of the Agile Nudge University

“…Compared with traditional or waterfall project management approaches, Agile methodology is statistically more likely to succeed by a factor of 12%–73% ( 90 ). Agile methodology can work in conjunction or independently of other project management strategies – such as lean or Six Sigma – adding responsiveness and adaptability ( 91 ).…”

Standardized Anesthesia InductioN Tool (SAINT) – The development and international adoption of an integrated electronic tool for documenting the induction of anesthesia in children

“…Our goal was to develop a comprehensive documentation tool that was easy to use, contextual, and quickly completed; the Agile development methodology allowed rapid iterations with frequent reviews by the core group and expert group until the final version was released. [6][7][8][9] The agile development methodology is a common technique used in software development and emphasizes close collaboration between the end-user and the software developer allowing review and feedback of each stage of development, testing and deployment and has been associated with high satisfaction among end-users. [6][7][8] The initial design stages included mock-ups of the tool, a review of…”

“…[6][7][8][9] The agile development methodology is a common technique used in software development and emphasizes close collaboration between the end-user and the software developer allowing review and feedback of each stage of development, testing and deployment and has been associated with high satisfaction among end-users. [6][7][8] The initial design stages included mock-ups of the tool, a review of…”