|
Risk Register |
|
| No. |
Risk |
Description |
Category |
Root Cause |
Triggers |
Potential Responses |
Risk Owner(select from Microsoft Project Resource Sheet) |
Probability(High, Med, Low) |
Impact Assessment(High, Med, Low) |
Reason for Impact Assessment Selection |
Status |
| R1 |
Project Team Selection |
May not get functional management support for project team member assignments to the project |
Planning |
Not enough coordination with functional management |
Poor lateral communication |
|
|
Medium |
|
|
Open |
| R2 |
Senior management Approval of Plans |
May not get senior management buy-in on other plans |
Planning |
Not enough coordination with senior management |
Poor upward communication |
|
|
Low |
|
|
Open |
| R3 |
Server owner requirements definition |
May not be able to accurately define server requirements due to implementation of new technologies |
Executing-Web Site Concept |
Not enough technical documentation available from server hardware suppliers |
Inadequate supplier support |
|
|
Medium |
|
|
Open |
| R4 |
Registration for classes and programs design undefined |
May not be able to accurately design "Registration for classes and programs" modules due to complex algorithm requirements |
Executing-Web Site Design |
Programmer/ Analyst unfamiliar with algorithm |
Increased Programmer/Analyst anxiety |
|
|
Low |
|
|
Open |
| R5 |
"Develop registration for classes and programs" code incomplete |
"Develop registration for classes and programs" code completion may be delayed |
Executing-Web Site Development |
Programmer/ Analyst unfamiliar with algorithm |
Delay in completing code walkthroughs |
|
|
High |
|
|
Open |
| R6 |
Verification Testing delayed |
Verification Testing delayed due to errors in code regression testing |
Executing-Web Site Development |
Code incompatibilities |
Test Plans unapproved |
|
|
High |
|
|
Open |
| R7 |
Uncooperative Users |
Users may not cooperate and be difficult during training |
Executing-Roll Out |
No plan for conflict management |
Poor team dynamics |
|
|
Low |
|
|
Open |
| R8 |
Support process definition |
May be challenges defining the technical support processes |
Executing-Support |
Support team unfamiliar with new software product line |
New intranet software products causing anxiety with field support personnel |
|
|
Medium |
|
|
Open |
| R9 |
Customer not willing to hold formal customer review |
Customer may refuse to hold formal customer review due to unavailability or product issues |
Controlling |
Lack of communication from Customer |
Customer not communicating and/or not committing to "formal customer review" date |
|
|
High |
|
|
Open |
| R10 |
Customer not willing to hear final presentation |
Customer may refuse to hear final presentation due to unavailability or product issues |
Closing |
Lack of communication from Customer |
Customer not communicating and/or not committing to "final presentation" date |
|
|
Low |
|
|
Open |
|
