3271 Registered Users
Skip Navigation LinksHome > ITTO Section > Project Risk Management > Identify Risks

Introduction


- Identify Risks is an iterative process all through the project lifecycle since risks exist all through the different project phases.
- This process deals with coming up with the risk register, which is the list of risks that would affect the project.
- All stakeholders must be involved in the Identify Risks process. Apart from the PM, the stakeholders include the Project Team, end-users, risk management team among others.
- The Project Team is involved in this process to develop a sense of ownership and responsibility for the risk and the responses.
- The different project plans, documents, baselines and the estimates are good areas to review and analyze for risk identification.

Inputs


- Risk Management Plan : Although the PM Plan as a whole is an input for the identify risks process, the RMP is important mainly because it has details about the identify risks process methodology, roles and responsibilities, RBS etc.
- Stakeholder Register : This is one of the first documents created as part of the stakeholder knowledge area. It also has all the stakeholder names as well as their roles and responsibilities.
- Scope Baseline: Out of all the baselines, the scope baseline is important because WBS is a component and allows to look at various work package and the magnitude of risk involved with each package.
- Activity Duration Estimates: Review of the estimates and their range can give an idea of the risks involved.
- Activity Cost Estimates: This is an important input to identify risks process due to the fact that cost by itself is a vital factor and also the ROM estimates involved here.
- Procurement Documents: If the project involves external procurement, then the complexity of the process play an important role in identify risks process.
- Project Documents: Project Charter, Project Schedule etc. have additional inputs to cross-check for identify risks process.
- OPA: Prior project processes followed for identify risks process play a vital role.
- EEF: As with all planning processes, external factors play an important role in this process too.
- Human Resource Management Plan: The HR process and the project hierarchy can contribute to identify risks process as such.
- Other knowledge area plans like Schedule, Cost, Quality are vital due to the planning process involved.

Tools & Techniques


- Documentation Reviews: Review of the different plans and documents to look for risks.
- Expert Judgment: Since risk identification is an important process, needs experience and expertise in identifying different project risks.
- Assumptions Analysis: Assumptions become risks. Assumptions made in different plans and documents can become risks.
- Checklist Analysis: Checklist analysis can identify gaps that can become risks. Lowest level of RBS used as risk checklist.
- Information Gathering Techniques:
> Brainstorming
> Delphi Technique:
-> Questionnaire-based
-> Consensus of the Experts
-> Participants are anonymous
-> Reduces bias or undue influence
-> Might involve multiple rounds
> Interviewing
> Root Cause Analysis
- Diagramming Techniques –
> Cause and Effect Diagrams
> System or Process Flow Charts
> Influence Diagrams
- SWOT Analysis: Organization strengths and weaknesses that can affect the project.

Outputs


- Risk Register – This process makes an initial entry and this list gets revisited in further processes. The risk register has -
> List of identified risks: risks, their root causes are documented
> List of potential responses: Main input for Plan Risk Responses process

Match the Following


1. Delphi Technique - a. Initial Risks and Responses
2. Identify Risks Process - b. Questionnaire-based
3. Cause and Effect Diagram - c. Project Files
4. OPA – d. Published Checklists
5. EEF – e. Ishikawa Diagram

Match the Following (Answers)


1. Delphi Technique - b. Questionnaire-based
2. Identify Risks Process - a. Initial Risks and Responses
3. Cause and Effect Diagram - e. Ishikawa Diagram
4. OPA – c. Project Files
5. EEF – d. Published Checklists