LS Project

Your Name Here

June 4, 2020
Table of Contents

1. INITIATING A PROJECT 1

1.1 Business case 1

1.2 Goal and objectives statement 1

1.3 Stakeholder engagement 2

1.3.1 Table of stakeholders 2
1.3.2 Stakeholder matrix 3
1.3.3 Stakeholder management 4

1.4 Communication plan 5

2. PLANNING A PROJECT 7

2.1 Determine the components 7

2.1.1 Component 1: Initiation 7
2.1.2 Component 2: Planning 7
2.1.3 Component 3: Execution 7
2.1.4 Component 4: Monitor and Control 7
2.1.5 Component 5: Closing 7

2.2 Component analysis 8

2.2.1 Component 1 8
2.2.2 Component 2 9
2.2.3 Component 3 11
2.2.4 Component 4 14
2.2.5 Component 5 16

2.3 Risk management 18

2.3.1 Risk matrix 18
2.3.2 Threshold value(s) 19
2.3.3 Risk graph 19
2.3.4 Risk actions 20

2.4 Statement of work document (SOW) 21

2.4.1 Background 21
2.4.2 Component by component discussion of inclusions 21
2.4.3 Assumptions that require mentioning 21
2.4.4 Major risks 22
2.4.5 Exclusions 22

2.5 Work breakdown structure (WBS) 23

2.6 Project scheduling: Network diagram 24

2.6.1 Activity data 24
2.6.2 Network diagram 25

2.7 Project scheduling: Gantt chart 26

2.8 Cost estimation 27

2.9 Determine budget 28

2.9.1 Project budget 28
2.9.2 Project baseline 29

3. MONITORING AND CONTROL 30

3.1 Progress reports 30

3.1.1 Progress summary report on activity level for Time Now 30
3.1.2 Cost summary report on activity level for Time Now 30

3.2 Earned value management 32

3.2.1 Project EVM analysis on activity level for Time Now 32
3.2.2 EVM summary on project level for Time Now 34

3.3 Project report for Time now 34

4. REFERENCES 36
1. Initiating a Project
Business case

The name of the project is ‘Self-Registration Kiosk’ and it is about the development
of an online system that will assist patients in booking appointments for check-ups
or follow up appointments at the Cresta Healthworx Centre. The main aim of the
project is to address the issue of the frustratingly long queues that patients have to
succumb to when they go to the centre, seeking for medical attention with a
medical professional. Additional to this, it is sometimes difficult for some of patients
to even fulfil or recall any check-up appointments made with the Health Centre,
due to the reality of busy schedules that people sometimes have. In looking at this
problem, the proposed solution for this issue, is to develop an online system for
booking appointments for consultations with their specified Doctor. This system
can be accessible on their computers or mobile phones which makes it more
convenient for any patient to make an appointment on the fly. With this system in
place, patients that have made an online appointment are also then provided with
reminder notifications the day before they are due to see the Dr and on arrival at
the centre, are given a receipt once they provide their patient ID and head straight
to the Dr’s rooms without having to wait in long queues. The proposed system will
be developed using current and modern technology namely, C# and Microsoft SQL
Server Studio Database.
Goal and objectives statement

The key goal of the project is to complete the system development within budget
($50,000) and timeline (5-months) specified. The project is mainly taken into the
consideration to enhance the service provided at the Cresta Healthworx Centre
and improving its operations and transactions by using the online self-registration
system. The technology behind the development of the system are the
programming languages Asp.net/C# as well as Microsoft SQL Server Studio
Database MySQL for the database or backend. Both these languages were
considered and with research, have found that they both can reduce processing
time. As a result, they will also improve the facilitation of the services in the Health-
Centre creating a benefit to the Health-Centre staff as well as the clients of the
Health-Centre.

The objectives of the system are:

 To manage and maintain patients records
 To keep a record of patient’s appointment details with the Health-Centre.
 To maintain the patient’s vs doctors’ records and their consultation details
