Project Plan: Mobile Application Development for Healthcare Sector

This project plan outlines the development of a mobile application for the healthcare sector, targeting both healthcare providers and patients. It details the project's purpose, business and project goals (including attracting patients, improving healthcare access, and increasing market share), scope definition, and a comprehensive budget. The plan is structured into six phases: planning, vendor selection, detailed design, execution, testing, and closure. It also includes a risk assessment, milestones, assumptions, constraints, and a project management approach with defined roles and responsibilities. The app aims to provide immediate treatment, appointment scheduling, medication reminders, access to patient history, and a chat feature for communication. The project's success hinges on factors like team efficiency, user knowledge, and clinical engagement. The plan emphasizes the importance of meeting healthcare standards and improving communication between providers and patients. This plan serves as a guide for developing a cost-effective and user-friendly healthcare mobile application.

Development of Mobile Application for Healthcare
Development of Mobile
Application for Healthcare
Author: Your name
Creation Date: date
Last Revised: date
Version: 1.0
INTRODUCTION
Purpose of Plan
The Project Plan defines the following:
 Project purpose
 Business and project goals and objectives
 Scope and expectations
 Roles and responsibilities
 Assumptions and constraints
 Project management approach
 Ground rules for the project
 Project budget
 Project timeline
Background Information

Your Project Name here
The project plan is focused on development of mobile application for healthcare
sector. The mobile app is both accessed by the healthcare providers and
patients. The mobile healthcare (m-health) app placed the patient data from their
past medical data, patient’s feedback and changes in the treatment method. The
healthcare providers access the application for identifying the patient’s problems
and making decisions to go forward with the treatment (O'Reilly-Shah, Easton
and Gillespie 2017). The m-health app is used to receive healthcare as well as
how the patients are communicated with the providers. It makes the patients to
take fully informed medical related decisions, provides them with knowledge and
increases involvement of patients.
Project Approach
The high level summary tasks are as follows
Phase I: Planning phase of healthcare mobile app
Phase II: Selection of the system vendor
Phase III: Detailed design of the healthcare mobile app
Phase IV: Execution of healthcare mobile app
Phase V: Testing of the healthcare mobile app
Phase VI: Closure phase of healthcare mobile app
Phase I: Planning phase
The planning phase for the healthcare app implementation contains
documentation of the project plan, project deliverables and defined project needs
(Kerzner 2017). There is also creation of project schedule which involves to set
the project plan for guiding the project team.
Phase II: Selection of project vendor
The project vendor selection phase includes kick off the project meetings and
define needs for the healthcare mobile app. Market research is conducted to
filter first vendor with providing request for proposal for vendor selection
(Heagne 2016). Review and evaluate responses of vendors and build an
evaluation sheet based on request for proposal.
Phase III: Detailed design phase
1

Your Project Name here
The design phase for the healthcare app includes app programming, feasibility
study, schematic design and development of healthcare app design as well as
contract documents.
Phase IV: Execution phase
In the execution phase, there is acquiring and managing of project team,
execute of project scope, recommended the project changes, timely
communication with the project stakeholder, implement approved project
changes, hold review meeting, and selection of seller for the procurement
requirements (Kerzner 2019).
Phase V: Testing phase
The testing phase contains main four stages which are required to finish before
the program is cleared for use, such as unit testing, acceptance testing,
integration and system testing.
Phase V: Closure phase
The closure phase is included handling of the project deliverables, archiving of
the project documents, closing of contracts as well as release of resources from
the project, lessons learned (Kerzner 2017).
GOALS AND OBJECTIVES
Business Goals and Objectives
The business goals and objectives for this project are:
 Build a customer focused primary healthcare application by attracting 25%
patients in 1 year
 Improve in healthcare access by increasing profitability of business by 10% in
6 months
 Increase in market share by 15% by focusing on the healthcare prevention
 Improve quality, performance and safety in healthcare
Project Goals and Objectives
The project goals and objectives are:
 Provide cost effective healthcare services and meet with established
