Page 198 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Software Project Management

Notes

Notes Note that if probability is high, and impact is low, it is a Medium risk. On the other
hand, if impact is high, and probability low, it is High priority. A remote chance of a
catastrophe warrants more attention than a high chance of a hiccup.

10.5.3 Risk Monitoring

The ongoing risk management task of monitoring the success and status of the other risk
management tasks.

Classification

Risk monitoring is part of the following inheritance hierarchy:
 Type: Abstract

 Superclass: Engineering Task
 Subclasses: None

Responsibilities

The typical responsibilities of Risk monitoring are to Determine if:
 any aspect of the risk analysis has changed and therefore should be repeated.

 any undesirable event defining a risk has actually occurred.
 the other risk tasks are being performed effectively and efficiently.
Preconditions

Risk monitoring can typically begin when the following preconditions hold:
 The endeavor is started.
 The associated teams are initially staffed.
 At least one of these teams is adequately trained in risk monitoring including associated
techniques and work products.
 The risk management plan exists and has passed evaluation.
 At least some risks have been identified, analyzed, and documented.

Completion Criteria

Risk monitoring is typically complete when the following post conditions hold:

 The risk monitoring reports have all been:
 Produced
 Evaluated for quality

 Updated based on the quality control evaluation

192 LOVELY PROFESSIONAL UNIVERSITY