i.e. historical records of test results
 To accept the payments from patients and to keep a financial record of
transactions for the Health-Centre up to date.
 To automate the current process that exists at the Cresta Healthworx
Centre

Stakeholder engagement

1.3.1 Table of stakeholders

Internal stakeholders External stakeholders

Project Manager Tester

Health-Centre Finance Manager Database Administrator
Health-Centre Staff System Designer
Health-Centre IT Manager Developer
Trainer
1.3.2 Stakeholder matrix

INFLUENCE ON
VH
Health- Hospital
Centre IT Financial
Manager Manager
H

Project
Manager
M

AGAINST PROJECT
FOR PROJECT

VH H M L L M H VH

M
Tester,
System
Designer
Database H

Hospital
Staff VH
INFLUENCED BY
1.3.3 Stakeholder
management

Project title
Stakeholder Assessment of impact
Stakeholder interest(s) in the (attitude to and influence Potential actions
project on or influenced by)

Meet with the Health-

 Must oversee each Centre IT Manager,

and every stage of the  Ally (High for the Finance Manager and
 Project
project and ensure all project and high Health-Centre staff to gain
Manager
stakeholders are on influence on) as much information as

board possible and ensure that a

common understanding is

gathered for the project.

Have a meeting with the

Project Manager and

Health-Centre IT Manager
Heath-Centre Has a big influence on  Ally (High for the
to discuss what can will be
Finance the funding for the project and very high
in scope and what will be
Manager project to take place influence on)
out of scope for the project

as this impacts the costs of

the project.
Has a huge say in the Must meet with the Project
Health- Ally (Very high for the
existence of a new Manager to gain a system
Centre IT project and very high
system to take over walk-through and what the
Manager influence on)
the current system new system should do
 Must assist and

cooperate with the Have meetings with the

Project Manager by Project Manager, Health-

providing him with as Supporter (Medium for Centre IT Manager, and

Health-
much information as the project and Designer to provide details
Centre Staff
possible on the current very high influence by) of advantages and

existing system and all challenges of the current

the details pertaining system.

to it
Must sit with the Heath-

Centre IT Manager and

Will provide the Supporter (Low for the
System work with him to discuss
planning of the project and High
Designer the plan that he has in place
software system influenced by)
for the designing of the

system
Database Will look at the Supporter (Low for the Will develop the back-end

Admin current system and project and High and the database for the

adequate if there is influenced by) system.

adequate

infrastructure for the

addition of a new

system or to

decommission the old

one to make space for

the new online

 system.
Will accept and Will start implementing the

understand the design Supporter (Low for the online-registration kiosk

Developer specifications project and High system from the

provided by the influenced by) specifications provided by

system designer the system designer

 Validates and verifies the
Will test the solution  Supporter (Low for the
project requirements by
 Tester executed by the project and High
performing system and
developer influenced by)
user acceptance testing
Will be on call to

equip the Health-

Supporter (Low for the
Centre staff with skills Responsible for training
Trainer project and High
to use the new online- the users and hospital staff
influenced by)
registration kiosk

system
Communication plan

Content of Method of Frequency of

Stakeholder Position in respect of project
communication/action communication/action communication/action

Project progress and Email, Live Meeting or

George  Project Manager Daily or Weekly
performance Phone Call
 Health-Centre Finance Project funding and Email, Live Meeting or
Lynda Daily or Weekly
Manager budget performance Phone Call
Health-Centre IT System reviewer and Email, Live Meeting or
James Daily or Weekly
Manager check point Phone Call
Review and feedback
Maria  Health-Centre Staff Live Meeting Daily or Weekly
about the system
Testing result or test Email, Live Meeting or Once (During Testing
Lana Rose  Tester
planning Phone Call Phase)
Design plan and Email, Live Meeting or Daily or Weekly (During
Micky John Designer
prototype discussion Phone Call design phase)
Email, Live Meeting or
Alexander Developer Development progress Daily or Weekly
Phone Call
Gloria Trainer Training plan Email, Live Meeting or Once
 Phone Call
