Development of Information System in Healthcare Industry

This document provides a plan for the management of the development of information in healthcare industry project. It contains project management plans and details on how the project management process will be applied to this project.

<Sponsoring Organisation>
<Development of Information System in Healthcare
Industry>
PROJECT MANAGEMENT PLAN
Project Title Development of Healthcare System in Healthcare Industry
Project ID Please fill
Document ID PM Plan/2019
Version 1.1
Date 3/14/2019
Project Manager Please fill
Sponsor Please fill
Document History
Revision Date Revision Version Summary of Changes
06/04/2017 1.0 Scope Management Plan
09/12/2017 2.0 Schedule changes
07/06/2018 3.0 Budget changes
04/28/2019 4.0 Project Charter
.
File name: Page 1

Approvals
Name Position Signature Date
Please fill
Please fill
Please fill
Distribution
Name Title Date of Issue Version
Please fill
Please fill
Page 2

Table of Contents
1.0 Introduction...............................................................................................................................5
1.1. About this Document............................................................................................................5
1.2. Background – Problem / Opportunity Statement.................................................................5
2.0. Business Rationale....................................................................................................................5
2.1. Project Benefits & KPIs.......................................................................................................6
2.2. Strategic Alignment..............................................................................................................6
3.0. Project Scope............................................................................................................................7
3.1. Deliverables..........................................................................................................................7
3.2. Work Breakdown Structure..................................................................................................8
3.3. Out of Scope.......................................................................................................................10
3.4. Project Constraints..............................................................................................................10
3.5. Project Assumptions...........................................................................................................11
4.0. Project Time Management.....................................................................................................11
4.1. Project Time Management - Approach..............................................................................12
4.2. Schedule.............................................................................................................................13
5.0. Project Cost Management.......................................................................................................15
5.1. Project Cost Management - Approach...............................................................................16
5.2. Budget.................................................................................................................................16
6.0 Project Human Resource Management...................................................................................18
6.1. Project Human Resource Management - Approach...........................................................18
6.2. Project Team Members.......................................................................................................19
6.3. Responsibility Assignment Matrix.....................................................................................19
7.0. Project Communications Management...................................................................................19
7.1. Project Communication Management - Approach.............................................................20
7.2 Communication Plan...........................................................................................................20
8.0. Stakeholder Management.......................................................................................................20
8.1. Stakeholder Management Plan...........................................................................................21
9.0. Project Risk Management.......................................................................................................22
9.1. Project Risk Management - Approach...............................................................................22
9.2. Risk Register......................................................................................................................23
10.0. Project Quality Management................................................................................................23
10.1. Project Quality Management - Approach.........................................................................24
10.2. Quality Plan......................................................................................................................24
11.0 Project Procurement Management........................................................................................25
11.1. Project Procurement Management - Approach................................................................25
Page 3

12.0 Project Control.......................................................................................................................27
12.1. Progress Reporting...........................................................................................................28
12.2. Change Management........................................................................................................28
12.3. Project Completion Review..............................................................................................28
References.....................................................................................................................................29
APPENDIX A – Schedule.............................................................................................................31
APPENDIX B – Project Budget....................................................................................................32
APPENDIX C – Responsibility Assignment Matrix.....................................................................34
APPENDIX D – Communication Plan..........................................................................................37
APPENDIX E – Stakeholder Management Plan...........................................................................39
APPENDIX F – Risk Register......................................................................................................41
APPENDIX G – Quality Register.................................................................................................43
Page 4

1.0 Introduction
1.1. About this Document
This document provides a plan for the management of the development of information in
healthcare industry project. It contains:
 Description of how the project management process will applied to this project
 Project management plans
The Project Management Plan is the operational document for the project. It is owned,
maintained and utilised by the Project Manager and Project Team to support the delivery of the
project deliverable.
The Project Management Plan expands on the Project Charter and details how’ the Project Team
will carry out their responsibilities to ensure that the objectives in the Charter will occur.
1.2. Background – Problem / Opportunity Statement
The problems related to the management of the data of patients in the healthcare organization are
common. In the healthcare industry, it is required to make use of effective information system
which can store healthcare records of patients and process those data of the patients. Usage of
the information system into the healthcare industry becomes a requirement as there is misplace
of data which can provide bad impact on reputation of organization and health of patients. It is a
key significant requirement of healthcare organization to develop information system for data
storage as well as access which will free from the human errors. Therefore, proposed information
system development is feasible for this project work.
In the healthcare industry, information system has various advantages. It is used to automate
entire process to provide healthcare services to patients. Through this proposed system, booking
of appointments with the doctors are being automated and there is digital generation of
prescriptions. The project work is expected to plan and execute in 16 weeks. The project is
expected to complete in estimated budget of $20,000. The estimated project costs are included
labor cost, materials cost and equipments. The hardware and software costs are also included in
the project plan.
2.0. Business Rationale
In order to provide better quality of the healthcare, in addition to value for money, the healthcare
organizations are spending in development of information system. The system makes informed
decisions for achievement of goals as well as objectives related to healthcare organizations. The
healthcare organization will benefit from implementation of information system in following
ways such as:
Page 5

 Improving the clinical decision making with existing information system
 Reducing the medical errors as well as associated costs
 Improving the safety of the patients
 Decreasing length of stay into the hospitals
 Improving in workflow processes
 Improving physician experimental staffs fulfillment over time
 Reducing and eliminating the paper orders
2.1. Project Benefits & KPIs
The healthcare KPI is defined s performance measurement which is used for monitoring,
analyzing and optimizing the healthcare processes for increasing patient’s satisfaction. In
following table, the benefits and respective KPIs are summarized as:
BENEFITS KPIs
Implementation of information system helps
in better management of healthcare
operations
Reducing the complaints from the customer’s
side by 25% in 2 months of implementation
of information system
Implementation of information system can
decrease processing time of healthcare
services accessible to patients
Reducing waiting time of patients by 30% in
1 month of system execution
Implementation of proposed system helps to
increase business benefits of healthcare
industry
Increasing the number of patient’s served per
day by 10% in 6 months of scheme execution
in healthcare industry
Implementation of information arrangement
helps to reduce treatment costs of patients
Decreasing the treatment cost of patients by
20% in 3 months of system implementation
2.2. Strategic Alignment
The project plan is based on delivering an information system to the healthcare organization so
that it improves over service delivery of the patients. The implementation of healthcare
information system is feasible as it enforces control over the generated information in the
healthcare industry. Due to implementation of healthcare information system, it excels in
provision of safety of patients, quality, timely care of patients and quality of stored data. The
healthcare industry strives to provide such a workplace where both staffs as well as physicians
are envy of the healthcare groups (Kerzner and Kerzner 2017). Implementation of proposed
system will reduce costly human errors, improve safety of patients, and decrease mortality, avoid
duplication of data. It will also save healthcare groups by reducing costs of staffs, developing
billing practices and increasing contract dealing out rate. The information system decreases
Page 6

