1) For this assignment, you will create a written plan on EHR in a 5-6 page paper and a PowerPoint presentation of 55 slides in detail excluding the title and reference page. Based on the assignment you completed in Week 4, you will now take the system that you selected for evaluation and create an implementation and support plan. You are to serve as the product manager for the given system. It is your responsibility to ensure the success of this system. With an abstract and table of content page Complete the following:

• Create an implementation plan (development and deployment) for the identified system.
• In addition to your implementation plan, what is the key performance indicators (KPIs) that you will use to evaluate the success or value of the system?
• what maintenance aspects must be accounted for to ensure the long-term use of this system.

2) Additionally, build off of what you created in the weeks leading up to this assignment. Create a PowerPoint presentation from your Individual Projects from Weeks 1–5. This PowerPoint presentation should be a presentation to a chief information officer (CIO). For your presentation, create a new division within a health care information technology (IT) organization. You have been given complete control of this division; however, you need to explain to the CIO how one will manage the following:

• The systems development life cycle (SDLC) (e.g., waterfall or agile)
• The regulations associated with health care (e.g., Health Insurance Portability and Accountability Act [HIPAA] and meaningful use)
• Security and recovery (e.g., system security, network security, and data security)
• System interoperability and organizational interoperability
• Implementation of the systems that your division is responsible for within the organization (e.g., action plan)
• Evaluation of your organization and definitions of success, including financial objectives

Note: Use APA 7th edition style to cite at least 6 scholarly sources from the last 5 years.  Consider writing in a third person.

Running head: AGILE METHODOLOGY IN HEALTH MANAGEMENT 1

AGILE METHODOLOGY IN HEALTH MANAGEMENT 10

Agile Methodology in Health Management

Frances Ogbankwa

HCM-690 Healthcare Informatics

December 15, 2021

Having gone through different Agile Methodologies, one would be able to come across one that would be best suited for healthcare management which is the Scrum Approach.

American healthcare difficulties may be alleviated by adopting Scrum practices. Healthcare and its development in the United States have been a major topic of discussion and news in recent years. Healthcare affordability and accessibility are fundamental aspects of civilized society (Jakupovic, 2021). In 1970, the Federal Government spent an estimated $75 billion on healthcare. The value was $3 trillion in 2012, and if present growth rates are maintained, it will be $5 trillion by 2022, and that rise is significant.

Healthcare expenditures are intimately linked to consumer satisfaction in the current healthcare culture. The impact of health technologies on clinical results and the better patient has grown significantly in recent years. To address the demands of a new paradigm, new methodologies are needed. Scrum is being utilized more and more often in the healthcare industry than in the past.

Why Scrum?

· Operational errors in healthcare are currently the third leading cause of death in the United States, behind cancer and cardiovascular disease. More than 500 people die each day from “errors, catastrophes, and illnesses” in hospitals.

· Scrum is money spent on care that was unneeded. According to the Institute of Medicine, it’s estimated that one-third of the millions spent on welfare each year is squandered. According to the Journal of the American of Gynecology, $1 billion is spent each year on elective births alone.

· Organizations must adapt quickly and thoroughly to keep pace with ever-changing requirements (Jakupovic, 2021).

· There is a huge need for health information systems, but there are no systems to accomplish this goal.

· There is a need for novel therapies and medications to be researched and developed.

· Some new medical equipment and machinery have not been properly tested for safety issues. Many of them are created using old procedures where design is done first, and testing is done afterward (Jakupovic, 2021).

Benefits

Scrum has two major advantages over other project management methodologies. In the first place, a Scrum team’s projects are more likely to be completed on time and within budget. The second greatest benefit of utilizing Scrum is to keep Scrum teams operating at their peak efficiency (Jakupovic, 2021). Scrum teams plan and manage their funds before beginning every project, effectively using time and money. This reduces the risk of unanticipated costs and delays. Towards the conclusion of each sprint, Scrum teams also test their product before releasing it so that they may detect and repair any probable defects.

Several aspects and components must be considered to guarantee the project’s success. As a result of scrum methodologies’ ability to break down large projects into smaller, more manageable components and teams’ more relevant attitude to finishing them, regular monitoring of these items is considerably simpler (Velthuijsen et al., 2015). The needs of a project may change as the project progresses, and so may the project itself. Since Scrum teams operate in sprints, modifications may be applied simply in the following iteration. A Waterfall approach team doesn’t have to start from scratch, as is common with those who do.

Challenges for Healthcare

This technique may seem like an ideal answer for all project-related challenges. However, there are some downsides to Scrum. Scrum projects can take longer than expected since there is no set timetable and the work is done according to the sprint cycle. Scrum emphasizes iterative development. At worst, it’s a liability. This is a major departure from their previous working style, which might be tough for Scrum teams to adapt to (Velthuijsen et al., 2015). As a result, Scrum masters and project managers have less control over their teams’ day-to-day operations, which may be inconvenient for everyone involved. Scrum team members may also have trouble adapting to a new way of working, leading to delays in the project.

