Project Planning and Risk Analysis: An IOT Healthcare Application

This project report details the project planning and risk analysis for an IOT-based healthcare application. The project plan outlines various components, activities, and resource assignments, estimating a total project time of 14 months and a cost of $900,000. Agile project management is identified as the most suitable methodology, with considerations for Waterfall, PERT, and Prince2 methods. Estimation techniques such as PERT, Critical Path Method (CPM), Work Breakdown Structure (WBS), and Gantt charts are discussed. The risk analysis section covers risk acceptance, mitigation, and transfer strategies, employing methods like brainstorming, flowchart analysis, and SWOT analysis to identify and address potential risks such as inaccurate resource allocation, improper cost estimation, and lack of technical knowledge among team members. Mitigation strategies are developed for each identified risk to ensure successful project implementation. The report also includes a Gantt chart and a Work Breakdown Structure diagram for visual representation of the project schedule and task breakdown.

Running head: PROJECT MANAGEMENT
Project management: Project plan and Risk Analysis
Name of the student:
Name of the university:

1PROJECT MANAGEMENT
Project plan and risk analysis
1. Project plan
This particular section of the report focuses on details of project planning. The software
design document includes different components and activities and based on the skills, approach
and knowledge of the project team members the activities are individually assigned to separate
resources. As soon as the tasks or activities are assigned it become their responsibilities to
accomplish assigned roles within estimated time maintaining all project requirements. After
estimating and analyzing the IOT based healthcare application project details it is determined
that the total time and cost needed or the projects are respectively 14 months and $900,000. Te
methods and estimation techniques that are employed to conduct the project are also elaborated
in the below section.
1.1 Methods applied to conduct the project
There are different methods used by the project managers and project team members to
deploy a cloud based project for the client companies. Agile, scrum, waterfall, Adaptive project
framework and PERT are the most widely used methodologies that helps to estimate the project
including identification of tasks, duration, resource identification etc. However, Agile project
management method is the most suitable one for this specific project. The details of such method
are elaborated below:
Waterfall method: This is the most generic and simple project development method used
to conduct any project successfully. This method is comprises of five phases in terms of
requirement gathering and analysis, design, implementation, verification and maintenance. At the

2PROJECT MANAGEMENT
initiation phase of this method the consumer specified requirements are listed to successfully
develop the content, design and plan for the project. After creating the physical product the
integrated system is validated and verified respectively to ensure whether it is ready to be
launched in the market or not.
Agile method: This method is most suitable for developing software products based on
the consumer’s expectations. The agile project managers are focused on creating ways for
delivering value after interacting with the consumers. The project managers have also expanded
the concept in many implementation frameworks which include extreme programming, scrum
project management etc.
PERT: Program Evaluation Review technique (PERT) is used to measure the time,
duration and cost of any project. This approach acts as tool used to plan activities within a
project to make the project easier. It helps to structure project schedule and make proper
coordination among the project team members. The PERT chart also helps to manage and
accomplish the work within estimated timeframe.
Prince2 method: The Prince2 method is also known as a process based method that is
used to achieve the project objectives an goals much effectively and efficiently. This method is
strictly business focused and helps to define organizational structure for the project manager.
This product based planning approach gives flexibility to the project team members and also
gives them controllable stages.

3PROJECT MANAGEMENT
1.2 Usage of estimation technique
There are different techniques used to create project plan including identification of tasks
its respective duration, resources and key milestones as well. The techniques are illustrated in
the below section:
PERT management method: For both the large scale small scale projects this estimation
method is very much applicable. However, for one time manufacturing and development
processes this technique is profitable. Through using this technique project manager can make
differentiation between the activities and events.
Critical path method: The Critical Path Method is focused on speeding up any task by
measuring its priority. Any project shows various directions following those it can be
accomplished. CPM governs the project through the most simple and easy direction. A project
manager can provide a clear and visible picture to the project team members by using the
concept of CPM.
Work Breakdown Structure: WBS is the other useful tool or technique used for
developing and sub-diving project activities. In order to complete the project within estimated
time frame and budget this is mandatory to segment the task into small parts. Individuals will be
assigned to those activities according to their responsibilities.
Gantt chart: Gantt chart is used to track any project and it makes the status and structure
of the project visible to the project team members. After completion of each phase the Gantt
chart must be monitored and checked by the project team members to understand what possible
changes are required to be incorporated by the project team members.

4PROJECT MANAGEMENT
1.3 Graphic images
Figure 1: Gantt chart of the project
(Source: created by author)

5PROJECT MANAGEMENT
IOT project development
schedule
Project initiation
Defining scope of
the project
Feasibility study to
determine project
cost
Contract to
suppliers
Selection of
vendors
Identify IOT modules
Project planning
Purchasing software
Purchasing
hardware
Risk management
plan
Stakeholder
management plan
Security
implementation
Procurement
management plan
Project execution
Project subdivision
Design prototype
Developing
prototype
Simulation
Final simulation
Project monitoring and
control
Unit testing
Integrated testing
Acceptance testing
IOT based
healthcare Project
launching
Project closure
Stakeholder signoff
Final document
submission
Post project
maintenance
planning
Figure 2: Work Breakdown Structure of the project
(Source: created by author)
2. Risk analysis
2.1 Discussion on the methods that are to be employed
The purpose of applying this IOT application in the healthcare center is to keep the health
records of the patients updated. This cloud based IOT system would be able to store huge
amount of information with high security functionalities. During the diagnosis of the patients the
doctors will be able to access needful information from the server. Not only this but also, with
advancement in technologies the doctors will also be able to update the patient’s current health
status. The patients can take the doctor’s appointment with this updates system much efficiently
and effectively. Though, certain risks are associated to this those have been identified. The

