Project Two Implementation Plan Template

IT 304 Project Two Implementation Plan Template Complete this template by replacing the bracketed text with the relevant information in each section. If there are sections that you believe do not need to be considered in this implementation plan (based on the scenario provided), type in “Does not apply.” Then provide a 1- to 3-sentence rationale as to why that section does not apply for this system. Implementation plans vary based on industry and organization. This template was intentionally designed to meet the needs of the project and may not contain all of the sections that you may experience at a future employer. Implementation Plan Millennia HealthCenter Cameron Thistle 01/08/2023 Table of Contents 1. Introduction .............................................................................................................................................. 3 1.1 Purpose ............................................................................................................................................... 3 1.2 System overview ................................................................................................................................. 3 2. Implementation approach and schedule .................................................................................................. 3 3. Phases ....................................................................................................................................................... 4 4. Tasks .......................................................................................................................................................... 4 5. Resources .................................................................................................................................................. 4 5.1 Hardware and software .................................................................................................................. 4 5.2 Personnel ........................................................................................................................................ 5 5.3 Training ........................................................................................................................................... 5 5.4 Budget ............................................................................................................................................. 5 6. Durations and estimates ........................................................................................................................... 5 7. Task dependencies .................................................................................................................................... 5 8. Performance monitoring........................................................................................................................... 5 2 1. Introduction The steps we will take to integrate the new software at Millennia HealthCenter will be outlined in this document. This implementation plan will cover the tasks, resources, installation, testing, and implementation of the new workflow application. It is planned to integrate and build for nine months, then softest for three months, before installing the new software at each workplace. Our goal is for every office in the world to use this new program to its full potential within a year. 1.1 Purpose The objective of this new system is to provide the medical staff at Millennia HealthCenter with a method that is both more effective and efficient for scheduling appointments and maintaining data. At the same time, the privacy and wellness of patients will be protected, and the standard of care that Millennia HealthCenter provides to its patients will be raised from in-person visits to virtual ones. The staff at Millennia HealthCenter, which includes doctors, nurses, and other support personnel, are just a few of the many stakeholders who will interact with the system. and Millennia HealthCenter's various departments, including online care, specialist care, and emergency care. 1.2 System overview The best course of action would be to develop a new system that incorporates all aspects of the offices into a single system to improve the patient experience and protect their data. The system will be able to retrieve and send patient information to any professional team member who needs it while adhering to safety regulations. The security measures will ensure that only the person who is relevant can access the information. The system will incorporate all other aspects of the patient's visit, including appointment scheduling, insurance information, diagnosis, pharmacy, and prescription history. In addition, all offices affiliated with Millennia HealthCenter will have universal access through the system. 2. Implementation approach and schedule This project will be developed using an agile development approach. This approach was chosen because of the software's many moving parts and points of connection. Before the program is implemented in workplaces, this strategy will ultimately enable a software testing phase that is more comprehensive and adaptable. In addition, even though agile places little emphasis on documentation, we do so and will continue to do so. Since this is a new system being built from the ground up, we want to make sure that anyone working on it in the future understands how it was made so they can quickly fix any problems. 3 3. Phases There are five key stages to this software development process: integration, soft-testing, development, and live review However, to guarantee that these subphases will function continuously and that each software component is tested and examined, additional divisions into smaller phases will be made. Given that data security has been brought up as one of the concerns, we need to make sure that every part of the build protects MHC's security and data. 4. Tasks Development: We will conduct a requirement analysis and compile a list of essential and desirable challenges and requirements with the assistance of MHC stakeholders. During the development analysis phase, the development team will be consulted to draft all concepts. During the current phase, we will then present the project concept to the MHC project team. The MHC project team's issues will be addressed next as part of the development analysis phase. If there is none, we will begin developing the software. The front office and administration, back-office nurses and doctors, lab and testing, patients, pharmacies, and video conference calls will all receive their own distinct software modules from us. Each module will be incorporated into the system after being independently constructed. This is done to make sure that everything in the program is working well. When developing independently, each developer must use the same coding language. Testing: Each module will be tested frequently throughout the testing process to ensure that it functions properly. The application will also test the front end and back end to make sure everything is in order. After each module is finished, a final exam will be given. The software will be made by combining the modules after each one has been successfully completed. The program will then go through testing to make sure that the modules work together well. Integration: The program will be put into use for the soft-test phase on hardware that is already in use if testing goes well. This is done to ensure that the software is compatible with all office software. Soft Tests: to ensure that everything is working properly; At first, the application will only work in a small number of offices. At this point, every last-minute bug will be fixed. Live Analysis: After the soft testing is successful, the program will be installed and used in every MHC location. 5. Resources The launch of this program will require staff, resources, and efforts. We intend to collaborate with MHC on the program's development. The reasoning behind this is that including MHC technical support in some steps will make it easier to manage the budget, make training more effective, and make it easier to hand over the process to the MHC employees in a smooth manner. 5.1 Hardware and software The system is being built in a hybrid cloud environment. To support a cloud environment, a server area with secure VPN access must be made available and updated. Each facility will have on-site server rooms for the system, which will make it possible to manage the local area network (LAN) there and guarantee connectivity to the main system, which will be hosted in the cloud and accessible online. Consequently, the MHC system can be utilized worldwide, allowing 4 patients and MHC staff to access data at any time. MHC will continue to have staff terminals to maintain security and prevent misidentification, but we will also add tablets for nurses and other staff members. We will also install kiosks at each office entrance to check patients in. When a patient arrives at the facility, these kiosks will also notify the MHC system. All the computers that are currently in use at MHC facilities will be kept, but any that do not meet the software and hardware requirements of the new MHC system will be cleaned and upgraded. 5.2 Personnel The scope of this project is very broad. To ensure that the schedule is followed, we will need a project manager. Additionally, there will be one software developer, one web developer, one computer network architect, and two computer programmers. During the testing, two MHC information security analysts and two computer systems analysts will be required. 5.3 Training The training aims to make the UI as easy to use and intuitive as possible. MHC employees will benefit from receiving technical training on the system by participating in the testing process. A user manual will also be provided to make this application even easier to use. In addition, the program will provide access to instructional videos as well as opportunities for on-site training. There are MHC facilities all over the world; As a result, we will offer 24/7 phone and online support to patients, employees, and physicians. It is also recommended that all new hires receive software training as part of the onboarding process. 5.4 Budget We must have at least $1,000,009 in available funds. The employees will receive most of the budget. This is only a rough estimate because we do not yet know how many servers or software licenses we will require. 6. Durations and estimates One year is the current period. The project is supposed to start on August 16 and finish exactly one year later. Even though a full year may not be necessary, it will allow for extensive testing and development to ensure the program's accuracy and effectiveness. The suggested breakdown is as follows: planning and design for one month, development and build for three months, testing for three months, integration for three months, soft testing for two months, and project completion for three months 7. Task dependencies Except for the initial task, the success of each subsequent task is dependent on the success of the previous one. During the development phase, the structure's construction is contingent on the design's completion. Testing will begin once the system has been constructed to its final stage. During this time, features can be evaluated as they are finished. The initial deployment phase will begin following the testing phase. We will collect additional data as required during the system's soft launch period and observe how it performs with a larger user base. We will deploy this globally and familiarize them with the system once everything is finished and we have made the necessary adjustments. 8. Performance monitoring The program will be checked for problems in two different ways. During the soft testing phase, fixing all common issues and concerns is the first step. We will be present to support and oversee the program at 5 this time. Then, in accordance with the contract, for a year, we will be accessible virtually round the clock to assist with any issues that arise. During this time, we will be able to access system statistics and adjust the software to ensure that it runs as efficiently as possible. 6