The lack of qualifications and expertise may create problems when teams are not properly taught and schooled in Agile and Scrum processes. The quality of the final product might suffer if teams don’t test vigorously enough throughout each version. Scrum teams must be dedicated to their project and the Scrum method to operate (Velthuijsen et al., 2015).

When implementing Scrum methodology, it’s essential to have a small group. Scrum teams often include four to six people. It might not be easy to communicate effectively with big teams in Scrum. If the team size is too huge, this may be a problem, and it can also cause a lot of irritation among the group members (Kurniawan et al., 2020). Scrum often has issues because the Scrum practices are not adequately applied, and the employees are not properly taught. Scrum techniques may benefit all projects in any business if this obstacle is overcome and communications are improved.

Challenges to be Mitigated

Lack of Documentation

The Agile Manifesto outlines fundamental principles. Values like working software above complete manuals are among them. According to the regulations, this value would seem to conflict with it directly. The FDA mandates that an implantable devices developer record all of the criteria for the software before it is developed. But one of the Agile manifesto’s writers Robert Martin advises: “Produce no document unless it’s urgent and meaningful.” In attaining regulatory compliance, paperwork is substantial, and it is still generated when following the agile approach (Kurniawan et al., 2020). Berard investigated documentation and agile software development. Agile software developers provide exactly what the client wants.

Traceability Problems

Regulatory clearance for medical device project management enterprises requires proof of transparency from the functional specifications to each phase of the construction process. According to the FDA “Guidelines of Software Validation (GPSV), documentation of screening and diagnostic cases must be connected to code. Needs are not established before creation starts, and modifications to requirements are encouraged throughout things. However, traceability may still be preserved after the training set and updates to the requirement gathering are recorded.

A lack of forethought

The Scrum model and other life cycles based on plan-driven software development focused on upfront planning. It’s important to have a plan from the beginning of a project to keep it on track. Although agile principles make up-front preparation challenging, it is expected and desired in an agile project (Kurniawan et al., 2020). While this is the case, agile methodologies use strategies such as user stories before a project starts. These are a sort of pre-planning that may help a project get off the ground.

Multiple Releases Under Control

Repetitions are used to break down professional developers produced using agile methodologies. A shippable system is the goal of each iteration for agile teams. Due to regulatory constraints, medical device software developers are prohibited from deploying incomplete software into a live patient setting since safety is crucial for medical device technology (Kurniawan et al., 2020).

Implementation of Scrum

To facilitate teamwork, Scrum was developed as a foundation. When teams practice Scrum like any game (from which it gets its name), they are encouraged to learn from their mistakes, self-organize while working on an issue, and reflect on their successes and failures to improve. For all sorts of cooperation, concepts and lessons from Scrum may be implemented. Developers most often utilize Scrum. That’s why Scrum is so well-liked. Scrum specifies a combination of events, tools, and responsibilities that help people manage and organize their work and is often considered an agile project methodology (Edoh et al., 2018).

Following are the keynotes took out after the real-time scrum implementation in a healthcare

· A project owner knowledgeable about the prerequisites and has the authority to set priority areas can be difficult to find. When working on big projects, it is common that the project backlog position must be shared among several people.

· The project roadmap must be comprehensive and accurately calculated when there is a critical deadline. Even if one has very little data about a project’s requirements, it’s better to have a guesstimate than not have a guesstimate. This data and the team’s speed are critical for the discharge planning stage (Edoh et al., 2018).

· With numerous remote teams, Scrum is ideal for implementation. It was beneficial for team unity and interaction to have resources in the Netherlands and India in each Scrum team. Hardware requirements that can be purchased at a low cost can be used for interaction.

· When starting a dispersed project, it’s a good idea to hold an initial meeting in person to establish team practices.

· A completely separate team can better handle work that doesn’t fit well into a Scrum Sprint (e.g., chasing down key people, interconnecting with other client debts). These teams can concentrate on developing the software. Technical writers can help with this, even with various communication costs (Edoh et al., 2018).

· Customers may still demand detailed records, even if it is not necessary for computer programming. However, in a Scrum project, user stories cannot be replaced. The cost of reconciling prerequisites in two places must be involved in planning.

· Automatic vehicle testing is essential to avoid slowed down by correlation bugs as software is released in stages. The project will add for itself before the project is finished.

References

Edoh, T. O., & Dehou, G. J. M. (2018). A multimodal speech-based Scrum Board for Agile Healthcare Inclusion of Traditional Healers in Rural Healthcare. In IREHI.

Kurniawan, F. F., Shidiq, F. R., & Sutoyo, E. (2020). WeCare Project: Development of Web-based Platform for Online Psychological Consultation using Scrum Framework. Bulletin of Computer Science and Electrical Engineering, 1(1), 33-41.

Jakupovic, A. (2021). Implementation of the Scrum method in a healthcare project: A case studied at Region Västra Götaland.

Velthuijsen, H., Balje, J., & Carter, A. (2015, October). Agile development as a change management approach in Healthcare Innovation Projects. In 3rd Understanding Small Enterprises (USE) Conference 2015.