processing time of services which are obtainable to the patients. It lessens human errors
connected with the data handing out and data storing in the system.
The project work has important necessitate into the healthcare industry and accomplishment of
this project work is acceptable. The entire planning team followed a realistic project plan for
proper development of information system. A project schedule is prepared so that delay in
project activities are avoided to make sure that the plan is completed with scheduled time of 16
weeks.
3.0. Project Scope
3.1. Deliverables
Project deliverables and project requirements are required to identify so that there is proper
implementation of healthcare information system to ensure successful planning and service
delivery to the patients. The deliverables are implemented such that the project can complete in
16 weeks. As time is one of major constraints in project, therefore the project is required to plan
accordingly for successful completion. Following are the key project deliverables and
requirements which are identified as:
Product Deliverables - Description & Requirements
The main project deliverables based on selected project plan are as follows:
 Approval of the project charter by project sponsor
 Estimating the schedule and budget for healthcare information system development
 Documentation of project requirements
 Identification of key project milestones
 Development of project plan
 Designing the healthcare information system
 Predefined design specifications
 Coding, testing and launching the system
 Providing training to the project staffs
 Preparing the closure report
 Acquiring of knowledge on the project management
 Documentation on technical methods and existing project management standards
Apart from the project deliverables, there are key requirements of the project plan so that it helps
to achieve desired project outcomes such as:
 Delivering of working information system to project clients
 Prior testing of information system before deliver it to the project clients
 Designing of information system must friendly with hardware modules of the healthcare
industry for which it is organized
 Prior quality testing of healthcare information system before delivery
Page 7

 Implementation of proposed system is to be completed in 16 weeks
 Completion of proposed system implementation with estimated budget of $20,000
 Maintaining awareness of scope as well as objectives of project
 Ensuring that the status and progress of project is reported on daily basis
 Maintaining the project work and visual plan
Project Management Deliverables
 Project charter
 Project management plan
 Schedule and cost management plan
 Work breakdown structure and Gantt chart
 Scope management plan
 Quality management plan
 Resource management plan
 Stakeholder management plan
 Project control plan
 Risk management plan
 Communication management plan
 Procurement management plan
3.2. Work Breakdown Structure
WBS Task Name
0 Development of Information System in Healthcare Industry
1 Project initiation phase
1.1 Assemble the project team
1.2 Create a business case
1.3 Feasibility study
1.4 Prepare a project charter
1.5 Assign the resources to project tasks
1.6 Schedule the plan
1.7 Estimate the project cost
1.8 Kick off the project meetings
1.9 Development and approval of project plan
2 Software designing phase
2.1 Analyze the performance of software
2.2 Making notes on additional system requirements
Page 8

2.3 Building architecture of the project plan
2.4 Identify design and workflows for information system
2.5 Create a data model
2.6 Identify tools used to create the software
2.7 System development
2.7.1 Detailed identification of project requirements
2.7.2 Identify the project resources
2.7.3 Documentation of project requirements and designs
2.8 Completion of software designing
3 Software coding phase
3.1 Produce the code for software development
3.2 Convert design into code using programming language
3.3 Developing error free executable programs
3.4 Completion of software coding
4 Software testing
4.1 Identify the issues in the system
4.2 Perform testing
4.2.1 Program testing
4.2.2 Product testing
4.2.3 User acceptance testing
4.3 Finding the test results
4.4 Fixing the issues
4.5 Approve for release
4.6 Document the internal design of software
4.7 Maintenance of the software and deployment
4.8 Completion of software testing
5 Training and support to the staffs
5.1 Planning a development team
5.2 Training classes for software users
5.3 Incorporate the organization to adopt new software
5.4 Implementation of training program
5.4.1 E-learning modules
5.4.2 Seminars
5.5 Completion of training to the staffs
Page 9

6 Project closure phase
6.1 Making project documents and deliverables
6.2 Formal acceptance of project deliverables
6.3 Closing the project accounts
6.4 Update and achieve the documents
6.5 Release of the resources
6.6 Review the final project plan
6.7 Finalize the lessons learned
6.8 Development of the project closure report
3.3. Out of Scope
Following are the out of scope based on development of information system in healthcare
industry such as:
 Billing functions are not in scope of the implementation of information system
 Schedule as well as registration are not in scope of current implementation
 Cleaning the backlog of maintenance request for entry of order upgrading and
developments
 The physicians non-order documentation are not in scope such as structured notes, flow
sheets
3.4. Project Constraints
The information system in healthcare plays a key significant role, while it has considerable
project constraints such as:
i. It is anticipated limitations focused on system upgrading and improvements because of
coordination required stopping the system that need continuity of healthcare operations.
ii. It can support higher rate of electronic transactions as various healthcare professionals
have to enter new information.
iii. Ensuring integrity of information at all times even in simultaneous discussion.
iv. It guarantees speed of data display, no matter how the information to look in various
databases.
v. There is delay in the plan activities by means of adding extra human resources are added
to the project schedule.
vi. It can able to handle various transactions at anytime.
vii. There is software errors in area of the information technology applied to the healthcare
industry.
Page 10

viii. There is over budget of the implementation plan due to extra additional of resources and
scope changes.
3.5. Project Assumptions
Certain project assumptions are existed for this particular project plan such as:
a. The selected vendor will provide certified technology which should meet with healthcare
industry requirements.
b. The adopted information system will scalable and patient centric along with secured and
flexible to use.
c. The project resources such as staffs, time, budget and healthcare equipments will
available as per project requirements.
d. The departmental leaders and physicians are on board in the project plan.
e. Information system supported training program will conduct in the healthcare
organization for providing training for physicians, healthcare staffs with 24*7 supports.
f. Each transaction will respect proper functions of databases such that changes occurred
are being recorded furthermore available to the healthcare professionals.
g. Right information will circulate to the healthcare professionals such that the patient will
encounter throughout their stay in the healthcare industry.
h. It is assumed that the project work is completed in scheduled time of 16 weeks and
estimated project cost of $20,000.
4.0. Project Time Management
The entire project plan on development of information system in healthcare industry is scheduled
to complete in 16 weeks. The project milestones of this project with its respective expected start
date are as follows:
Milestone activities Expected start date
Development and approval of project plan Mon 3/25/19
Completion of the software designing Wed 3/27/19
Completion of the software coding Fri 4/12/19
Completion of the software testing Wed 6/12/19
Completion of training of the staffs Fri 6/28/19
Development of the project closure report Mon 7/15/19
In order to complete the project work is scheduled time, the project manager follows the project
management approaches such that it will complete within 16 weeks. The estimated start date is
14th March, 2019 and estimated finish date is 15th July, 2019. Failure to achieve the project
milestones can result to failure in the entire project and delay in the project.
Page 11

4.1. Project Time Management - Approach
At the project management stages based on development of information system in healthcare
industry, the project manager outlines following main six stages for conducting work in this
project plan such as:
Stage 1: Development and approval of project plan
This stage is based on when the project plans are documented, project deliverables, project
requirements are defined and creation of project schedule and budget plan. In this stage, the
project resources are assigned with project tasks based on their skills and knowledge. It is
involved to set plans for helping the team throughout implementation to closure project phases.
The plan is created which help to manage time, risk, and cost and scope changes (Schwalbe
2015). This phase helps to control the staffs as well as external suppliers to make certain that the
project is finished on instance in addition to budget.
Stage 2: Software designing
In this software development phase, the information system is prepared from system requirement
specifications. System design helps to specify both hardware as well as system requirements and
help to define the system architecture. Design specifications of system serves as input for next
phase. The technical details related to system design are being discussed with the project
stakeholders (Fleming and Koppelman 2016). Both time as well as design is reviewed as design
approach for the information system development.
Stage 3: Software coding
After receiving the documents on system design, actual coding of the software is started. Code is
formed which is main spotlight for the software developer. It is best phase of software
development life cycle. The developers started coding of software based on design requirements
(Heagney 2016). The database admin creates data into the database and code the software using
programming languages.
Stage 4: Software testing
The testing is done for new code which the developer has written, reviews the code, creates,
builds, as well as deploys the software to the business environment. The software testing is
repeated until the project requirements are to meet (Walker 2015). The testing is performed for
the software such as program testing, product testing and user acceptance testing.
Stage 5: Training and support of the staffs
Once the customers are started by means of developed system, then actual issues are required to
solve from time to time. This requires training the staffs regarding technical work for
development of information system. Seminars and workshops are conducted for providing
training to the system users and physicians (Harrison and Lock 2017). The healthcare
organization is being incorporated to implement new system in the business operations.
Page 12

