Risk Register No. Risk Description Category Root Cause Triggers R1 Project Team Selection May not get functional Planning management support for project team member assignments to the project Not enough coordination with functional management R2 Senior management Approval of Plans May not get senior management buy-in on other plans Planning Not enough Poor upward coordination with communication senior management R3 Server owner requirements definition May not be able to accurately define server requirements due to implementation of new technologies Executing-Web Site Not enough Concept technical documentation available from server hardware suppliers 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 R5 "Develop registration for classes and programs" code incomplete "Develop registration for classes and programs" code completion may be delayed Risk Owner (select from Microsoft Project Resource Sheet) Probability (High, Med, Low) Impact Assessment (High, Med, Low) Reason for Impact Assessment Selection Status Medium Open Low Open Inadequate supplier support Medium Open Executing-Web Site Programmer/ Design Analyst unfamiliar with algorithm Increased Programmer/Analyst anxiety Low Open Executing-Web Site Programmer/ Development Analyst unfamiliar with algorithm Delay in completing code walkthroughs High Open R6 Verification Testing Verification Testing delayed delayed due to errors in code regression testing Executing-Web Site Code Development 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 Poor team dynamics management 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 Controlling hold formal customer review due to unavailability or product issues Lack of communication from Customer Customer not communicating and/or not committing to "formal customer review" date High Open Lack of communication from Customer Customer not communicating and/or not committing to "final presentation" date Low Open R10 Customer not Customer may refuse to Closing willing to hear final hear final presentation due presentation to unavailability or product issues Poor lateral communication Potential Responses \f