Database development Email, Live Meeting or
William Database Admin Daily or Weekly
planning Phone Call
2. Planning a Project
Determine the components

2.1.1 Component 1: System

Interface

The interface is the main part or component of the Self-Registration Kiosk which
enables the users to interact with the system. Without interface no one can interact
with the system. The interface is basically known as front-end of the system in
which control of the system are provide to the users i.e. patients, doctors and
hospital staff.

2.1.2 Component 2: System

Backend or Database

This component allows the Cresta Healthworx Centre to store the data and
information about the patient for the long-term and retrieve or update that info
when required. However, this component would be mainly integrated with the
interface of the system.

2.1.3 Component 3: Login and

Payment Module

Component allow the users to get the access and to use the system. Each user
has its own unique account which can help to prevent the unauthorized access to
the system. Also, system allow the users to make the payment for their follow-up
or check-up at the hospital and they can make payment using the system on their
mobile and laptop. Moreover, they can add their credit or debit card in the system
and payment made will be secure with end-to-end encryption

2.1.4 Component 4: Patient

Module

This component or module allow the users to maintain their profile and view their
medical records and history as well as enable them to book the appointment and
follow-up or check-up at the hospital.
.
Component analysis

2.2.1 Component 1: System interface

WBS Inclusions Activities Exclusions Assumption Risks Actions after risk analysis
Number (Deliverables) s
1.3.1 Requirements Users Input Project Users and Poor users’ Prepare the stakeholder list
Document, Charter health-care inputs and users and arrange the meeting
Business staff input are not interest to and interview with them and
Case would be give their input. everything will be noted
taken and down that discussed in the
their meeting.
requirements
are collected
and analysed.
1.3.5 Software Layout Design Project Layout of the Poor design and Design approach and model
Requirement Charter, system is not be accepted. is taken into the
Specification Business designed consideration during design
Case following the phase.
modern
approach and
model of
design.
 1.3.5 Software Front-End Project Design meet Stakeholders are Design approach and
Requirement Design Charter, the needs not happy with principles are adopted to
Specification Business and the design meet the stakeholder need
Case expectations and expectations.
of
stakeholders
1.3.5 Project Plan Prototype Project Prototype is Project prototype Stakeholders should be
Charter prepared is not approved constantly involved and
within the prototype will be reviewed.
deadline.
1.3.5 Project Plan Finalize Cost plan Stakeholders Not getting the Resources and cost rough
Prototype agreed with funding and estimate is prepared and
the prototype. resources benefits are defined to the
required for the top management.
project.

2.2.2 Component 2: System backend or Database

WBS Inclusions Activities Exclusions Assumptions Risks Actions after risk

Number (Deliverables) analysis
1.3.2 Project Configure Business Successful Database cannot Simple and flexible
Management Database case configuration be configured technology of database is
 Plan of the and match with used.
database. the technology
used.
1.3.4 Project Install Database Cost Plan Database Database crash Maximum testing is
Management successfully or hack. performed to avoid any
Plan deployed at kind of failure.
online server
of the hospital.
1.3.5 Project Develop Back- Benefit Back-end is In-efficient cost Cost management and
Management end Analysis completely and schedule schedule management
Plan, Business developed planning plan is prepared
Case within the
schedule and
timeline
specified.
1.3.5 Project Integrated with Business Successful Poor schedule Schedule, WBS and Gantt
Management Front-End case integration Chart or Network diagram
Plan within the is prepared
deadline
1.3.5 Project Review Business Effective and Communication Communication and
Management Component or case efficient conflict and stakeholder management
Plan, Status Module stakeholder stakeholders are plan is prepared
 Report and not satisfied
communicatio
n management

2.2.3 Component 3: Login Module