Stage 6: Development of project closure report
The closure phase is concerned to complete the project work by making the project documents,
project deliverables and formal acceptance of the project deliverables by project sponsor. The
project resources are released and the project manager finally updated the project final
documents (Kerzner 2018). They reviewed the plan and finalized the lesson learned.
4.2. Schedule
The duration of this project plan is from 03/14/2019 to 07/15/2019.
WBS Task Name Duration Start Finish
1 Project initiation phase 12 days Thu 3/14/19 Fri 3/29/19
1.1 Assemble the project team 2 days Thu 3/14/19 Fri 3/15/19
1.2 Create a business case 4 days Mon 3/18/19 Thu 3/21/19
1.3 Feasibility study 5 days Fri 3/22/19 Thu 3/28/19
1.4 Prepare a project charter 2 days Fri 3/22/19 Mon 3/25/19
1.5 Assign the resources to project tasks 3 days Mon 3/18/19 Wed 3/20/19
1.6 Schedule the plan 3 days Mon 3/25/19 Wed 3/27/19
1.7 Estimate the project cost 2 days Thu 3/28/19 Fri 3/29/19
1.8 Kick off the project meetings 4 days Thu 3/21/19 Tue 3/26/19
1.9 Development and approval of project
plan 0 days Tue 3/26/19 Tue 3/26/19
2 Software designing phase 45 days Thu 3/21/19 Wed 5/22/19
2.1 Analyze the performance of software 3 days Wed 3/27/19 Fri 3/29/19
2.2 Making notes on additional system
requirements 4 days Mon 4/1/19 Tue 5/21/19
2.3 Building architecture of the project plan 15 days Thu 3/28/19 Wed 4/17/19
2.4 Identify design and workflows for
information system 3 days Thu 4/18/19 Mon 4/22/19
2.5 Create a data model 15 days Tue 4/23/19 Mon 5/13/19
2.6 Identify tools used to create the software 6 days Tue 5/14/19 Tue 5/21/19
2.7 System development 45 days Thu 3/21/19 Wed 5/22/19
2.7.1 Detailed identification of project
requirements 1 day Wed 5/22/19 Wed 5/22/19
2.7.2 Identify the project resources 3 days Thu 3/21/19 Mon 3/25/19
2.7.3 Documentation of project
requirements and designs 2 days Tue 3/26/19 Wed 3/27/19
2.8 Completion of software designing 0 days Wed 3/27/19 Wed 3/27/19
Page 13

3 Software coding phase 44 days Tue 3/26/19 Fri 5/24/19
3.1 Produce the code for software
development 13 days Mon 4/15/19 Wed 5/1/19
3.2 Convert design into code using
programming language 17 days Thu 5/2/19 Fri 5/24/19
3.3 Developing error free executable
programs 14 days Tue 3/26/19 Fri 4/12/19
3.4 Completion of software coding 0 days Fri 4/12/19 Fri 4/12/19
4 Software testing 66 days Mon 4/15/19 Mon 7/15/19
4.1 Identify the issues in the system 4 days Mon 4/15/19 Thu 4/18/19
4.2 Perform testing 42 days Fri 5/17/19 Mon 7/15/19
4.2.1 Program testing 15 days Fri 5/17/19 Thu 6/6/19
4.2.2 Product testing 20 days Fri 6/7/19 Thu 7/4/19
4.2.3 User acceptance testing 7 days Fri 7/5/19 Mon 7/15/19
4.3 Finding the test results 20 days Fri 4/19/19 Thu 5/16/19
4.4 Fixing the issues 4 days Fri 5/17/19 Wed 5/22/19
4.5 Approve for release 4 days Thu 5/23/19 Tue 5/28/19
4.6 Document the internal design of
software 3 days Wed 5/29/19 Fri 5/31/19
4.7 Maintenance of the software and
deployment 8 days Mon 6/3/19 Wed 6/12/19
4.8 Completion of software testing 0 days Wed 6/12/19 Wed 6/12/19
5 Training and support to the staffs 22 days Thu 6/13/19 Fri 7/12/19
5.1 Planning a development team 4 days Thu 6/13/19 Tue 6/18/19
5.2 Training classes for software users 3 days Wed 6/19/19 Fri 6/21/19
5.3 Incorporate the organization to adopt
new software 4 days Tue 7/2/19 Fri 7/5/19
5.4 Implementation of training program 15 days Mon 6/24/19 Fri 7/12/19
5.4.1 E-learning modules 5 days Mon 7/8/19 Fri 7/12/19
5.4.2 Seminars 5 days Mon 6/24/19 Fri 6/28/19
5.5 Completion of training to the staffs 0 days Fri 6/28/19 Fri 6/28/19
6 Project closure phase 11 days Mon 7/1/19 Mon 7/15/19
6.1 Making project documents and 3 days Mon 7/1/19 Wed 7/3/19
Page 14

deliverables
6.2 Formal acceptance of project
deliverables 1 day Thu 7/4/19 Thu 7/4/19
6.3 Closing the project accounts 2 days Fri 7/5/19 Mon 7/8/19
6.4 Update and achieve the documents 1 day Tue 7/9/19 Tue 7/9/19
6.5 Release of the resources 1 day Wed 7/10/19 Wed 7/10/19
6.6 Review the final project plan 1 day Thu 7/11/19 Thu 7/11/19
6.7 Finalize the lessons learned 2 days Fri 7/12/19 Mon 7/15/19
6.8 Development of the project closure
report 0 days Mon 7/15/19 Mon 7/15/19
The project schedule diagram shows the Gantt chart of the main project phases required to
conduct the work. The project schedule is in Appendix A.
5.0. Project Cost Management
Verzuh (2015) stated that the project cost management is important aspect of the project
administration help to finish the plan in approved and estimated budget. The knowledge areas
aims to determine the budget for completion of project and monitor, control the project cost to
determine the budget. The cost management involved processes for planning, calculating,
budgeting as well as controlling the cost such that it can finish in estimated budget. Following
are the processes of cost management plan such as:
Plan resources:
 The financial officer estimates the monetary resources required to estimate the budget
and implement the information system.
 It develops an estimation of price of physical and non-physical resources required to
finish the planning work.
Estimate cost of planned resources:
 Each of the resource cost is planned based on their involvement in the project plan.
Allocate cost to activities:
 Each of the project activities are allocated a project cost based on resources involved for
those particular activity (Binder 2016).
 A cost baseline is developed which is required to approve by the project sponsor.
