Professional Documents
Culture Documents
Risk Management Plan Document
Risk Management Plan Document
System Name
CS690
Author(s)
Roja Boina
Date
8/30/2016
Table of Contents
1
INTRODUCTION ..3
BACKGROUND 3
RISKS .....3
RISK ASSESSMENT....4
REVISION HISTORY .. 5
1 INTRODUCTION
The purpose of this document is to describe potential risks associated with a
project, the likelihood of the risks, the impact of the risks and a contingency plan for
them.
This plan will identify, assess and prioritize risks.
Select appropriate controls or countermeasures to measure each risk.
Risk mitigation needs to be approved by the appropriate level of management. For
instance, a risk concerning the image of the organization should have top
management decision behind it whereas IT management would have the authority to
decide on computer virus risks.
The risk management plan should propose applicable and effective security controls
for managing the risks. For example, an observed high risk of computer viruses
could be mitigated by acquiring and implementing antivirus software. A good risk
management plan should contain a schedule for control implementation and
responsible persons for those actions.
2 BACKGROUND
This project team has been tasked to design a web-based online system that allows
users to easily access books and reduce manual effort of borrowing and checking
for books.
The project team will acquire the hardware and software applications necessary to
design a web based online reservation system for our customer. The reservation
system will allow our customer to borrow, search books, reserve books, place order
for books check availability online instead of manually performing all these tasks.
RISK
IDENTIFICATION
PREVENTION &
CONTINGENCY
RISK ASSESSMENT
(PROPABILITY and
PRIORITY)
Loss of data
Medium
Design and
implementation
Keep it simple to
implement
Low
Schedule slip
May required
more time to
complete
assigned tasks
than scheduled
Medium
Loss of data
Data may be lost after some time which is a great loss, since loss of
data makes everything inaccessible.
Schedule Slip:
May required more time to complete assigned tasks than scheduled
Loss of data
Get data backed up for every two to three weeks.
Schedule Slip
Weekly meeting will be held to discuss problems, and to provide status
Encourage overtime, borrow staff from other project groups for
additional manning,
Potential risks
Probability:
Priority:
Impact:
6 REVISION HISTORY
Date
9/2/2016
Name
1
Changes
edited the tables present.