Risk Identification, Assesment a

Risk Item Number Date Raised Source

1 28/7/10 People, Process.

2 28/7/10 Technology.

3 28/7/10 People, Organisation.

4 28/7/10 People, Organisation.

5 28/7/10 People.

6 28/7/10 People, Environment.

7 28/7/10 Product.
8 28/7/10 Technology, Environment.
9 28/7/10 People, Environment.
10 28/7/10 People
 EXPERIMENT NO. 6
ification, Assesment and Handling Plan

Risk Description Internal/External Impact Description

Long Schedules. Internal Some devices may takes
more time to get completed
then expected.
Inadequate configuration of server.
External Server may not be
upgraded to handle the
Excessive paper work. Internal If the maganement
software on which project is
demands
made. extra
documentation then
Inadequate user documentation.
Internal The various
required things
or the related
team does
to
theproject, changes
same then it may go
implemented,
out of schedule.errors made
Risk of programmer leaving Internal Delay will increase as new
and solved etc may not be
the job. programmer might take
documented properly.
time to understand the
logic.
Creeping user requirements. External Project delay leading to
customer dissatisfation.
Hidden errors. Internal Progress hampered and it
might stop also in severe
Excessive time to get project External Alternatives to be found
case.
live. leading to dealy
Low productivity. Internal Members may not be
familiar with the language,
Low user satisfaction. External User may not be satisfied
no proper motivation etc
the way the product has
may be the reason.
come leading to his
siasatisfaction.
Probability Potential Impact Risk Exposure
0.7 0.5 0.35

0.3 0.9 0.27

0.5 0.5 0.25

0.6 0.4 0.24

0.7 0.1 0.07

0.8 0.5 0.4

0.7 0.6 0.42

0.01 0.01 0
0.4 0.7 0.28
0.7 0.8 0.56
Assigned to Status
Krishna,Jai Open

Priyanka Open

Krishna,Jai Open

Krishna,Jai Open

Priyanka Open

Priyanka Open

Krishna,Jai Open
Priyanka Open
Krishna,Jai Open
Krishna,Jai Open
Approach
Reduce the likelihood or impact of the risk.

Transfer the risk to someone else.

Ignore the risk.

Accept the risk.

Reduce the likelihood of the risk.

Reduce the likelihood of the risk.

Reduce the likelihood and impact of the risk.

Accept the risk.
Reduce the impact of risk.
Reduce the likelihood and impact of the risk.
Actions to be Taken
Time the devices that may take more time accordingly

Server components should be upgraded.

Explain the team or maganement what is not required.

Explain the team what is required to be documented.

Check if the team member has problem and try solving it.
Do not give a particular team member too many details.

Keep the customer involved in the project and keep

him/her updated at every stage.
Do thorough testing at every stage.
Determine the alternatives and implement them.
Determine the reason and find solution for them.
Keep the customer involved in the project and keep
him/her updated at every stage.