Manage costs:
 There is monitoring and controlling of cost expenditures against the work performed.
 The project costs are managed in project scope and approve the adjustments in the budget
as required (Kerzner 2019).
Page 15

5.1. Project Cost Management - Approach
The total cost of the entire development plan of healthcare information system is $20,000. The
budget plan highlighted of:
 Capital budget
 Server cost
 Testing and maintenance cost
 Salary of human resources
 Technology costs
The project sponsor collects funds for the project work so that there is no lack of project cost for
successful completion of the plan.
5.2. Budget
The total cost for the entire project is $20,000. The breakdown of cost for the main project
activities is shown in following table:
WBS Task Name Cost
0 Development of Information System in Healthcare Industry $20,000.00
1 Project initiation phase $3,200.00
2 Software designing phase $3,120.00
3 Software coding phase $1,760.00
4 Software testing $8,680.00
5 Training and support to the staffs $1,840.00
6 Project closure phase $1,400.00
Figure 5.1: Cost breakdown graph of the main project stages
Role of project resources Cost ($)
Project Sponsor $880.00
Page 16
Project
initiation
phase
Software
designing
phase
Software
coding phase
Software
testing
Training and
suppot to the
staffs
Project closure
phase
$0.00
$1,000.00
$2,000.00
$3,000.00
$4,000.00
$5,000.00
$6,000.00
$7,000.00
$8,000.00
$9,000.00
$10,000.00
Cost Variance

Project Manager $3,240.00
Project Technical Lead $120.00
Training Manager $1,360.00
Functional Lead $280.00
Software Developer $2,720.00
System Analyst $3,440.00
Business Analyst $560.00
Software Tester $4,960.00
Human Resource Manager $1,120.00
Financial Manager $400.00
Programmer $1,080.00
Designer $800.00
Figure 5.2:
Cost
breakdown graph of project resources
The budget breakdown is in Appendix B
Page 17
Project Sponsor
Project Manager
Project Technical Lead
Training Manager
Functional Lead
Software Developer
System Analyst
Business Analyst
Software Tester
Human Resource Manager
Financial Manager
Programmer
Designer
$0.00
$1,000.00
$2,000.00
$3,000.00
$4,000.00
$5,000.00
$6,000.00
Cost Variance

6.0 Project Human Resource Management
Milosevic and Martinelli (2016) stated that the HRM summarizes the project procedures which
facilitate the project manager to guide the entire plan team members. The project team is
responsible for conducting work for each project tasks which are assigned to them. Following
are processes of human resource management such as:
Develop human resource plan:
 Identification and documents the positions of project team members and their
responsibilities. The roles are assigned to each project team members those are taking
part in project work.
 Identification of strategies required to build the project team and program required to
distinguish and reward them (Lock 2017).
Acquire the project team:
 The project staffs are assigned with tasks and the assignments are being documented.
 The resource calendars document time periods of each team members work on the plan.
Develop the project team:
 This process improves competencies and communications among the project group
members and the team environment is enhanced the project performance.
 Enhancing the skills in addition to knowledge of team (Kerzner 2017).
 Enhancing trust and agreement among the members.
Manage the project team:
 Process is used to follow performance of team members, present feedback and determine
the project related issues.
 The project team should manage conflicts, resolve the project issues and observes the
behaviour of each other’s (Nicholas and Steyn 2017).
 The project team management achieves submission of change results, updates the human
resource plan and resolves the project issues.
6.1. Project Human Resource Management - Approach
The setting of human resources is managed based on the abilities as well as knowledge necessary
for conducting the project activities. The human resource management throughout the project is
as follows:
Project Tasks Project Resources involved in project phases
Development and approval of
project plan
Project Manager, Project Sponsor, Business Analyst, Human Resource
Manager, Financial Manager
Software Designing Software Developer, System Analyst, Functional Lead, Project Manager
Software Coding Programmer, Designer
Software Testing Software Tester, System Analyst, Project Manager, Project Sponsor, Business
Analyst, Designer, Software Developer
Page 18

Training and support to the
project staffs
Functional Lead, Human Resource Manager, Training Manager,
Development of project closure
report
Project Manager, Project Technical Lead, Human Resource Manager
6.2. Project Team Members
Following are the project team members those are involved in the project work are as follows:
 Project Sponsor
 Project Manager
 Project Technical Lead
 Training Manager
 Functional Lead
 Software Developer
 System Analyst
 Business Analyst
 Software Tester
 Human Resource Manager
 Financial Manager
 Programmer
 Designer
6.3. Responsibility Assignment Matrix
The Responsibility Assignment Matrix is in Appendix C.
7.0. Project Communications Management
The project communication management is included processes which are needed to make sure of
appropriate planning, controlling along with monitoring of the project related information. The
project manager performs communication with the team members and planning stakeholders.
Effective communication management creates bridge among the stakeholders those have
different cultural plus organizational backgrounds (Heldman 2018). The communication impacts
and influences on the project execution and project outcomes. The project communication
management processes are categorized as follows:
Plan communication management:
 This process is developed as an approach for the project communication based on needs
of project internal and external stakeholders and organizational assets.
Manage communications:
 This process is involved to create, share, store and retrieve of project related information
to other stakeholders for solving project related problems.
Page 19

Control communications:
 Through entire project work, there is controlling as well as monitoring of project
communication to make sure that the project stakeholders can get enough information
related to project plan (Young 2016).
7.1. Project Communication Management - Approach
The project manager and team members used various methods and approaches to manage
communication with other such as:
 Face-to-face or personal communication: Face-to-face meeting
 Mobile communication channels
 Electronic communication methods: Email, social media platforms
 Written methods of communications: Manuals, letters, notices, presentations and
announcements
7.2 Communication Plan
The communication plan documents will store project related information whereas the
employees uses two main methods to store data such as paper based and electronic based. The
communication plan is a roadmap to get messages delivered to the audiences (Joslin and Müller
2015). It is a project management tool used for communicational purposes ensured that the
organization sends specific messages with the measurable project results. The plan included
communication methods, who address the communication and frequency of the communication.
The Communication is in Appendix D.
8.0. Stakeholder Management
The project stakeholder management is consisted of procedures which are needed to recognize
people, groups as well as associations which can impacted by the project plan. It is involved to
analyze the expectations of the stakeholders for developing administration strategies for
appealing the stakeholders plus development decisions (Lientz and Rea 2016). It is focused on
continuous communications with the project stakeholders, managed the conflicts among the
stakeholders and promoted stakeholder engagement into the project related decisions in addition
to project activities. The processes for the project stakeholder management are defined as
follows:
Identify the stakeholders:
The project stakeholders are identified by using stakeholder register to identify people those are
involved in the project plan. It is the process to identify the individuals those can positively and
negatively impacted by the plan (Todorović et al. 2015). Stakeholder register is used to identify
the stakeholders both internal and external stakeholders by analyzing their expectations as well
as impact on the project. There is development of management strategies to engage the
stakeholders.
Page 20

