Project
The Project represents an actual Software Project to be completed by the Software Engineering Team.  Each Project should contains one or more Risk Information Sheets describing the Risks accompanying the Project.

 

Project ID:

Each Project created in the R.I.S. Builder web application is assigned a unique ID.  The Project ID is used to identify each Project within the system and therefore, cannot be changed.  However, the Project Title and Description may be edited.

 

Project Title:

The Project Title should be the name of a Software Engineering Project for which the team will be creating Risk Information Sheets.  The Project Title is displayed when the item is listed on the Project Listing page and when the Project is referenced.

 

Project Description:

The Project Description should describe the Software Engineering Project in more detail that the Title.  The Project Description is displayed on the Project Listing page below the Project Title.

 

 

	Risk Information Sheet
The Risk Information Sheet documents a Risk that may during the life-time of a specific Software Project.  Risk Information Sheets can be used in to supplement or in the place of a formal Risk Mitigation, Monitoring and Management (RMMM) Plan.

 

Risk ID:

Each Risk Information Sheet created in the R.I.S. Builder is assigned a unique ID.  The ID shown while editing the R.I.S. is in the form: P####-R#### where P#### is the number of the Project and R#### specifies the number of the Risk Information Sheet within that Project.  Similar to the Project ID, the Risk ID cannot be changed.

 

Risk Title:

The Risk Title should be the name of the risk that has been identified in the Software Project, for which the Risk Information Sheet is being created.  The Risk Title is displayed when the item is listed on the Project Listing page and when the Risk Information Sheet is referenced.  Therefore, the Risk Title should be brief, yet descriptive enough that a team member from the Software Project will be able to identify the risk quickly.

 

Date Identified:

The date on which the Risk was first identified and catalogued with the Risk Information Sheet Builder.  When creating a new Risk Information Sheet, the R.I.S. Builder will store the current date.  This value cannot be edited.  The date will be displayed in the following format: MM-DD-YYYY.

 

Probability:

This value indicates the relative Probability that the Project Risk will occur during the time-frame of the Software Project.  The  Probability can be a value from 10% to 100% in increments of 10%.

 

Priority:

The Priority is a rates the urgency of a given Risk compared to the other Risks in the same Project.  The value may be one of the following: Low, Medium, High or Urgent.

 

Impact:

The Impact is a rating that indicates the possible effect on a Software Project in that case that the Risk occurs during completion of the Project.  The value may be one of the following: Negligible Almost no effect on Project. Marginal Project time-line may be impacted, but not changed for the long-term. Critical The Project time-line requires major modifications to recover from the Risk. Catastrophic The Project is delayed indefinitely and cannot be completed.

 

Risk Description:

The Project Description is a summary of the Risk and should describe the Project Risk in more detail that the Title.  The Risk Description is displayed on the Project Listing page below the Risk Title.  Therefore, the Risk should be described in terms that any team member from the Software Project should be able to understand.

 

Refinement/Context:

This section of the Risk Information Sheet should be used to summarize the circumstances, resources and other issues affecting the risk while refining the Risk Description by breaking it down into a list of Sub-Conditions.

 

Sub-Condition:

Each Sub-Condition in the Refinement/Context section should describe an issue that contributes to the cause of the Risk.

 

Mitigation/Monitoring:

The Mitigation/Monitoring section of the Risk Information Sheet presents a list of proposed actions to eliminate, ease or prevent the given Project Risk.  Each action is referred to as a Mitigation and Monitoring Step.

 

Steps:

The individual Mitigation and Monitoring steps that should be taken by the development team to eliminate or prevent the Risk before the Risk occurs.

 

Management:

The Management section gives details on how to deal with a Risk if it becomes a reality.  The Management section includes two items: the Contingency Plan and the Trigger.

 

Contingency Plan:

The Contingency Plan is a detailed plan for the Project Team to act upon in the case that the described Risk occurs during the Software Project.

 

Trigger:

The Contingency Plan Trigger identifies the events that will indicate if the risk has materialized.  The Trigger can serve as a litmus test when deciding whether to enact the Contingency Plan.

 

Current Status:

The Current Status is a list of updates describing the change of the Risk's status in terms of change in probability of key events or a change in the potential impact, etc.  Each status update contains a Date and a Description.

 

Status Date:

The date of the status change.  When modifying the status of a Risk Information Sheet, the R.I.S. Builder will store the current date.  This value cannot be edited.  The date will be displayed in the following format: MM-DD-YYYY.

 

Status Description:

Description of the Current Status or action taken in reference to the identified Risk.

 

Originator:

The name of the Project Team Member who happened to stumble upon the never before seen risk.

 

Assigned:

The name of the unlucky Project Team Member who is responsible for examining the Risk and recommending mitigation.