You and your project team are just starting the risk identification activities for a project that is scheduled to last for 18 months. Your project team has already identified a long list of risks that

The correct answer is D. Identify risks is an iterative process.. Risk identification is an iterative process that continues throughout the entire project lifecycle, not just at the start. New risks can emerge at any phase - during execution, as the environment changes, as requirements evolve, or as earlier risks are resolved and new ones surfa

Security and Privacy Governance, Risk Management, and Compliance Program

Question

You and your project team are just starting the risk identification activities for a project that is scheduled to last for 18 months. Your project team has already identified a long list of risks that need to be analyzed. How often should you and the project team do risk identification?

Options

AAt least once per month
BSeveral times until the project moves into execution
CIt depends on how many risks are initially identified.
DIdentify risks is an iterative process.

How the community answered

(52 responses)

A
2% (1)
B
2% (1)
C
6% (3)
D
90% (47)

Explanation

Risk identification is an iterative process that continues throughout the entire project lifecycle, not just at the start. New risks can emerge at any phase - during execution, as the environment changes, as requirements evolve, or as earlier risks are resolved and new ones surface. PMI's PMBOK Guide explicitly states that risk identification is iterative because new risks may become known as the project progresses. The number of risks initially identified (C) is irrelevant to the frequency. Limiting it to once per month (A) or only through execution (B) would leave the project blind to newly emerging risks.

Topics

#Risk Identification#Risk Management Process#Iterative Process#Project Lifecycle

Community Discussion

No community discussion yet for this question.

Full CAP Practice