Plan the stakeholder management:
The stakeholder management plan is produced information as well as data. It is a step to
recognize, systematize as well as apply the analysis results of the stakeholders to drive the
project success. It documents approaches which can increase support as well as lessen the
negative impacts of the stakeholders through the project lifecycle. It identifies the stakeholders
with its level of power as well as interest in the project work (Hornstein 2015). It describes
strategies plus actions which is used to manage the stakeholders by using power/interest matrix.
Manage stakeholder engagement:
This process ensures commitment of the project stakeholders at entire stages of the project work.
The influences of project stakeholders are highest at starting point of the project and its
processes influences on the stakeholders to reduce conflicts. There is assistance of the project
sponsor which is taken by the project manager when required. The stakeholder engagement is
managed by using communication plan. It includes documentation of the stakeholder’s
requirements for communicational needs (Turner 2017). Tools which are used to manage
stakeholder engagement are included effective communication methods are email, project
updates and weekly meetings.
Control stakeholder engagement:
It is a process in the project management which can monitor entire project as well as stakeholder
relationships. It is performed by different stakeholder management strategies to engage the
stakeholders. It helps to improve efficiency of the stakeholder engagement activities as the
project lifecycle is continued to evolve because of changes in the project requirements. It ensures
commitment of the stakeholders through entire stage of the project plan (Muller 2017). It makes
sure that stakeholder expectations are meeting with future problems such that it can address
throughout the project lifecycle.
8.1. Stakeholder Management Plan
The stakeholder management plan is a process to develop administration strategies to appoint the
stakeholders during the entire development lifecycle. It is done based on the investigation of the
stakeholder’s needs, interest in addition to impact on the development success. The Stakeholder
Management Plan is in Appendix E
9.0. Project Risk Management
Page 21

The project risk management is a process to classify, analyze and respond the risks which are
raised over project lifecycle which help the project team to be on track to meet its goals. The
risks are required to analyze otherwise it would impact the project timeline, performance and
project budget (Hopkinson 2017). The risk management strategies include extensive detailed
project planning for each of the project risks which ensure to mitigate the risks using strategies.
9.1. Project Risk Management - Approach
Following are steps in the project risk management approaches such as:
Identify the risk:
Risk identification is involved using the checklists of potential project risks and evaluate the
likelihood of project risks that the risk events are happened on the project plan. The industry
develops the risk checklists based on past performance of the project work (Harris 2017). The
sources of project risks are identified by risk category which is considered as other method to
explore potential risks on the project.
Analyze the risk:
The next step is to determine likely of each project risks which are happened. It is performed
using the risk register. Through quantitative and qualitative risk analysis, the project manager
determines the risk factors by how it impacts the project work. The project risks are analyzed
based on activity resources, project duration and cost estimation. It is also analyzed how the risk
is going to provide an impact on schedule in addition to budget. The project team members
identified what are procedures required to manage the project related risks. Qualitative risk
analysis is used to analyze and work through assessment as well as integration of impacts on
project work (Cleden 2017). Quantitative risk analysis is done to perform numerical analysis of
the impact of risks on entire project plan.
Prioritize the risk:
The risks are evaluated to identify how the project resources are going to assemble towards
resolving the occurrence of risks on the project. Some of the project risks are going to acceptable
(Carvalho 2015). The risks are categorized as high, medium and low based on their impact on
project success.
Assign owner to the risk:
While mitigating the project risks, it is required to assign resource to oversee the risks those are
involved to mitigate the risks. The assigned persons for each project risks have skilled and
experienced to mitigate them. It is better to assign task to right person and also important to
ensure that each project risk has resource responsible to mitigate it (Bi et al. 2017). The project
risks are allocated to team members who have impact on the project.
Respond to the risk:
Page 22

For each of the project risks which are identified, it is required to create a plan for mitigate the
project risks. A risk management strategy is developed, with contingency plan for each of the
identified project risks. It is required to act on the project risks by how the risk owner prioritized
it. It is required to make communication with the risk owner as well as created a risk
implementation plan to resolve the risks. The project meetings are managed to prioritize the
project risks (Harris 2017). The risk responses are used to increase opportunities and lessen
impedances towards the project goals.
Monitor the risk:
The risk owner is responsible to track its project progress towards the project resolution. The
project progress is done to identify as well as monitor the new project risks. Communication is
required to monitor the project risks so that it is mitigated using mitigation strategies. The risk
response plan can track identified project risks plus monitor residual risks.
RISK RATING
(Likelihood/
Consequences)
Insignificant Minor Moderate Major Catastrophic
Highly Likely Moderate Moderate High Extreme Extreme
Likely Low Moderate High High Extreme
Possible Low Moderate Moderate High High
Unlikely Low Low Moderate Moderate Moderate
Highly Unlikely Low Low Low Moderate Moderate
Table 9.1: Risk rating table
9.2. Risk Register
The Risk Register is in Appendix F
10.0. Project Quality Management
The project quality management contains processes as well as project tasks of performing project
organization which establishs the quality policies, project objectives as well as project
responsibilities such that the project plan is satisfied with needs which are undertaken (Badewi,
2016). The quality management processes can determine quality standards which are applicable
to development and devise ways to convince them. The objective of this process is to create
quality management plan which can document following such as:
 Way the project team will implement the quality policies
 Way the quality of the project plan and product can assure throughout the project work
Page 23

 The resources are required to make sure about product and project quality
 Additional project resources are required to carry out the quality plan
10.1. Project Quality Management - Approach
The project quality management plan is consisted of three major project processes such as:
Plan quality management:
It is used to identify the quality requirements of project and standards for the project as well as
products. The project team member identifies quality requirements and standards which can
sustain project deliverables in addition to document how the development work will determine
compliances with superiority needs. The quality plan includes metrics for measuring quality
while managing the project plan (Svejvig and Andersen 2015). It is included with quality
checklist to gather and determine scores need to hit throughout the project work.
Perform quality assurance:
It audits quality requirements as well as controls to make sure proper quality standards are to be
used. In this particular process, the project team can perform audit for quality requirements,
results on or after quality control measurements to make certain that there is suitable quality
standards for the project plan (Archibald and Archibald 2016). Quality assurance is planned plus
systematic project activities implemented into quality system such that quality needs for the
information system will fulfill.
Control quality:
It monitors and records consequences of the quality project activities to review project
presentation as well as recommended required changes. In this project process, the project team
can monitor as well as record quality project activities to measure project performance plus
recommend required project changes (Heldman 2018). It is required to check quality of project
deliverables throughout the project management processes to adjust the deliverables when they
are not meeting with quality standards.
The system analyst is the main project stakeholder those can continue superiority of the project
deliverables although the software developer, programmer and tester are dependable for
presentation control of the healthcare information system. The project managers as well as
project management team have responsibility to balance the quality of the information system.
At starting of the project work, the project requirements are to be determined with project
stakeholders. The requirements become foundation of the work for the project plan.
10.2. Quality Plan
The quality plan is in Appendix G
Page 24

