PMI-RMP · Question #159
Adrian is a project manager for a new project using a technology that has recently been released and there's relatively little information about the technology. Initial testing of the technology…
The correct answer is A. Risk register. All identified project risks - regardless of their source - should be documented in the Risk Register. The risk register is the central repository for recording risk descriptions, probability and impact assessments, risk owners, planned responses, and current status. A Risk…
Question
Adrian is a project manager for a new project using a technology that has recently been released and there's relatively little information about the technology. Initial testing of the technology makes the use of it look promising, but there's still uncertainty as to the longevity and reliability of the technology. Adrian wants to consider the technology factors a risk for her project. Where should she document the risks associated with this technology so she can track the risk status and responses?
Options
- ARisk register
- BRisk low-level watch list
- CProject scope statement
- DProject charter
How the community answered
(24 responses)- A88% (21)
- B8% (2)
- C4% (1)
Explanation
All identified project risks - regardless of their source - should be documented in the Risk Register. The risk register is the central repository for recording risk descriptions, probability and impact assessments, risk owners, planned responses, and current status. A Risk Watch List (B) is used for low-priority risks that are monitored but not actively managed. The Project Scope Statement (C) describes project deliverables and boundaries, not risks. The Project Charter (D) is a high-level authorization document. The risk register is the correct and authoritative place to track risks and their responses throughout the project lifecycle.
Topics
Community Discussion
No community discussion yet for this question.