A Smartphone App to Increase Immunizations in the Pediatric Solid Organ Transplant Population: Development and Initial Usability Study

Background Vaccine-preventable infections result in significant morbidity, mortality, and costs in pediatric transplant recipients. However, at the time of transplant, less than 20% of children are up-to-date for age-appropriate immunizations that could prevent these diseases. Smartphone apps have the potential to increase immunization rates through their ability to provide vaccine education, send vaccine reminders, and facilitate communication between parents and a multidisciplinary medical group. Objective The aim of this study was to describe the development of a smartphone app, Immunize PediatricTransplant, to promote pretransplant immunization and to report on app functionality and usability when applied to the target population. Methods We used a mixed methods study design guided by the Mobile Health Agile Development and Evaluation Lifecycle. We first completed a formative research including semistructured interviews with transplant stakeholders (12 primary care physicians, 40 parents or guardians of transplant recipients, 11 transplant nurse coordinators, and 19 transplant subspecialists) to explore the acceptability of an immunization app to be used in the pretransplant period. Based on these findings, CANImmunize Inc developed the Immunize PediatricTransplant app. We next held 2 focus group discussions with 5-6 transplant stakeholders/group (n=11; 5 parents of transplant recipients, 2 primary care physicians, 2 transplant nurse coordinators, and 2 transplant subspecialists) to receive feedback on the app. After the app modifications were made, alpha testing was conducted on the functional prototype. We then implemented beta testing with 12 stakeholders (6 parents of transplant recipients, 2 primary care doctors, 2 transplant nurse coordinators, and 2 transplant subspecialists) to refine the app through an iterative process. Finally, the stakeholders completed the user version of the Mobile Application Rating Scale (uMARS) to assess the functionality and quality of the app. Results A new Android- and Apple-compatible app, Immunize PediatricTransplant, was developed to improve immunization delivery in the pretransplant period. The app contains information about vaccine use in the pretransplant period, houses a complete immunization record for each child, includes a communication tool for parents and care providers, and sends automated reminders to parents and care providers when immunizations are due. During usability testing, the stakeholders were able to enter a mock vaccine record containing 16 vaccines in an average of 8.1 minutes (SD 1.8) with 87% accuracy. The stakeholders rated engagement, functionality, aesthetics, and information quality of the app as 4.2/5, 4.5/5, 4.6/5, and 4.8/5, respectively. All participants reported that they would recommend this app to families and care teams with a child awaiting solid organ transplant. Conclusions Through a systematic, user-centered, agile, iterative approach, the Immunize PediatricTransplant app was developed to improve immunization delivery in the pretransplant period. The app tested well with end users. Further testing and agile development among patients awaiting transplant are needed to understand real-world acceptability and effectiveness in improving immunization rates in children awaiting transplant.

Analysing the Obstacles in Agile Software Development Approach: A Review

The development of reusable and extensible software for business purposes has been the hallmark of the day. More developers are taking advantage of numerous approaches towards reaching their goals. One such approach is the agile approach in the development of extensible applications which has become so popular since its introduction over a decade ago. Using an agile approach that has a defined value in developing applications portray numerous benefits which have been identified by various scholars pointing out their outcomes as motivating factors of its adoption. With all such outline benefits, there exist some potential obstacles to agile developmental approach which has not been fully addressed. Hence, this article is aimed at analysing the obstacles which software developers face during agile development through a database search and also to guide them on ways to overcome such obstacles.

Agility in Software Development and Project Value

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

Applying Software Engineering Design Principles to Agile Architecture

Most enterprise IT systems are very complex with a combination of COBOL and Java programs running on multiple platforms. What is needed is a solid IT architecture that supports the operation and growth of a cross-platform IT system. It must enable the iterative and incremental development of applications that are foreseen in an agile development process. The design concept of such an architecture with its infrastructure and development tool is presented in this chapter. This design concept is based on the design principles and architectural patterns of software engineering. The architecture is a combination of layered, component-based, and service-oriented architectural patterns. The agile development process is based on a model-driven approach. The architecture and development approaches were first introduced in 2004. Since then, many applications have been developed on time and within budget.

Measuring Software Development Project Performance

Adopting agile methodologies to software development processes helps software companies to sustain their growth through efficiency for long term. In the digital transformation era, Industry 4.0 as part of High-Tech Strategy 2020 for Germany involves agile principles and brings the latest technological trends in production process. The purpose of this chapter is to design a proper agile project management performance measurement model for start-up software companies. First, all key performance indicators related to agile development in the literature have been listed. Then KPIs that are provided from literature review with content analysis have been reviewed and categorized by expert opinions that were collected through in-depth interviews. Seven strategic KPIs and their data collection systems are defined and designed. Lastly, process and data collection improvements are recommended in order to sustain agile development measurement model.

Reuse in Agile Development Process

Reusability is a clear principle in software development. However, systematic reuse of software elements is not common in most organizations. Application programmers rarely design and create software elements for possible future reuse. In many agile software development processes, the project teams believe that the development of reusable software elements can slow down the project. This can be a misconception. This chapter examines various ways to reuse software. Three approaches to developing reusable software artifacts from 15 years of experience in the agile development process are presented. The first approach is to create generic programs or configurable frameworks that support similar solutions for a variety of use cases and environments. The reuse of patterns is the second approach presented. Another effective way is to use a model-driven approach with model patterns. These approaches help to speed deployment software. The final product is flexible and can easily be adapted to changes. This is one of the main goals of an agile approach.

Adaptation of Modern Agile Practices in Global Software Engineering

Software engineering has been an active working area for many decades. It evolved in a bi-folded manner. First research and subsequently development. Since the day of its inception, the massive number of variants and methods of software engineering were proposed. Primarily, these methods are designed to cater the time-varying need of modern approach. In this connection, the Global Software Engineering (GSE) is one of the growing trends in the modern software industry. At the same time, the employment of Agile development methodologies has also gained the significant attention in the literature. This has created a rationale to explore and adopt agile development methodology in GSE. It gained rigorous attention as an alternative to traditional software development methodologies. This paper has presented a comprehensive review on the adaptation of modern agile practices in GSE. In addition, the strength and limitation of each approach have been highlighted. Finally, the open area in the said domain is submitted as one of the deliverables of this work.

Auditing an Agile Development Operations Ecosystem

In an enterprise software development, DevOps is a practice of integrating development and operations to deliver cost-efficient, improved quality solutions to the customer by automating the existing processes to achieve “continuous delivery.” In the current dynamic IT Ecosystem where there is a rising need to prove a competitive edge to maximize profitability, it is pivotal to drive business value with profound emphasis on quality. Agile enables us to take calculated risks during development whereas its affinity to adopting DevOps will promote continuous delivery with reduced friction to improve business efficiency. As this approach requires a change in people, process, technology, culture, usage of right tools and techniques, the early involvement of IT Auditors during the process of transformation could aid to build effective Risk Management strategies to handle organizational challenges. This article aims to present a risk-based audit approach to effectively use audit tools and techniques in an Agile-DevOps transformation environment to achieve maximum business value.