Project Risk Survey Collection

Project Name: [Project Name]

Date: [Date]

The project scope is:  Well defined and  Somewhat  Poorly defined [Enter Total] : High understood defined, but and/or likely to [Enter Total] : subject to change change Medium [Enter Total] : Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5] Proposed Mitigation: [Enter Mitigation. See Options below]

The requirements of the project are:  Understood and  Understood but  Very unclear or very [Enter Total] : High straightforward very complex or complex [Enter Total]: straightforward Medium but not well- defined [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5] Proposed Mitigation: Enter Mitigation. See Options below] The project hour estimates are:  Agreed to and  High-level  Estimates are not [Enter Total] : High well estimated estimates agreed [Enter Total]: Medium [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5] Proposed Mitigation: Enter Mitigation. See Options below] The project duration is:  Based on scope,  Based on high-  Based on scope that [Enter Total] : High resources hour level estimates, is not well defined [Enter Total]: estimates and requirements are and estimates have Medium considering risk not complete not been identified. [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5]

Proposed Mitigation: Enter Mitigation. See Options below]

Dependencies on Vendor:  There is no  There is a  The project requires [Enter Total] : High dependency on a dependency on a a RFP and/or Vendor [Enter Total]: vendor or RFP vendor, but the and the process has Medium RFP or Vendor is not started. ready. [Enter Total]: Low Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5]

Proposed Mitigation: Enter Mitigation. See Options below]

The scope of the project:  Is something the  Is something that  I something that is [Enter Total] : High project team has the project team new the project [Enter Total]: done before has not done team and there is Medium before but there not a past project to is past projects to review [Enter Total]: Low use as history Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5]

Proposed Mitigation: Enter Mitigation. See Options below] Project Resources:  Have been  Have been  Have not been [Enter Total] : High identified and are identified but are identified [Enter Total]: being utilized to not ready to start Medium gather estimates on project [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5]

Proposed Mitigation: Enter Mitigation. See Options below] Additional Risk questions:  High  Medium  Low [Enter Total] : High [Enter Total]: Medium [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5] Proposed Mitigation: Enter Mitigation. See Options below] Additional Risk questions  High  Medium  Low [Enter Total] : High [Enter Total]: Medium [Enter Total]: Low

Proposed Probability: [Enter %] Proposed Impact: [Enter 1-5] Proposed Mitigation: Enter Mitigation. See Options below]

Additional Risks: [Add your comments here.]

Possible Risks and Mitigations

Scope risk factors:

 The scope of the project is poorly Scope Mitigation Plans: defined  Define various components of scope,  Hard to provide sound estimates such as expected deliverables and known requirements  Easy to have scope creep  Define all out of scope items and  Hard to gather detailed requirements document in Charter

 Start defining high-level business requirements

 Define all assumptions when creating estimates  Ensure there is a process in place for changes in scope

Requirement risk factors: Requirement Mitigation Plans:

 Difficulty understanding the  Hold a requirements gathering session expectations of the project with all stakeholders

 Likelihood that the solution will not  Ensure that stakeholders sign off on meet the business need requirements.

 Difficulty to document the  Ensure there is a process in place for requirements adequately requirement changes

 If customers have not gone through providing business requirements, consider a training session on gathering business requirements for the customers. Estimates risk factors: Estimate Mitigation Plans:  Resources not involved in estimates  Ensure resources are involved in  Resources giving high estimates due giving estimates to unknowns  Utilize estimation techniques to help achieve realistic estimations such as Analogous Estimating, Parametric Estimating, or Three Point Estimates