1.

0 Risk Management
A risk is the possibility of an issue that has not occurred yet, and if it occurs it would have a
negative impact on a project. Risks can become issues if they are not addressed properly. The
process of risk management includes identifying, analyzing and addressing risks in order to
mitigate their negative effects on a project.
1.1 Impact Scale

Project
Objective
Cost

Schedule

Scope

Quality

Very Low
1
Insignifican
t cost
impact
Insignifican
t schedule
impact
Barely
noticeable

Low
2
< 10%
cost
impact
< 5%
schedule
impact
Minor
areas
impacted

Moderate
3
10-20%
cost
impact
5-10%
schedule
impact
Major
areas
impacted

Barely
noticeable

Only very
demanding
application
s impacted

Sponsor
must
approve
quality
reduction

High
4
20-40%
cost
impact
10-20%
schedule
impact
Changes
unaccepta
ble to
sponsor
Quality
reduction
unaccepta
ble to
sponsor

Very High
5
> 40%
cost
impact
> 20%
schedule
impact
Product
becomes
effectively
useless
Product
becomes
effectively
useless

Risk severity matrix

Probabilit

5
4
3

Moderate
Major
Minor

y
2
1
1

Impact
Table: Risk severity matrix

1.2 Risk Assessment

Ti
me
5

Co
st
5

Sco
pe
5

Impa
ct
5

Probabi
lity
5

Ind
ex
25

15

Major

Avera
ge
5
4.8333
33
3.6666
67

Attrition

4.5

Absenteeism

20

3.5

Design defect
Test case defect
Defect found in
UAT level
Deployment
approval delay

3
4

2
2

3
3

3
3

2
1

6
3

Server failure

15

Power failure
technology
change
Update issues
with uncertainty
Lack of top
management
commitment to
the project
Failure to gain
user
commitment
Users with
negative
attitudes toward
the project

12

Minor

3.5
2.6666
67
3
3.6666
67
1.6666
67
2.6666
67
3.6666
67
2.6666
67
3.6666
67

Major
Modera
te
Modera
te
Modera
te
Minor
Modera
te

SRS defect

Change Request

16

Major

2.6666
67

Modera
te

2.6666
67

Modera
te

3.6666
67

20

Risk
System error

Status
Major

Minor
Modera
te
Modera
te

Major

1.3 Risk Response Matrix

Risk

Mitigation plan

Responsi
ble

Contingency plan

System error

Test prototype

SSE

Work around help

comes

Attrition

Allocate bench
resources

PM

Lock bench resources

Absenteeism

Allocate acting person

SRS defect

SRS rework

SSE,
SQAE, PM
Snr.BA

Change Request

Evaluate the impact

on current system

Lock and educate

bench resources
Increase the review
Gather and analyze
the requirements
effectively

design defect

Design rework

Test case defect

Test case rework

Defect found in UAT

level

Change management

Deployment approval
delay
Server failure

Power failure

technology change

Increase the effective

communication
Use machine
dependant server
system for the
moment
Use generator,
Contact EB
immediately
(dependable on
situation)
Upgrade with
minimum impact to
system

TL
Tech
Lead
QA lead
PM,
Review
board

Increase the review

Increase the review
Test prototype

PM

Timely review and

communication

Network
Admin

Monitor server failure

frequency and analyze
to prevent

Admin

Allocate UPS for each

nodes

Tech
Lead

Develop the system

considering the future
enhancements
Monitor the
firewall/NW
configuration
frequently

Update issues with

uncertainty

Re-installation

Network
Admin

Lack of top
management
commitment to the
project

Manage with the

highest authorized
person next to the top
management

PM

Increase the
communication via
meetings

Failure to gain user

commitment

Increase effective
communication

BA

Increase the user

friendliness in
functionality

Users with negative

attitudes toward the
project

Conduct training with

effective
communication

BA

Increase the number

of trainings