PMI Updated PMI-RMP Exam Questions and Answers by aleksandra

The main output of the stakeholder meeting in the initiation phase is to identify threats and opportunities that may impact the project in a positive or negative way. This information will be used to develop the risk management plan.

The meeting that the project stakeholders are invited to in the initiation phase is part of the Identify Risks process. The purpose of this process is to identify the risks that may affect the project objectives in a positive or negative way, and to document their characteristics. The main output of this process is the risk register, which is a document that contains the list of identified risks, their causes, potential responses, and other relevant information. The risk register is an essential input for the subsequent risk management processes, such as Perform Qualitative Risk Analysis, Perform Quantitative Risk Analysis, Plan Risk Responses, and Monitor Risks. Therefore, the correct answer is B. Identifying threats and opportunities. References: PMI, The Standard for Risk Management in Portfolios, Programs, and Projects, 2019, p. 79-80, 86-87.

A risk checklist is a tool for identifying risks based on historical information and knowledge from similar projects. It is a list of potential risk sources or categories that can be used to prompt the project team to consider possible risks that may affect the project. A risk checklist should include information that is relevant and useful for identifying risks, such as lessons learned from similar completed projects and previous project risks that may be relevant to this project. These two pieces of information can help the project manager to learn from past experiences and avoid repeating the same mistakes or overlooking the same threats or opportunities. A risk checklist should not include information that is not directly related to risk identification, such as budget variance data from previously completed projects, project scope and cost management plans from previous projects, or stakeholder analysis metrics from projects with similar risk profiles. These pieces of information may be useful for other aspects of project management, such as planning, monitoring, or controlling, but they are not helpful for identifying risks on a project. References: PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Chapter 11: Project Risk Management, p. 397. 5

Lessons learned and previous project risks are valuable sources of information for creating a risk checklist. They provide insights into potential risks that may impact the current project and help the project manager develop appropriate risk responses. Budget variance data, project scope and cost management plans, and stakeholder analysis metrics, although useful, are not directly related to risk identification. (Reference: Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Section 11.2)

The The project manager should include secondary and residual risks as part of the risk response plan. Secondary risks are those risks that arise as a direct result of implementing a risk response to a specific risk. Residual risks are those risks that are expected to remain after the planned responses of risks have been taken, as well as those that have been deliberately accepted. Both secondary and residual risks should be identified, analyzed, and monitored throughout the project life cycle. The project manager should communicate the risk response plan to the project sponsor and other stakeholders, and explain how the project team has planned to manage the secondary and residual risks12

 1: PMI Risk Management Professional (PMI-RMP)® Handbook, page 10 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, page 11.2.2.1

project manager should include secondary and residual risks in the risk response plan, as they may still impact the project. Proactively addressing these risks will help the project team to be prepared and manage them effectively if they occur.

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Identification is to review the stakeholder register and stakeholder engagement plan to communicate and solicit stakeholder input on risks throughout the project life cycle1. The stakeholder register is a project document that identifies the project stakeholders, their roles, interests, expectations, influence, and communication requirements2. The stakeholder engagement plan is a component of the project management plan that describes the strategies and actions to promote productive involvement of stakeholders in project decision making and execution3. In this scenario, the risk manager should review these documents to address the concerns of some stakeholders who are complaining that their opinions were not considered in the risk identification process. The risk manager should communicate with the stakeholders according to their preferences and needs, and solicit their input on the project risks using various tools and techniques, such as interviews, surveys, brainstorming, etc. The risk manager should also update the stakeholder register and stakeholder engagement plan as needed to reflect any changes in the stakeholder community or their expectations. The risk manager should not refer to the requirements documentation to confirm stakeholder requirements as they relate to risks, because that is not a direct way to address the stakeholders’ concerns, and it may not capture all the potential risks that the stakeholders may identify4. The risk manager should not refer to the project charter to find guidelines and stakeholder communication channels, because the project charter is a high-level document that does not provide detailed information on how to communicate and engage with the stakeholders5. The risk manager should not rewrite the risk register to include the additional possible risks and inform the stakeholders, because that is a premature and presumptuous action that may not reflect the actual views and inputs of the stakeholders, and it may create more confusion and dissatisfaction among them6. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 82: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 5133: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 5184: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 1525: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 776: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 414.