11.0 Project Procurement Management
The plan is creation of relationships with the vendors as well as suppliers, goods and services
needed to complete the project work. The project procurement management is required part for
the supply chain management.
11.1. Project Procurement Management - Approach
Following are the processes for the project procurement management such as:
Plan procurement management:
This process involves in formation of official procurement management plan. The decisions are
made to engage the items which are acquired plus the items will be outsourced. This information
provides effect on budget as well as project financial scope (Kerzner 2018). The procurement
documents are prepared and developed to generate selection of the possible project vendors. The
assortment matrix is based on scope, schedule and development requirements.
Selection process:
The selection process is involved to compare and contrast advantages of vendors plus contractual
offerings. The procurement contracts are being decided as well as awarded throughout
collaboration between the procurement managers (Harrison and Lock 2017). The proposals are
being evaluated so that the project procurement team can utilize the online ads for soliciting the
new bidders.
Closing process:
This process is not only ends the procurement contracts and also documents the processes and
summarizes the project for the future requirements. Documentation involves the project team
members in new locations. Throughout the closing process, negotiations are required to
determine the contract disputes (Kerzner 2019). When it comes with the project procurement
management, then the standards and features are analyzed.
The following parts of the Work Breakdown Structure will be procured:
WBS Task Name Procured by Procurement method
1.1 Assemble the project team The employee Procuring from a
Single Source
1.2 Create a business case The employee Request for the project
proposals
1.3 Feasibility study The employee Procuring from a
Single Source
1.4 Prepare a project charter The employee Request for the project
proposals
1.5 Assign the resources to project tasks The employee Procuring from a
Single Source
1.6 Schedule the plan The employee Procuring from a
Single Source
1.7 Estimate the project cost The employee Procuring from a
Single Source
(approval of budget
Page 25

plan)
1.8 Kick off the project meetings The employee Procuring from a
Single Source
2.1 Analyze the performance of software
The employee Procuring from a
Single Source
(through system
specifications)
2.2 Making notes on additional system
requirements
The employee Procuring from a
Single Source
2.3 Building architecture of the project plan The employee
2.4 Identify design and workflows for
information system
The employee Analysis and compare
between the design of
system
2.5 Create a data model The employee Procuring from a
Single Source
2.6 Identify tools used to create the software The employee Procuring from a
Single Source
2.7.1 Detailed identification of project
requirements
The employee Procuring from a
Single Source
2.7.2 Identify the project resources The employee Request for the project
proposals
2.7.3 Documentation of project requirements
and designs
The employee Request for the project
proposals
3.1 Produce the code for software
development
The employee Request for the project
proposals
3.2 Convert design into code using
programming language
The employee Request for the project
proposals
3.3 Developing error free executable
programs
The employee Procuring from a
Single Source
4.1 Identify the issues in the system The employee Procuring from a
Single Source
4.2.1 Program testing The employee Procuring from a
Single Source
4.2.2 Product testing The employee Procuring from a
Single Source
4.2.3 User acceptance testing The employee Procuring from a
Single Source
4.3 Finding the test results The employee Request for the project
proposals
4.4 Fixing the issues The employee Request for the project
proposals
4.5 Approve for release The employee Request for the project
proposals
4.6 Document the internal design of software The employee Request for the project
proposals
4.7 Maintenance of the software and
deployment
The employee Request for the project
proposals
5.1 Planning a development team The employee Procuring from a
Single Source
5.2 Training classes for software users The employee Procuring from a
Single Source
Page 26

5.3 Incorporate the organization to adopt
new software
The employee Procuring from a
Single Source
5.4.1 E-learning modules The employee Procuring from a
Single Source
5.4.2 Seminars The employee Procuring from a
Single Source
6.1 Making project documents and
deliverables
The employee Procuring from a
Single Source
6.2 Formal acceptance of project
deliverables
The employee Procuring from a
Single Source
6.3 Closing the project accounts The employee Procuring from a
Single Source
6.4 Update and achieve the documents The employee Procuring from a
Single Source
6.5 Release of the resources The employee Procuring from a
Single Source
6.6 Review the final project plan The employee Procuring from a
Single Source
6.7 Finalize the lessons learned The employee Procuring from a
Single Source
12.0 Project Control
The project control is critical to achieve successful completion of the project work and project
outcomes such as delivering needed benefits to the project cost, time and business performance.
The project controls are data gathering along with managing used to forecast, recognize plus
control the time as well as budget outcomes of the project. The project control is varied as per
the project requirements, but it can address control aspects of the information system such as:
 Development of project management strategies which will enhance the project
management software usage and its outcomes
 Development, updates and maintenance of project schedules for the project management
software
 Estimate the project cost and controlling the cost for assessment of project values (Muller
2017)
 Managing the project risks and analyzing those risks for avoiding future project risks
 Earned schedule and breakdown structure of the team members
 Quality assessment of the supplied materials
 Addition of elements of control as well as domains for the development management
12.1. Progress Reporting
The Project Management Plan will be controlled by:
 Providing quarterly academic report on the information system
Page 27

 Monitoring status of the project to modernize progress of project plan
 Managing the schedule baseline and cost baseline changes
 Controlling and quality assurance measures undertaken for the materials and equipments
 Plan the change requested approved by the project manager
 Each of the project changes made to the plan is being documented in change request log
 Final submission of design of the healthcare system to the board of directors
12.2. Change Management
Any proposed changes will be processed as follows:
Change in the scope: Through working in the project plan, there is possibility that the scope
behind implementation of information system changes.
Change in schedule: After completion of project work, it is seen that the schedule becomes
behind the schedule due to delay in the one of the project activities.
Change in budget: After completion of project work, it is seen that the budget becomes over
budgeted due to addition to extra project resources.
Change in system specifications: There are changes in features of proposed system and changes
in code of the programming which is used to implement information system.
Change in stakeholder’s interests: There is change in interest of project stakeholders due to
change in the project scope. The management is not interested in the implementation processes.
12.3. Project Completion Review
The section will review the project management documents which will show progress of the
development plan and update the stakeholders about this planning work. Following project
management reports are delivered to be submitted to board of directors and project sponsor such
as:
 Project final report
 Scope process report
 Financial plan
 Schedule management plan
 Documentation on project requirements
 Report on the list of project tasks and processes performed during the project plan
References
Archibald, Russell D., and Shane Archibald. Leading and Managing Innovation: What Every
Executive Team Must Know about Project, Program, and Portfolio Management. Auerbach
Publications, 2016.
Page 28

Badewi, Amgad. "The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework." International Journal of Project Management 34, no. 4 (2016): 761-778.
Bi, Hua-ling, Xiang Jia, Fu-qiang Lu, and Min Huang. "Schedule risk management of it
outsourcing project using negotiation mechanism." In Proceedings of the 23rd International
Conference on Industrial Engineering and Engineering Management 2016, pp. 29-33. Atlantis
Press, Paris, 2017.
Binder, Jean. Global project management: communication, collaboration and management across
borders. Routledge, 2016.
Carvalho, Marly Monteiro de, and Roque Rabechini Junior. "Impact of risk management on
project performance: the importance of soft skills." International Journal of Production
Research 53, no. 2 (2015): 321-340.
Cleden, David. Managing project uncertainty. Routledge, 2017.
Fleming, Quentin W., and Joel M. Koppelman. "Earned value project management." Project
Management Institute, 2016.
Harris, Elaine. Strategic project risk appraisal and management. Routledge, 2017.
Harrison, Frederick, and Dennis Lock. Advanced project management: a structured approach.
Routledge, 2017.
Heagney, Joseph. Fundamentals of project management. Amacom, 2016.
Heldman, Kim. PMP: project management professional exam study guide. John Wiley & Sons,
2018.
Hopkinson, Martin. The project risk maturity model: Measuring and improving risk management
capability. Routledge, 2017.
Hornstein, Henry A. "The integration of project management and organizational change
management is now a necessity." International Journal of Project Management 33, no. 2 (2015):
291-298.
Joslin, Robert, and Ralf Müller. "Relationships between a project management methodology and
project success in different project governance contexts." International Journal of Project
Management 33, no. 6 (2015): 1377-1392.
Kerzner, Harold, and Harold R. Kerzner. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons, 2017.
Kerzner, Harold. Project management best practices: Achieving global excellence. John Wiley &
Sons, 2018.
Kerzner, Harold. Project management metrics, KPIs, and dashboards: a guide to measuring and
monitoring project performance. John Wiley & Sons, 2017.
Kerzner, Harold. Using the project management maturity model: strategic planning for project
management. Wiley, 2019.
Page 29