healthcare standards of quality
 Complete the project work by considering business goals, objectives in
estimated budget and scheduled timeframe
 Provide training in quality improvement in healthcare sector
2

Your Project Name here
 Develop broader improvement advantages across spectrum of the healthcare
 Improve communication among the healthcare providers and patients
 10% change in patient’s knowledge of using the m-health app
 Demonstrate a development in team efficiency behavior
3

SCOPE
Scope Definition
The scope is defined as project work requires to be done to achieve the project
goal and objectives.
Desired Enhancements
 Using the m-health app, the healthcare providers can provide immediate
treatment to the patients 24*7
 Schedule appointment with the healthcare providers anytime
 The healthcare provider provides appointment time, date as per their
availability
 The m-health app provides reminder to the patients for taking medicines
 The app contains past medical history of patients for healthcare provider
review
 Develop the healthcare mobile app on Android and iOS platform
 Chat allows the healthcare providers and patients to exchange of
messages
Items beyond Scope
The project does not include the following:
 Social media to engage and educate patients on healthcare mobile app
 Surveys used to monitor conditions of the patients and collect satisfaction
data of patients
 Wide market research on the healthcare mobile app
Projected Budget
Activities Cost (in $US)
Planning phase of
healthcare mobile app
50,000
Selection of the project
vendor
31,000
Feasibility study 54,000
Detailed project design
phase
19,000
Execution phase 28,500
Testing phase 1,17,000
Training requirements 10,000
Handling of the project
deliverables
15,000
Review of the project plan 7,500
4

Total 3,32,000
Risk Assessment
The initial Risk Assessment (following page) attempts to identify, characterize,
prioritize and document a mitigation approach relative to those risks which can
be identified prior to the start of the project.
The Risk Assessment will be continuously monitored and updated throughout
the life of the project, with monthly assessments included in the status report
(see Communications Plan) and open to amendment by the Project Manager.
Because mitigation approaches must be agreed upon by project leadership
(based on the assessed impact of the risk, the project’s ability to accept the risk,
and the feasibility of mitigating the risk), it is necessary to allocate time into each
Steering Committee meeting, dedicated to identifying new risks and discussing
mitigation strategies.
The Project Manager will convey amendments and recommended contingencies
to the Steering Committee monthly, or more frequently, as conditions may
warrant.
Initial Project Risk Assessment
Risk Risk Level
L/M/H
Likelihood
of Event
Mitigation Strategy
Change in team
member
H: 5 members Certainty Frequent project meetings
and develop communication
plan
Project schedule delay H: Over 1 year Certainty Required proper project
estimation with schedule
baseline review
Scope creep L: Scope are
generally defined
subject to revision
Unlikely Adequate project planning
with the stakeholders and
project charter
Delay in healthcare
data collection
M: Pre-data
collection takes
more time
Likely Increase frequency of data
collection time by limiting
weeks required for pre-data
collection
Project deliverables
not meet with the
stakeholder’s needs
L: Change the
project deliverables
as per request
Unlikely Regular contact as well as
review of project work with
the project stakeholders
Low knowledge level
of the project users
M: Knowledgeable
of user area only
Likely Training providerd to the
users on acheivement of
medical skills
5

Risk Risk Level
L/M/H
Likelihood
of Event
Mitigation Strategy
Low clinical
engagement
M: Engagement
between project
team members
Likely Communication is required
to engage the project team
team
Change request H: Sudden change
in project scope
Likely Focus on the healthcare
research to gather in and out
of scope items of the project.
Unavilabilioty of
human resouurce
M: 7 members Certainty Assign the HR Manager for
technical skills expertises in
healthcare field are being
hired.
Limited coverage to
internet
M: Decrease in
adoption of m-
health
Likely M-health app availability
should expand in poor
covered areas.
Variability in the
technology
L: Decrease in
capability to scale
Unlikely Assign the IT manager to
use interperable technology.
Legal issues M: Applications are
not meet with
standards
Likely Follow the legal guidelines of
app development
Milestones
The following represent key project milestones, with estimated completion dates:
Milestone Estimated Completion Date
Phase I: Planning phase
Initial Steering Committee Meeting 28/04/2020
Phase II: Selection of system vendor
Kick of meeting 18/05/2020
Phase III: Design phase
Completion of design phase 19/06/2020
Phase IV: Execution phase
Completion of execution phase 03/08/2020
Phase V: Testing phase
Completion of testing phase 21/08/2020
Phase VI: Closure phase
Lessons learned 28/09/2020
6

