Example: Risk List
**Course Registration System
Risk List**
Version 2.0
Revision History
| Date | Version | Description | Author |
|---|---|---|---|
| 18/Jan/99 | 1.0 | Risks identified at the beginning of the Inception Phase. | Rick Bell |
| 12/Feb/99 | 2.0 | Updated risk list at beginning of Elaboration Phase. No new risks. Eliminate risk of funding problems. Downgrade criticality of other risks. | Rick Bell |
| | | |
| | | |
Risk List
Project risk is evaluated at least once per iteration and documented in this table. The risks of the greatest magnitude are listed first in the table. (This list was last updated at the beginning of the Elaboration Phase.)
| Risk Ranking/ Magnitude | Risk Description & Impact | Mitigation Strategy and/or Contingency Plan |
|---|---|---|
| 8 | Volume of students logged on during peak hours of the registration period may significantly degrade system performance. | Further develop prototype to obtain more accurate numbers. |
| 7 | R1 and R2 Releases may slip and not be available by September 1999 - the start of the Registration Period. | Monitor progress against the schedule & milestones. Update effort to complete and time to complete on a regular basis. |
| 5 | Interfaces to the old legacy Billing and Course Catalog Systems may introduce performance and response time issues. | Continue to develop prototype. Monitor this issue at weekly progress meetings. |
| 4 | One Developer position remains unfilled. If not filled by the start of the Construction Phase, the schedule could slip by up to 5 weeks. | Contact local recruiting agencies. Action: Rick Bell. |
| 3 | Strike Action of College Facility Union Workers may impact project schedule if IT services are unavailable. | Monitor. |