WBS Inclusions Activities Exclusions Assumption Risks Actions after risk analysis
Number (Deliverables) s
1.3.2. Project Purchase Online Business Server Crashing of Testing is performed and
Management Server case purchase and server server is configure properly
Plan successfully before the use.
configured.
1.3.5 Project Develop login Feasibility Module Module cannot Quality Assurance is
Management module study developed be integrated performed during each
Plan successful with other phase of the project so that
modules. all issues and defects will
be overcome.
1.3.7. Project Creation of Feasibility Users System would be Two-factor authentication is
Management users account study accounted access used to prevent and avoid
Plan created. unauthorizedly. any kind of unauthorized
access
1.3.5. Project Integration of the Feasibility Integration Cannot meet the Schedule and cost
Management project modules study performed budget and management is prepared in
 Plan successfully timeline which consistently tracking
constraints. and monitoring is performed
and if cost and schedule
variance is negative then
corrective actions are made
or both schedule and cost is
revised.
1.3.9. Project Testing Feasibility Testing is Testing results Maximum internal testing is
Management study completed as failed. performed during the
Plan per plan develop to prevent any type
of failure.
1.3.8. Project Training Feasibility All users are High training cost Online training is provide
Management study trained and user-manuals are
Plan successfully. prepared.

2.2.4 Component 4: Patient Module

WBS Inclusions Activities Exclusions Assumptions Risks Actions after risk

Number (Deliverables) analysis
1.3.11 Project Deploy on Business System System crash System is tested before
Management Server case deployed on deploying to the server to
Plan the hospital avoid any kind of issue and
server error
1.5.1. Project Release Business Resources are Increase cost of Resources management
Management Resources case releases resources plan is considered
Plan
1.5.2 Project Presentation Business Project is Time is not Schedule is taken into the
Management case defined and managed consideration
Plan presented to
the staff and
top
management
of hospital
1.5.1 Project Project Business Documentatio Deliverables are Review and revise all the
Management Documentation case n completed not accepted deliverables according to
Plan Handover and handed requirements
over
1.4.1 Project System Business System is Crashing of the 1-year free warranty is
Management Maintenance case made system provide
Plan operational
and live to use
Risk management

2.3.1 Risk matrix

Probability Impact Equivalent

Risk Risk identified
(1-10 scale) (1-10 scale) value
R1 System Crash 7 7 49
R2 Technology used is not 5 10 50
appropriate
R3 Budget overruns 10 10 100
R4 Delay in the development 10 10 100
R5 Turnover of team member 8 10 80
R6 0
R7 0
R8 0
R9 0
R 10 0
R 11 0
2.3.2 Threshold value(s)

Threshold value Actions

High Risk is unacceptable
Medium Risk should be reviewed
Low Risk is acceptable

2.3.3 Risk graph

10

8
Impact
2.3.4 Risk actions

Risk Risk action Component analysis

R1 Maximum testing is performed during the development of Execution and

the system. So, that all of the errors are reduced and Monitor & Control

minimize before the project delivery and it can save the

failure cost as well.

R2 Technology chosen for the project will be according to Initiation

latest trends.
R3 Cost is reviewed and burn-down chart is prepared to track Planning and

the cost and if there is over-run then contingency is used Execution

or budget is revised
R4 Schedule is reviewed throughout the completion of the All components

project and when there is delay then burn-out mode is ON would be taken into

in which team is asked to work for extra hours to meet the the consideration

schedule.
R5 Back-up of every team member is generated if anyone All components

leave then that person is replaced is with other one. would be taken into

the consideration
Statement of work document (SOW)

2.4.1 Background

The project mainly aimed meet the needs of the Cresta Healthworx Centre and to
automate the process for the patient to book an appointment to the hospital using
their mobile phone and laptop whenever they want to and with their suitable timing.
The current or existing process at the hospital is very in-adequate and everything
is manual and the patient has to wait for long-time for their number to come-up for
their check-up. So, with the implementation of the system name “Self-Registration
Kiosk” this process can be automated and patients can book their appointment in
hospital for their follow-up and the can manage the medical history and records in
the single application or system as well as they can made the payment for their
follow-up online.