6PROJECT MANAGEMENT
details of the risk management approach are elaborated in the below section. The methods that
are deployed to conduct risk management include the following:
Risk acceptance: There are certain risks which cannot be easily mitigated such as
operational risks theses risk are needed to be accepted first by the project team members and then
accordingly mitigation strategies must be developed.
Risk mitigation: The risks such as improper resource, time and cost management risks
are needed to be mitigated to obtain structured revenue and competitive advantages all over.
Risk transfer: The risk of investment and insurance should be transferred instead of
mitigating this.
Risk mitigation: The risks of lack of communication and lack od technical knowledge
are needed to be mitigated by the project manager.
2.2 Using risk identification methods
There are different methods thorough which risks of any project can be easily identified.
The process of risk management uses various formula and templates accordingly and that are
mostly based on industrial practices. The methods of risk identification are as follows:
Brainstorming: The session of brainstorming become much clear and visible to the
participants when the objectives of the project are stated directly and understood by the project
team members at the initial phase. Brainstorming helps to identify the risks associated to any
project. For this specific project through brainstorming the risk that is identified is wrong
resource allocation.

7PROJECT MANAGEMENT
Flowchart method: This is the other method utilized for graphical, sequential
management of needful activities. Through flowchart method the risk that has been identified for
this project is improper cost and time estimation for the project.
SWOT analysis: The SWOT analysis is referred to as the tool that is used to identify the
strength, weaknesses, opportunities and weakness of any project easily. The project strength
gives it effective opportunities on the other hand the weakness of the project gives it further
threats. The threats that are identified through this method is lack of training and skills among
the working project team members.
2.3 Development of risk mitigation strategies
Risk
Id
Identified risks
for the project
Likelihood Impact Probability Mitigation strategies for
the identified risks
R12 Inaccurate
allocation of
resources
Unlikely m Extreme Based on the requirement
of the project the project
manager and the project
team members are required
to assign accurate resources
for the project. It is the
responsibility of the project
manager to accomplish the
project within the assigned
resources only to avoid
over resource allocation

8PROJECT MANAGEMENT
issues.
R23 Improper
allocation of cost
Likely Severe High Based on project
complexities the project
managers are required to
allocate cost for the tasks.
Additionally feasibility
study is also needed.
R5 Improper
estimation of
project time frame
Possible Significant Low Depending upon the project
complexities, skills and
knowledge of the project
managers and team
members at the initial phase
time period should be
designed.
R8 Lack of leadership
and
communication
strategies
Very
unlikely
Minor Medium The project associates must
use open communication
while interacting with each
other.
R2 Lack of technical
knowledge among
the users and
project team
members
Very likely Medium Medium While developing the IOT
based healthcare system on
job technical training
program needs to be
arranged by the HR

9PROJECT MANAGEMENT
manager.

10PROJECT MANAGEMENT
References
Albliwi, S., Antony, J., Abdul Halim Lim, S., & van der Wiele, T. (2014). Critical failure factors
of Lean Six Sigma: a systematic literature review. International Journal of Quality &
Reliability Management, 31(9), 1012-1030.
Bodily, R., Nyland, R., & Wiley, D. (2017). The RISE Framework: Using Learning Analytics to
Automatically Identify Open Educational Resources for Continuous Improvement. The
International Review of Research in Open and Distributed Learning, 18(2).
Cohen-Vogel, L., Tichnor-Wagner, A., Allen, D., Harrison, C., Kainz, K., Socol, A. R., & Wang,
Q. (2015). Implementing educational innovations at scale: Transforming researchers into
continuous improvement scientists. Educational Policy, 29(1), 257-277.
Conger, S. (2015). Six sigma and business process management. In Handbook on Business
Process Management 1 (pp. 127-146). Springer, Berlin, Heidelberg.
First, M. B. (2016). Adopting a continuous improvement model for future DSM revisions. World
Psychiatry, 15(3), 223-224.
Hambach, J., Tenberg, R., & Metternich, J. (2015). Guideline-based video analysis of
competencies for a target-oriented continuous improvement process. Procedia CIRP, 32,
25-30.
Heinemann, B., Ceauau, I., Buchmüller, M., & Kopia, J. (2017). Quality Management System
Certification and the Continuous Improvement Process by the Example of a Training
Company in Germany. Calitatea, 18(156), 97.

11PROJECT MANAGEMENT
Ivey, M., Dew, S., Mandal, M., Mohamed, Y., Nychka, J. A., Raboud, D., & Carey, J. P. (2017).
USING POST COURSE ASSESSMENTS TO INVOLVE INSTRUCTORS IN THE
CONTINUOUS IMPROVEMENT PROCESS. Proceedings of the Canadian
Engineering Education Association (CEEA).