Identify

1
What is Identification?
 Identification is a process of transforming uncertainties and issues about the
project into distinct (tangible) risks that can be described and measured.
Identifying risks involves two activities:
• Capturing a statement of risk
• Capturing the context of a risk
 Context provides additional information about the circumstances of the risk.
 The objective of risk identification is to locate risks before they become
problems and to incorporate this information into the project management
process.

2
Inputs and Outputs of the Identify
Function

3
Inputs and Outputs of the Identify
Function

4
Inputs and Outputs of the Identify
Function

5
Risk Identifiers
 A unique risk identifier is generally used to help keep track of risks that have
been identified and are going to be managed. This can be a number, project
name and number combination, or some other unique combination of letters
and numbers.

6
Capturing a Statement of Risk
 Capturing a statement of risk involves considering and recording the
conditions that are causing concern for a potential loss to the project,
followed (optionally) by a brief description of the potential consequences of
these conditions.
 The objective of capturing a statement of risk is to arrive at a concise
description of risk, which can be understood and acted upon.
 The components of risk statement are:
• Condition: a single phrase or sentence that briefly describes the key
circumstances, situations, etc., causing concern, doubt, anxiety, or
uncertainty.
• Consequence: a single phrase or sentence that describes the key, possible
negative outcome(s) of the current conditions. 7
Capturing a Statement of Risk

8
Example Statement of Risk
 Given that the graphical user interface (GUI) must be coded using X
Windows and we do not have expertise in X Windows, then there is concern
that (possibly) the GUI code will not be completed on time and will be
inefficient.

9
Example Statement of Risk
 When writing the statement of risk the words "given that" can be omitted,
and the phrase, "then there is concern that (possibly)", can be replaced by a
semicolon.
 Simplified Notation: The graphical user interface (GUI) must be coded
using X Windows and we do not have expertise in X Windows; the GUI code
may not be completed on time and may be inefficient.
 The minimum statement of risk is the condition (Capturing the condition is
the important aspect of risk identification).
 The following statement is not a satisfactory statement of a risk.
• There is risk in the schedule.

10
Methods and Tools for Risk Identification

11
Methods and Tools for Risk Identification

12
Capturing the Context of a Risk
 Capturing the context of a risk involves recording the additional information
regarding the circumstances, events, and interrelationships within the project
that may affect the risk.
 This description has captured more detailed than can be captured in the basic
statement of risk.
 The objective of capturing the context of a risk is to provide enough
additional information about the risk to ensure that the original intent of the
risk can be understood by other personnel, particularly after time has passed.

13
Capturing the Context of a Risk

14
Capturing the Context of a Risk
 Effective context captures the what, when, where, how, and why of the risk
by describing the circumstances described in the risk statement, contributing
factors, related issues, and potential consequences of the risk.
 The structure of the context is informal text, which may consist of brief
comments through one or more sentences of explanation.
 Example Statement of Risk: The graphical user interface (GUI) must be
coded using X Windows and we do not have expertise in X Windows; the
GUI code may not be completed on time and may be inefficient.
 Context: The graphical user interface is an important part of the system and
we do not have anyone trained in the X Window System. We all have been
studying the language but it is complex and only one person in the group has
any graphics experience and that is with Windows on the PC.
15
 Updating the
Context
 The context of a risk is often modified and expanded as a normal part of the
risk management process. This is done to reflect the most current risk
information. Things that are added to the context are:
• Changes in conditions
• New conditions or concerns
• Decisions made

16
Guidelines and Tips for Identify
 Develop a common understanding of the risk by sharing several points of
view.
 Provide an opportunity for individual contributions.
 Ensure that the common view does not eliminate individual views.
 State risks in objective terms which are understood by project personnel.
 State risks in a way such that they can be addressed.

17