Risk checklist – YES Answers indicate increased risk in an area
Risk factor / YES / NO- Project is not thoroughly defined or has a large number of open questions.
- Project will result in significant work flow or business process flow change.
- Project is introducing a new process or system.
- Project is underway, but project plan is not developed, or was developed without much input from the project team or impacted departments.
- Project time line is not realistic.
- Project has a hard implementation date, or is based on the academic or other calendar.
- Project will take more than 1 year to complete.
- Project’s deliverables will be developed by an external consultant or vendor who has limited, poor or no previous track record working with the University.
- Project will require participation by 4 or more departments.
- Project scope is complex and complicated.
- Project will introduce a new technology for which we do not have staff expertise.
- Project dependencies are unknown or undefined.
- The project team has little experience with projects of similar size & complexity.
- User training needs may be significant based on expected change and complexity.
- Requirements are not stable, and may change significantly during the project.
- Interfaces are undefined, unclear and/or subject to change.
- Project will require a significant data conversion or migration.
- Functional team may not have sufficient time or resources to commit to the project.
- Project requires a major change to customer service or support.
- On-going maintenance is not known or not clearly defined.
- A Project Manager has not been assigned, or does not have sufficient time and expertise to manage a project of this size.
- The project requires or may require SAGIT funding.
- This project is dependent upon university or department policy that has not yet been defined (i.e., cloud solution, but no one has defined acceptable data for the cloud).
- The project will require contract review and approval by OGC, Purchasing or OIT Operations & Planning.
- The project will require an extensive discovery phase (i.e., never done this in the past).
- The project relies heavily on people whose primary responsibilities are operational, limiting the time they can devote to any assigned projects.
- The project involves significant customization of a purchased package or tool.
- The project involves significant internal custom development instead of purchasing.
- The project is a change from a tool or processes that is widely used and liked.
- The project appears to be nice to have, rather than in high need or demand.
- The project goal/purpose is not easily described in “plain English”.
- The project involves sensitive University data (e.g. private info about people, research, etc.) that needs to be protected.
- The project requires extensive end user involvement in requirements definition.
- The full cost of the solution or service over its lifecycle has not been calculated.
- Project roles and responsibilities are not clearly defined.
- Executive support is unclear, lukewarm, or has not been established.
- There is no clear plan for managing stakeholder expectations.
- There is a poor match between stakeholder expectations and project realities.