Risk type

Possible risks

Technology

Internet disconnection.

People

Illness of team work member.

members of team don’t know how to use Java Language.

Lack of time for project.

Members' lack of previous experience.

Conflicting opinions among members.

Organizational

Change the head of department.

Tools

Choosing inefficient CASE tools.

Requirements

Change the requirement after design.

Estimation

unexpected change of final exams' date

Risk

Probability

Effects

Internet is disconnection.

Moderate

Serious

Illness of team work member.

All members of team don’t know how to use Java Language.

Lack of time for project

Members' lack of previous experience

Conflicting opinions among members.

Low

High

Moderate

Moderate

Low  

Catastrophic

Tolerable

Serious

Tolerable

Tolerable

Changing the head of department

Low

Tolerable

Choosing inefficient CASE tools.

Low

Serious

Change in requirements after design.

Low

Catastrophic

unexpected change of

Final exams' date

Low

Catastrophic

Risk Planning and Monitoring

each member knows the mobile number of every other member

Internet disconnection.

Minimization strategy

Members Understand Each other's Job.

Illness of team work member

Minimization strategy

Settle for the majority of opinions.

Conflicting opinions among members.

Minimization strategy

Provide Java courses

members of team don’t know how to use Java Language.

Avoidance Strategy

re-organize time

lack if time for project

Avoidance Strategy

Provide training courses

Members' lack of previous experience

Avoidance Strategy

Choose tools Carefully

Choosing inefficient  CASE tools

Avoidance Strategy

when we finish any

task begin the next one immediately & double the efforts of each member

unexpected change of final exams' date

Avoidance Strategy

Meet new head &         discuss the project again

Changing the head of department.

Contingency plan

increase time to design study requirements carefully

Change in requirements after design

Contingency plan