ASSUMPTIONS
Project Assumptions
The following assumptions were made in preparing the Project Plan:
 Management will ensure that project team members are available as needed
to complete project tasks and objectives.
 Failure to identify changes to draft deliverables within the time specified in the
project timeline will result in project delays.
 The healthcare staffs are supportive to implement design approach for m-
health app
 The quality of healthcare mobile app will be approved by the quality
assurance manager (Papke-Shields and Boyer-Wright 2017).
 The ethical approval of the evaluation strategy of the proposed mobile app
will be approved.
 The project will completed on scheduled time of 4 months and estimated
budget of $332,000.
 The mobile app is easier to access by the users and also user friendly.
 The functional requirement of the mobile app has been analyzed (Portny,
2017).
 All business strategies are considered for development of the healthcare
mobile app (Yadav et al. 2018).
CONSTRAINTS
Project Constraints
The following represent known project constraints:
 Project funding sources are limited, with no contingency.
 Due to the nature of law enforcement, resource availability is inconsistent.
 The project requires to be finished within 3 months of time period
 The scope for the project for development of healthcare mobile app is to be
approved by project client.
7

Related Projects
None known.
Critical Project Barriers
Unlike risks, critical project barriers are insurmountable issues that can be
destructive to a project’s initiative. In this project, the following are possible
critical barriers:
 Removal of project funding
 Natural disasters or acts of war
Should any of these events occur, the Project Plan would become invalid.
PROJECT MANAGEMENT APPROACH
Project Timeline
See appendix (insert Gantt chart)
Project Roles and Responsibilities
Matrix
Role Responsibilities Participant(s)
Project
Sponsor
 Ultimate decision-maker and tie-breaker
 Provide project oversight and guidance
 Review/approve some project elements
John Smith
Steering
Committee
 Commits department resources
 Ensure delivery of the project outputs as well
as achievement of the project outcomes
 Providing advices on the changes to project
plan (Young 2016).
 Provide strategic direction to the project
 Support the project manager in taking project
related decisions
Bob Zames
Project
Manager
 Review aspect of the healthcare programme
 Mitigate the project risks
 Coordinate learning session for the users
 Set up project meetings and webinars
 Coordinate the conference calls with the
project sponsor (Badewi 2016).
Please enter your
name
Project
Participants
 Share information about best features of the
mobile app
 Contribute to the project goals and objectives
 Complete the project based on project
Kate Andrews
8

Role Responsibilities Participant(s)
deliverables (Layton and Ostermiller 2017)
 Work with the users for meeting the business
goals and objectives
 Document the project processes
Subject
Matter
Experts
 Ensuring that the project details are correct
 Meeting needs of the legislation and policies
 Testing the communication skills of the users
 Determining quality of the mobile app
(Radujković and Sjekavica 2017).
Mack Sine
Clinical
Advisor
 Help the project manager in developing the
project charter
 Attend the advisory group meetings
 Supporting the project team by answering
their queries
 Providing examples of the project success to
cope up with challenges faced by project team
Jenny Sizh
Quality
Manager
 Understanding expectations of the clients and
need from the mobile app development
 Develop quality processes and standards
 Ensuring that app is designed with devotion to
the legal standards (Meng and Boyd 2017)
 Monitoring the production standards
