During the Monitor and Control Program Risks process, how should the program manager handle the program risk register when no new threats have been identified since the last review?
Freeze the risk register until the next formal risk identification cycle to avoid unnecessary rework.
Skip further risk register updates and focus on issue management instead, because all risks have already been logged.
Continue to update the risk register to reflect changes in probability, impact, and status of existing risks and their responses.
Archive the current risk register and start a new version only if a major change request is approved.
PMI guidance views the risk register as a living document. Even if no new threats are discovered, the program manager should continue to update it to show changes in probability, impact, or status of existing risks, document outcomes of implemented responses, and retire risks that are no longer relevant. These updates keep risk information current for stakeholders and maintain alignment with strategic objectives.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a risk register and why is it important in program management?
Open an interactive chat with Bash
What are emerging issues in project management, and how do they affect the risk register?
Open an interactive chat with Bash
How can program managers effectively monitor risks if no new threats are identified?
Open an interactive chat with Bash
PgMP
Governance
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Project Management Package Join Premium for Full Access