Lientz, Bennet, and Kathryn Rea. Breakthrough technology project management. Routledge,
2016.
Lock, Dennis. The essentials of project management. Routledge, 2017.
Milosevic, Dragan Z., and Russ J. Martinelli. Project management toolbox: tools and techniques
for the practicing project manager. John Wiley & Sons, 2016.
Muller, Ralf. Project governance. Routledge, 2017.
Nicholas, John M., and Herman Steyn. Project management for engineering, business and
technology. Routledge, 2017.
Schwalbe, Kathy. Information technology project management. Cengage Learning, 2015.
Svejvig, Per, and Peter Andersen. "Rethinking project management: A structured literature
review with a critical look at the brave new world." International Journal of Project
Management 33, no. 2 (2015): 278-290.
Todorović, Marija Lj, Dejan Č. Petrović, Marko M. Mihić, Vladimir Lj Obradović, and Sergey
D. Bushuyev. "Project success analysis framework: A knowledge-based approach in project
management." International Journal of Project Management 33, no. 4 (2015): 772-783.
Turner, J. Rodney. Contracting for project management. Routledge, 2017.
Verzuh, Eric. The fast forward MBA in project management. John Wiley & Sons, 2015.
Walker, Anthony. Project management in construction. John Wiley & Sons, 2015.
Young, Trevor L. Successful project management. Kogan Page Publishers, 2016.
Page 30

Project Management Plan – Development of Information System in Healthcare Industry
APPENDIX A – Schedule
(return)
Figure 1: Gantt chart
[Type text] Page 31

Project Management Plan – Development of Information System in Healthcare Industry
APPENDIX B – Project Budget
(return)
ID WBS Tasks Cost ($)
1 Project initiation phase $3,200.00
1.1 Assemble the project team $240.00
1.2 Create a business case $640.00
1.3 Feasibility study $600.00
1.4 Prepare a project charter $240.00
1.5 Assign the resources to project tasks $600.00
1.6 Schedule the plan $240.00
1.7 Estimate the project cost $160.00
1.8 Kick off the project meetings $480.00
1.9 Development and approval of project plan $0.00
2 Software designing phase $3,120.00
2.1 Analyze the performance of software $240.00
2.2 Making notes on additional system requirements $320.00
2.3 Building architecture of the project plan $1,200.00
2.4 Identify design and workflows for information system $120.00
2.5 Create a data model $240.00
2.6 Identify tools used to create the software $480.00
2.7 System development $520.00
2.7.1 Detailed identification of project requirements $120.00
2.7.2 Identify the project resources $240.00
2.7.3 Documentation of project requirements and designs $160.00
2.8 Completion of software designing $0.00
3 Software coding phase $1,760.00
3.1 Produce the code for software development $520.00
3.2 Convert design into code using programming language $680.00
3.3 Developing error free executable programs $560.00
3.4 Completion of software coding $0.00
Page 32

4 Software testing $8,680.00
4.1 Identify the issues in the system $0.00
4.2 Perform testing $3,360.00
4.2.1 Program testing $1,200.00
4.2.2 Product testing $1,600.00
4.2.3 User acceptance testing $560.00
4.3 Finding the test results $3,200.00
4.4 Fixing the issues $320.00
4.5 Approve for release $800.00
4.6 Document the internal design of software $360.00
4.7 Maintenance of the software and deployment $640.00
4.8 Completion of software testing $0.00
5 Training and support to the staffs $1,840.00
5.1 Planning a development team $480.00
5.2 Training classes for software users $240.00
5.3 Incorporate the organization to adopt new software $320.00
5.4 Implementation of training program $800.00
5.4.1 E-learning modules $400.00
5.4.2 Seminars $400.00
5.5 Completion of training to the staffs $0.00
6 Project closure phase $1,400.00
6.1 Making project documents and deliverables $480.00
6.2 Formal acceptance of project deliverables $120.00
6.3 Closing the project accounts $240.00
6.4 Update and achieve the documents $120.00
6.5 Release of the resources $80.00
6.6 Review the final project plan $120.00
6.7 Finalize the lessons learned $240.00
6.8 Development of the project closure report $0.00
Total: $20,000
Page 33

Project Management Plan – Development of Information System in Healthcare Industry
APPENDIX C – Responsibility Assignment Matrix
(return)
WBS Task Name
Project
Sponsor
Project
manager
Project
Technical
Lead
Training
Manager
Functiona
l Lead
Software
Developer
System
Analyst
Business
Analyst
Software
Tester
Human
Resource
Manager
Financial
Manager
Program
mer
Designer
0 Development of Information System in
Healthcare Industry
1 Project initiation phase
1.1 Assemble the project team R R
1.2 Create a business case R R A
1.3 Feasibility study R R A
1.4 Prepare a project charter R R C I I A I I I A
1.5 Assign the resources to project tasks R I I A A I I A
1.6 Schedule the plan R R A
1.7 Estimate the project cost R R C I I
1.8 Kick off the project meetings R I I
1.9 Development and approval of project
plan
2 Software designing phase
2.1 Analyze the performance of software R I A I A A I C I
2.2 Making notes on additional system
requirements R I A I A A I C I
2.3 Building architecture of the project
plan R I A I A A I C I
2.4 Identify design and workflows for
information system R I A I A A I C I
2.5 Create a data model R I A I A
[Type text] Page 34

2.6 Identify tools used to create the
software R I A I A R I A I A
2.7 System development
2.7.1 Detailed identification of project
requirements R I A I A
2.7.2 Identify the project resources R I A I A
2.7.3 Documentation of project
requirements and designs R I A I A
2.8 Completion of software designing
3 Software coding phase
3.1 Produce the code for software
development R I A I A A
3.2 Convert design into code using
programming language R I A I A A
3.3 Developing error free executable
programs R I A I A A
3.4 Completion of software coding
4 Software testing
4.1 Identify the issues in the system R I A I A
4.2 Perform testing
4.2.1 Program testing A R I A I A
4.2.2 Product testing A R I A I A
4.2.3 User acceptance testing A R I A I A
4.3 Finding the test results A R I A I A
4.4 Fixing the issues A I I A I R
4.5 Approve for release R A I A A I A
4.6 Document the internal design of
software R A I A A I A
4.7 Maintenance of the software and
deployment R A I A A I A
4.8 Completion of software testing
5 Training and support to the staffs
File Name: 11687263391624336308.docx Page 35 of 44