Jam Sen
Issue Management
The information contained within the Project Plan will likely change as the project
progresses. While change is both certain and required, it is important to note that
any changes to the Project Plan will impact at least one of three critical success
factors: Available Time, Available Resources (Financial, Personnel), or Project
Quality. The decision by which to make modifications to the Project Plan
(including project scope and resources) should be coordinated using the
following process:
Step 1: As soon as a change which impacts project scope, schedule,
staffing or spending is identified, the Project Manager will
document the issue.
Step 2: The Project Manager will review the change and determine the
associated impact to the project and will forward the issue, along
with a recommendation, to the Steering Committee for review and
decision.
9

Step 3: Upon receipt, the Steering Committee should reach a consensus
opinion on whether to approve, reject or modify the request based
upon the information contained within the project website, the
Project Manager’s recommendation and their own judgment.
Should the Steering Committee be unable to reach consensus on
the approval or denial of a change, the issue will be forwarded to
the Project Sponsor, with a written summation of the issue, for
ultimate resolution.
Step 4: If required under the decision matrix or due to a lack of consensus,
the Project Sponsor shall review the issue(s) and render a final
decision on the approval or denial of a change.
Step 5: Following an approval or denial (by the Steering Committee or
Project Sponsor), the Project Manager will notify the original
requestor of the action taken. There is no appeal process.
Communications Plan
Disseminating knowledge about the project is essential to the project’s success.
Project participants desire knowledge of what the status of the project is and how
they are affected. Furthermore, they are anxious to participate. The more that
people are educated about the progress of the project and how it will help them
in the future, the more they are likely to participate and benefit.
This plan provides a framework for informing, involving, and obtaining buy-in
from all participants throughout the duration of the project.
Audience This communication plan is for the following audiences:
 Project Sponsor
 Steering Committee
 Project Manager
 User Group Participants
 Subject Matter Experts
Communications Methodology The communications methodology utilizes
three directions for effective communication:
Top-Down It is absolutely crucial that all participants in this project sense
the executive support and guidance for this effort. The executive
leadership of the organization needs to speak with a unified, enthusiastic
voice about the project and what it holds for everyone involved. This will
be 'hands-on' change management, if it is to be successful (Butt,
Naaranoja and Savolainen 2016). Not only will the executives need to
speak directly to all levels of the organization, they will also need to listen
directly to all levels of the organization, as well.
10

The transition from the project management practices of today to the
practices envisioned for tomorrow will be driven by a sure and convinced
leadership focused on a vision and guided by clearly defined, strategic,
measurable goals.
Bottom-Up To ensure the buy-in and confidence of the personnel
involved in bringing the proposed changes to reality, it will be important to
communicate the way in which the solutions were created. If the
perception in the organization is that only the Steering Committee created
the proposed changes, resistance is likely to occur (Yap, Abdul-Rahman
and Chen 2017). However, if it is understood that all participants were
consulted, acceptance seems more promising.
Middle-Out Full support at all levels, where the changes will have to be
implemented, is important to sustainable improvement. At this level (as
with all levels), there must be an effort to find and communicate the
specific benefits of the changes. People need a personal stake in the
success of the project management practices.
Communications Outreach The following is a list of communication events that
are established for this project:
Monthly Status Reports The Project Manager shall provide monthly
written status reports to the Steering Committee. The reports shall include
the following information tracked against the Project Plan:
- Summary of tasks completed in previous month
- Summary of tasks scheduled for completion in the next month
- Summary of issue status and resolutions
Monthly Steering Committee Meeting These status meetings are held
at least once per month and are coordinated by the Project Manager.
Every member of the Steering Committee participates in the meeting. The
Project Manager sends the status report to each member of the team
prior to the meeting time so everyone can review it in advance.
Bi-Monthly Project Team Status Meeting These status meetings are
held every other month. Every member of the Project Team will be invited
to participate in the meeting. Project Manager sends the status report to
each member of the team prior to the meeting so everyone can review it
in advance.
Website Use User Group Participants and Subject Matter Experts may be
updated monthly at the discretion of the Project Manager. Information will
be posted to the project’s website.
11