2.4.2 Component by
component discussion of inclusions

The project is categorized into the five components in simple words we can say the
overall project is divided into five phases (Initiation, Planning, Execution, Monitor &
Control and Closing). All of these phases are involved different activities and some
of the key activities are discussed above in the component analyse and the
complete activities list of the project are given below in the WBS.

2.4.3 Assumptions that

require mentioning

The system can be supported and maintained by highly experienced and

professionals because the system main aim is to meet the requirements of Cresta
Healthworx Centre as they want to facilitate the patient more and make all
operation and process check-up very easy. However, the project can pay for itself
within 5 months which can reduce the operational cost of the project with the
control in the project budget. The project manager should receive the full
resources, commitments, and support from top management. Hospital top
management and manager can help the project manager to lead effort, hospital
different services and process. The system will be implemented by using the
programming language C# and MySQL and system is deployed on the machine
and also it contains the high-level security algorithm for encryption to prevent any
kind of threats and vulnerabilities as well as hacking attacks.

2.4.4 Major risks

The risk associated with the project are identified in the above section of risk
management but the major risks of the project are:
 Turnover of team member during the project.
 Project cannot meet the deadline
 Project cost exceeded to its limit

2.4.5 Exclusions

During the project, following things are excluded:

 Project team is not providing the fee for travelling.
 Installation of software and OS on hospital computer and devices.
 Project team is not provided any meal or lunch.
 The project team is not provide the equipment and tools for the
development and testing.
Work breakdown structure (WBS)
Project scheduling: Network diagram

2.6.1 Activity data

Immediately preceding
Activities Duration
activities
A 25 -
B 5 A
C 20 A
D 30 B, C
E 25 D
F 18 D, E
G 20 D
H 60 D, E, F, G
I 45 H
J 80 H, I
K 30 H, I
L 30 C, D
M 22 C, D
M 35 J
O 20 H
P 45 H, I, J, L, M
Q 120 J, K, N, O, P
2.6.2 Network diagram
Project scheduling: Gantt chart
Cost estimation

The total cost assigned for the development of system is $50,000 the cost includes all associated cost i.e. development cost,
maintenance cost. The analogous estimation method is used for the cost estimation in which the cost or budget is used for the
project which is completed in the future or past. Here below is below is the budget of the project is defined using the key items of
WBS.
Determine budget

2.9.1 Project budget

In our project, the main source of funding is the Finance Department of University. The project can cost us approx. $ 50,000 and
during the first year there will be no profit, the investment will be recovering after 3 years. Cost $ 90,000 will be estimated as a
benefit, ROI is 73% and NPV is $ 72,250.
2.9.2 Project baseline

Earned Value Management can play an important role to control the performance of the project by performing the comparison
between time and cost initially. EVM below provides schedule and cost performance and project assessment. EVM is used to
measure the performance of the project, identify a problem in different scenarios related to the project as well as a forecast or
estimate the cost and time required for completion of the project.
3.

Monitoring and Control

Progress reports

3.1.1 Progress summary

report on activity level for Time Now

As from now the project activities are completed within the time and on the track as
the project manager is consistently monitoring the project timeline and referring to
the Gantt Chart. If delay occurs then project manager can revise the schedule and
asked team member to work for an extra hour to meet the deadline of the project
and at the end they would be rewarded as rewards and incentives. Also, the cost is
tracked and monitored by comparing the actual value and estimate value (date).
As from the Gantt Chart given above till the date everything is completed
according to the time
3.1.2 Cost summary report on
activity level for Time Now

Here below the EVM is given which elaborates the overall progress of the project
in term of cost and timeline.

The graph given above can show three values PV, AC, EV. The point of BAC in a
graph is projected to total budget and this was shown only when project total
budget is spent that we have. EAC point mean project needs the extra budget or
cost and maybe it takes the extra days as planned. The budget for "Self-
Registration Kiosk" will be less than 70K and from the probability of project we
can get the idea, there is a need for the extra cost than estimated to successfully
complete the project
Earned value management