5.1 Planning a development team R R A I A A I
5.2 Training classes for software users R R
5.3 Incorporate the organization to adopt
new software R R
5.4 Implementation of training program
5.4.1 E-learning modules R
5.4.2 Seminars R
5.5 Completion of training to the staffs
6 Project closure phase
6.1 Making project documents and
deliverables R R
6.2 Formal acceptance of project
deliverables R R
6.3 Closing the project accounts R R
6.4 Update and achieve the documents R R C I I A I I I
6.5 Release of the resources R I I A A I I
6.6 Review the final project plan R R C I I A I I I
6.7 Finalize the lessons learned R R C I I A I I I
6.8 Development of the project closure
report
Date: 6/18/2019
File Name: 11687263391624336308.docx Page 36 of 44
LEGEND
R – Responsible (for executing activity) A – Accountable (buck stops here) I – Informed (FYI) C – Consult (must)

APPENDIX D – Communication Plan
(return)
Key Reports / meetings Who to receive Frequency Method
The status report of the
project
The project team members
and project sponsor
Weekly Email and project presentation
The team members
allocation
The project team members Before starting the project plan Meetings and conferences
Building architecture of
the project plan
The software developer Weekly basis Email and project presentation,
Weekly meetings
Updates on the
progresses of the project
tasks
The project team members On regular basis Email and project presentation
Review the project plan Project Sponsor At the project milestones Email and project presentation,
Weekly meetings
Post-project meeting on
the project success
The project team members At the end of the project plan Email and project presentation
Testing plan of the System Tester When working on the testing Email and project presentation
[Type text] Page 37

information system phase
Finalize the project
deliverables
Daily basis Weekly basis Check-in project meetings and emails,
presentations
Coding documents Programmer Weekly basis Email and project presentation
Final approval of the
project milestones and
strategic directions
The project technical lead After completion each project
phases
Face-to-face meetings and
conferences, emails
Patient and family
complaint history
Weekly written report Weekly written report Check-in project meetings and emails,
presentations
Existing issues with the
current information
system processes
The project team members Weekly (at the time of
stakeholder meetings)
Face-to-face meeting
Training manuals Training manager Weekly basis Emails and presentations
[Type text] Page 38

APPENDIX E – Stakeholder Management Plan
(return)
Stakeholder Stake/Interest Action Responsibility By When Status
Project Sponsor Create the business case
and approve the project
release
Sign off the key decisions
and project phases
Facilitate the stakeholder
meetings
By 28th
March,
2019
On
progress
Project Manager Assemble the project team
members,
Feasibility study on the
project areas
Prepare an agenda which
allows the sources to
discuss and prepare the
project charter
By 4th April,
2019
On
progress
Project technical
lead
Making the project
documents and
deliverables
Review the project
deliverables
Technical skills to analyze
existing information
system
By 15th
April, 2019
On
progress
Training Manager Performing training classes
for the software users
Incorporate the
organization for adopting
new software
Performing training
programs such as E-
learning modules and
seminars
By end of
month
April, 2019
On
progress
Functional Lead Identification of design and
workflows for the
information system
Plan a team for
development of
information system
Function entire
development of healthcare
information system
By first
week of
June, 2019
On
progress
Software Developer Analyze the performance
of the software
Creating a data models Maintenance of the system
and deployment
By 9th April,
2019
On
progress
System Analyst Making notes on additional Building architecture of Document the requirements By 20th Completed
Page 39

information system
requirements
the project plan of information system and
its designs
April, 2019
Business Analyst Create the business case on
healthcare information
system
Document the internal
design of the software
Analyze current operations
of healthcare organization
By end
week of
April, 2019
On
progress
Software Tester Perform the information
system testing
Perform product, program
and user acceptance
testing
Findings the test results as
per project requirements
On 15th
May, 2019
On
progress
Human Resource
Manager
Assign the project
resources to the project
tasks
Schedule the project team
members
Hire more team members
based on the skills and
knowledge required to
perform the project tasks
By last
week of
May,2019
Completed
Financial Manager Estimate the project cost Prepare a budget plan Kick off the project
meetings
By first
week of
June, 2019
On
progress
Programmer Produce code for the
development of software
Develop error free
executable programs
Coding the information
system for healthcare
industry
By 19th
June, 2019
On
progress
Designer Convert design into code
by means of programming
language
Document the internal
design of the software
Design the information
system based on project
requirements
By 29th
June, 2019
On
progress
Page 40

APPENDIX F – Risk Register
(return)
Risk
Id
Risk Event Likelih
ood
Conseque
nce
Ratin
g
Treatment Responsibl
e
Officer
By
Date
Status
R1 Schedule risk: It is occurred when the
project is implemented in constricted project
timeframe.
Likely Minor High A proper project plan is
developed to consider all
the project activities
required and completed in
the project work.
Project
Manager
15th
April,
2019
Solved
R2 Unavailability of project resources: Proper
and required project resources are not
involved and hired to perform the project
work.
Possible Major High Skilled as well as
knowledgeable resources
are required to be chosen.
Human
resource
manager
29th
April,
2019
In progress
R3 System failure: The implemented healthcare
information system is failed as the software
being implemented in much constricted
timeframe.
Unlikel
y Catastrophi
c
Moder
ate
A significant amount of
time is allocated for testing
the healthcare information
system.
System
Analyst
3rd
May,
2019
In progress
Page 41

R4 Lack of proper training: There is lack of
training provided to the project team
members as the staffs are new to
implementation of information system.
Possible Major High
Training program should
require developing as part
of this particular project
work.
Training
Manager
16th
May,
2019
In progress
R5 Operational risk: There is improper testing
of the information system. Likely Major High
Testing of the healthcare
information system should
require to done properly.
Tester 25th
May,
2019
In progress
R6 Budget risk: Due to addition of extra
resources to the project plan, there is an
increase in project budget over the planned
cost.
Likely Minor High There is required to use
project schedule for
estimating the cost based on
the project plan.
Project
Manager
13rd
June,
2019
In progress
R7 Technical risk: The system is not operated
as per planned project requirements due to
wrong coding of the information system. Possible Moderate Moder
ate
Proper coding of the
software should require
performing based on
system’s requirements.
Programmer 15th
June,
2019
In progress
Page 42

APPENDIX G – Quality Register
(return)
WBS # Product Name Quality Acceptance
Criteria
Quality Check
Method
Quality Checker Quality Checker Result of Quality
check
2.7.1 Detailed identification of
project requirements
Cover requested level of
project details
Obtaining
information system
according to project
specifications
Project Sponsor Project Manager Fulfill 100%
requirements of the
project clients
3.1 Produce the code for
software development
Cover requested level of
coding for the information
system
Obtaining
information system
according to project
specifications
Programmer System Developer Quality fulfills project
specifications and
guidelines 100%
4.3 Finding the test results Cover requested level of
testing for implementation
of healthcare information
system
Obtaining
information system
according to project
specifications
System Tester System Developer Cost of the testing in
system specifications
4.7 Maintenance of the
software and deployment
Software testing for proper
implementation
Obtaining
information system
according to project
specifications
System Developer System Analyst Detailed project plan
for software
maintenance
5.2 Training classes for
software users
Training is provided to the
staffs have lack of technical
knowledge
Obtaining
information system
according to project
specifications
Training Manager Project Manager Training manuals
required
6.2 Formal acceptance of Cover requested level of Obtaining Project Manager Project Sponsor All basic
Page 43

project deliverables project details information system
according to project
specifications
requirements of
project stakeholders
are fulfilled
END OF
PROJECT MANAGEMENT PLAN
Page 44