PM 7: Risk Management



		PM 7: Risk Management

PM7 - Risikomanagement

Contents
Product Flow
Handling
Explanation
Roles

Methods
Tools Requirements
External Norms

Contents		Product Flow Handling Explanation Roles		Methods Tools Requirements External Norms

Product Flow

From		Product		to		Methods	Tool Req.	Ext. Norms
Activity	State	Chapter	Title	Activity	State	Methods	Tool Req.	Ext. Norms
PM1 or PM4	being proc.	All	Project Plan	PM1 or PM4	-			/ISO IEC 12207/ Supply Proc.: Exec. and Control, Mngmt. Proc.: Planning
CM4	being proc.	All	Project History	-	-
PM8	-	All	Report Documents: Protocol , Progress Report , Final Project Report , Case Report , Memo , Internal Message , Invitation	PM8 , External	-	FMEA ⁽¹⁾ NPT ⁽²⁾	SPM04

+ "Chapter" are extra columns from the original printed version of GD 250

Handling

The goal of this activity is to detect project risks as early as possible, to initiate preventive measures and to supervise the efficiency of the initiated measures.

Risk management is preventive and must be realized periodically, if possible, at short intervals; it must be documented and realized in the following way:

Measures initiated to eliminate risks detected earlier have to be evaluated regularly with regard to their success and should, if necessary, be corrected.

Possible new risks have to be identified, the probability of their taking place must be estimated and the estimated damages quantitatively determined, as far as this is possible.

If necessary, a priority allocation of the preventive measures with regard to the detected risks must be undertaken.

Definition and initiation of measures minimizing or preventing detected risks have to be realized.

Suggested measures must be reported to activity PM8 - Project Control via Report Documents (Protocol, Progress Report, Final Project Report, Case Report, Memo, Internal Message,Invitation) which in turn might initiate the update of the Project Plan (in activity PM4 - Detailed Planning).

Explanation

Risks always have a negative impact on the planned cost, deadlines and product quality; they may have various reasons. Here some examples:

Risks "based on planning" that are caused by project planning and control, e. g. by unrealistic plans, organizational and personnel bottlenecks, insufficient information flow, changing user requirements, too great a complexity;

"technical" risks; they may e. g. occur within the scope of the integration of various technical products;

"quality-related" risks based on the development process; e. g. by violations against the regulated development process during the development, during quality assurance or configuration management;

"contractual" risks caused by problems on the contractor's side;

"financial" risks based on uncertain financing;

"project-specific" risks based on peculiarities of the project.

When selecting measures to handle risks, the measures should be coordinated in order to prevent new risks being created.

Roles

Role	Participation
Project Leader	responsible
Project Administrator	cooperating

Methods

Product	Methods Allocation	Use
Report Documents: Protocol , Progress Report , Final Project Report , Case Report , Memo , Internal Message , Invitation	FMEA - Failure Mode Effect Analysis ⁽¹⁾	Generate
	NPT - Network Planning Technique ⁽²⁾	Generate

Tools Requirements

Product	Functional Tools Requirements
Report Documents	SPM04 - Supporting Planning of the Project Realization

External Norms

Norm	Process	Chapter	Obs.
/ISO IEC 12207/	Supply Process	Execution and Control	(s. Part 3 - ISO 3.2.1)
/ISO IEC 12207/	Management Process	Planning	(s. Part 3 - ISO 3.2.3)

Notes:

(1) Method FMEA is to be applied if
- high restrictive planned values (deadlines, costs) or
- high requirements
have to be fulfilled in the project.

(2) Method NPT is to be applied if complex arrangement relations and logical interdependences exist in the detailed planning.

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster