Go directly to workshop page for Leveraging Drupal

Using PFT to build PFT from scratch: risk management

Every project runs a series of risks (usually a top ten, but there is no limit). Each risk has a title, a descripition, a degree of severity , and a mitigation plan. They can be added, modified and have their state changed at any time.

 

Risk Ranking (sorted by magnitude)

Magnitude   (

Description

Impact

Indicators

Mitigation Strategy

Contingency Plan

 

The following risk list uses these conventions:
Magnitude:                  Risks are ranked from 1 to 10. 1 is the lowest risk and 10 is the highest
risk. Ranking is based upon the criticality of the risk and the probability
of the risk occurring.
Description:                Brief description of the identified risk
Impact:                     C – Critical (Affects all project functionalities and baselines.)
H – High (Affects stakeholders needs and major product functionalities)
M – Medium (These risks are subject to contingency but most of the times,
a mitigation plan will be established in order to avoid the risk.)
L – Low (Generally these are risks for which Risk Acceptance strategies
will be held or quick mitigation plan will be implemented. Usually the
team will decide to live with the risk as a contingency)
Indicator:                  Metrics concerned.
Mitigation/Contingency: Plan to live with or avoid/transfer the risk

 

Select Project as relationship target and add risks, specifying that the project runs the risk.