3.2.1 Project EVM analysis on activity level for Time Now

BCWP BCWS ACWP SPI / SV CPI / CV

Activity BAC BTC ETC EAC VAC
(PV) (EV) (AC) % %

A 1000 1000 1000 1000 0 0 0 0 1000 0

B 1500 1500 1500 1500 0 0 0 0 1500 0

C 2500 2500 2500 2500 0 0 0 0 2500 0

D 3000 3000 3000 3000 0 0 0 0 3000 0

E 1000 1000 1000 1500 0 0 0 0 1000 0

F 1000 1000 1000 1000 0 0 0 0 1000 0

G 2000 2000 2000 2000 0 0 0 0 2000 0

H 3000 3000 3000 5000 0 0 0 0 3000 0

I 5000 5000 5000 5000 0 0 0 0 5000 0

J 7000 7000 7000 7500 0 -500 0 0 7000 0

K 5000 5000 1500 5000 -3500 -3500 0 0 5000 0

L 1500 1500 1500 1500 0 0 0 0 1500 0

M 2000 2000 2000 2000 0 0 0 0 2000 0

 BCWP BCWS ACWP SPI / SV CPI / CV
Activity BAC BTC ETC EAC VAC
(PV) (EV) (AC) % %

N 3000 3000 3000 3000 0 0 0 0 3000 0

O 2500 2500 2000 2500 -500 -500 0 500 2500 0

P 5000 5000 500 1500 -4500 -1000 0 4500 1500 0

Q 5000 5000 0 1000 -5000 -1000 0 5000 1000 0

3.2.2 EVM summary on
project level for Time Now

Item Data
Budget at completion (BAC) 50,000
Budgeted cost of work scheduled (BCWS) 45,000
Budgeted cost of work performed (BCWP) 50,000
Actual cost of work performed (ACWP) 52,000
Schedule performance index (SPI) or 0.9
schedule variance (SV %)
Cost performance index (CPI) or cost 0.86
variance (CV %)
Budget to completion (BTC) 52,000
Estimate to completion (ETC) 57,090
Estimate to completion (ETC) 13.3 months
Variance at completion (VAC) 7,090

Project report for Time now

Project Report:
The project performance is not good in term of cost and budget as the SPI and CPI
from the above result is less than 1. So the project manager need to identify that
where the delay is occurring and where cost is spent maximum. During the project,
the risk may occur to interrupt the overall project performance and progress as
every thing has associated risks. So, to overcome the risk, the project risk
management is performed in which each risk associated with the project are
identified and contingencies and mitigation strategies are proposed for each risk to
overcome its impact and effect on the project cost, timeline and quality. However,
the variance is calculated throughout out the project life-cycle and in each phase of
the project and variance is calculate by comparing the actual cost or time with
estimated cost and time. If variance is negative then corrective actions are made
and schedule and cost is revised and minor variance is neglected and acceptable
but if the variance is high then it is the point of indication to make the corrections
with schedule and cost. However, to deal with different issues in the project the
contingency strategies proposed are:
 To overcome the project delay in the project schedule, project tracking is

performed in which the actual time of completion of each task is compared

 with the estimated time of completion and variance is calculated if the

variance is negative then corrective actions should be proposed to

overcome the delay ins schedule.

 To maintain the quality, testing is performed along with the development so

at the end when the software is delivered that will be an error or defect-free

and no extra time is required because of no fixing or error and at the same

time delay is overcome along with maintaining the quality level.

4. References

Heerkens, G. R. (2015). Project management. Place of publication not identified:

Mcgraw-Hill Education.

Kerzner, H. (2017). Project management: A systems approach to planning,

scheduling, and controlling.

PROJECT, M. A., & Project Management Institute (U.S.). (2018). GUIDE TO THE

PROJECT MANAGEMENT BODY OF KNOWLEDGE.