A project manager is assigned to a new project and is told they need to develop the project's risk register. When should the project manager identify the project risks?

Question

Options

• AIdentify risks only at the project's midpoint for the stakeholders to review them
• BEnsure project team members proactively identify risks throughout the project to plan for possible
• CIdentify risks at the beginning of the project because the risk posture will not change
• DDelegate risk identification to each team member and have them record the risks on separate risk

• A
  4% (2)
• B
  91% (42)
• C
  2% (1)
• D
  2% (1)

Explanation

Risk identification is a continuous, iterative process that occurs throughout the entire project lifecycle, not just at a single point in time (B). New risks emerge as the project evolves, assumptions are validated or invalidated, and the environment changes. Option A (identifying risks only at the midpoint) misses both early project risks and late-emerging ones, and limits stakeholder review to a single snapshot. Option C (identifying risks only at the beginning) is incorrect because the risk posture absolutely changes as the project progresses - risks emerge, materialize, or become obsolete over time. Option D (delegating to individuals on separate registers) fragments the risk information, making it impossible to manage holistically; all risks should feed into a centralized risk register.

No community discussion yet for this question.