A full risk information sheet

A full risk information sheet

 

 

 

 

Scenario: The Stevens Company is converting the SQL Server database to the Oracle database.

Using the sample below, create a 1- to 2-page Risk Information Sheet in Microsoft® Excel® for at least five risks that might be encountered during the conversion.

 

Risk Information Sheet
Risk id: PO2-4-32
Date: March 4, 2014
Probability: 80%
Impact: High
Description:
Over 70% of the software components scheduled for reuse will be integrated into the application. The remaining functionality must be custom developed.
Refinement/context:
Certain reusable components were developed by a third party with no knowledge of internal design standards.
Certain reusable components are implemented in a language unsupported on the target environment.
Mitigation/monitoring:
Contact the third party to determine conformance to design standards.
Check to see if language support can be acquired.
Management/contingency plan/trigger:
Develop a revised schedule assuming that 18 additional components must be built.
Trigger: Steps unproductive by March 30, 2014
Current status:
In process
Originator: Jane Manager