PMI PMI-RMP - PMI Risk Management Professional (PMI-RMP) Exam

To address the lack of risk management buy-in from the project team, the risk manager should organize risk engagement activities, such as workshops. These activities can help create awareness of the importance of risk management and motivate the team to take their risk management responsibilities seriously.

 Risk engagement is the process of involving stakeholders in risk management activities, such as identifying, analyzing, prioritizing, and responding to risks. Risk engagement activities are designed to motivate and influence the project team and other stakeholders to take their risk management responsibilities seriously and to understand the benefits of risk management for the project’s success. Risk engagement activities can include workshops, games, simul-ations, brainstorming sessions, surveys, interviews, and other interactive methods. Risk engagement activities can help to create a positive risk culture, improve communication and collaboration, increase risk awareness and ownership, and enhance risk management skills and knowledge. References: PMI Risk Management Professional (PMI-RMP) Examination Content Outline and Specifications1, page 9; Mastering PMI-RMP Domains, Tasks, and Enablers for Effective Risk2

 

Variance analysis is a method used to compare planned project performance against actual performance. Since the project sponsor has requested a performance report for the entire 10-year initiative, variance analysis would allow the risk manager to identify discrepancies between what was planned and what has been achieved over the course of the project. This analysis is crucial for understanding performance trends, cost deviations, schedule variations, and overall project health.

PMI ' s guidelines support the use of variance analysis in performance reporting as it provides insights into how well the project is adhering to its planned budget, schedule, and scope​​.

 

Adding the identified risk to the risk register is the best action that the risk manager can take to address this risk. The risk register is a document that records the identified risks, their characteristics, their status, and their responses. By adding the risk to the risk register, the risk manager can ensure that the risk is not overlooked or ignored, and that it will be subjected to further probability and impact analysis to determine its priority and response strategy. Accepting the identified risk because other stakeholders feel that there are higher priority risks to address is not a good practice, as it may lead to overlooking a potentially significant risk that could affect the stakeholder’s team. Mitigating the identified risk in order to reduce the probability of impacting the stakeholder’s team is not advisable, as it may be a premature or unnecessary action without proper analysis of the risk probability and impact. Escalating the identified risk to the project sponsor and allowing them to determine the best course of action is not appropriate, as it may be an overreaction or a sign of lack of competence from the risk manager, who should be able to handle the risk identification and analysis process. References: PMI Risk Management Professional (PMI-RMP)® Exam Content Outline1, PMI Practice Standard for Project Risk Management2, Risk Management Professional (PMI-RMP)® Cert Guide3

 According to the PMBOK Guide, one of the tools and techniques for the identify risks process is data gathering. Data gathering is the process of collecting information from various sources to identify potential risks that may affect the project objectives. One of the data gathering techniques is document analysis, which involves reviewing and analyzing available project documents and other information sources to identify potential risks1.

Two of the artifacts that will help the risk manager conduct the initial risk assessment for a six month initiative are the work breakdown structure (WBS) and the project organizational chart. These are two of the project documents that can be analyzed for potential risks in the project.

The work breakdown structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The WBS represents the work defined in the current approved project scope statement and provides the framework for detailed cost estimating, resource planning, and risk management. By reviewing the WBS, the risk manager can identify potential risks that are associated with each work package, deliverable, or scope element, such as technical complexity, quality requirements, dependencies, assumptions, constraints, and uncertainties1.

The project organizational chart is a graphical representation of the project team members and their reporting relationships. The project organizational chart depicts the roles and responsibilities of the project team, as well as the communication channels and authority levels among the team members and other stakeholders. By reviewing the project organizational chart, the risk manager can identify potential risks that are related to the project team structure, such as resource availability, skill gaps, team dynamics, stakeholder expectations, and conflict resolution1.

Some of the other options are not relevant or appropriate for the question scenario:

The configuration management plan is a component of the project management plan that describes how the project team will manage the configuration of the project’s deliverables and documentation. The configuration management plan defines the processes, tools, and methods for identifying, controlling, tracking, and auditing the changes to the project’s baselines. The configuration management plan is not an artifact that will help the risk manager conduct the initial risk assessment, as it does not provide information on the potential risks that may affect the project objectives or scope1.

Brainstorming is a technique for the identify risks process that involves generating a list of potential risks through a group discussion. Brainstorming is not an artifact, but rather a tool and technique for identifying risks. Brainstorming can help the risk manager conduct the initial risk assessment, but only after reviewing and analyzing the available project documents and information sources1.

Monte Carlo analysis is a technique for the perform quantitative risk analysis process that involves simulating the combined effect of individual project risks and other sources of uncertainty on the project objectives, such as cost or schedule. Monte Carlo analysis is not an artifact, but rather a tool and technique for analyzing risks. Monte Carlo analysis can help the risk manager conduct the initial risk assessment, but only after identifying and prioritizing the individual project risks and their probability and impact1.

PMBOK Guide, 6th edition, pages 397-399, 414-415, 431-432, 441-442, 156-157, 168-169, 89-901; PMI-RMP Exam Content Outline, 2015, page 7.

In agile projects, the risk burndown chart is used to monitor the reduction of project risk over time. If risk exposure is found to be increasing, it is essential to act immediately by selecting and implementing risk mitigation actions that can reduce exposure in upcoming iterations. The PMI “Agile Practice Guide” and the PMBOK® Guide state:

“In agile projects, risks are identified and managed continuously. When risk exposure is high, mitigation actions (often called ‘risk mitigation stories’) should be prioritized in the next iteration or sprint to bring exposure back to acceptable levels.”

— Agile Practice Guide, PMI, Section 5.7 (Responding to Risks in Agile Projects)

“Project teams may develop risk response actions as work items and prioritize these for execution in the backlog, particularly in iterative and incremental environments.”

— PMBOK® Guide, 6th Edition, Section 11.6.2.3

Therefore, prioritizing risk mitigation stories for the next sprint (Option C) is the most effective and officially recommended response.

Meeting with the traffic authority staff responsible for the new regulation allows the project manager and risk manager to understand the potential changes and their impact on the project. This will help them proactively address any potential issues and ensure the project complies with the new regulations.

According to the PMBOK Guide, 6th edition, Chapter 11: Project Risk Management1, the project manager and the risk manager should handle this situation by meeting with the traffic authority staff in charge of the new regulation. This is because:

The new traffic regulation is an external risk that could affect the project objectives, such as scope, schedule, cost, quality, and customer satisfaction. External risks are those that arise from outside the project boundaries and are beyond the control of the project team. Examples of external risks include changes in government policies, regulations, laws, market conditions, environmental factors, etc.

The project manager and the risk manager should proactively engage with the external stakeholders who have the power and influence to create or modify the external risks. By meeting with the traffic authority staff, they can establish a positive relationship, gain insights into the new regulation, and influence its development to align with the project needs. They can also obtain information on the probability and impact of the risk, as well as the potential response strategies.

The other options are not effective in handling this situation because:

Ensuring the project complies with the current traffic regulations and laws does not address the risk of the new regulation that could change the project requirements, scope, or deliverables. It also does not help the project team to prepare for the possible changes and mitigate their negative effects.

Sending a letter to the traffic authority with the general project information does not establish a direct and timely communication channel with the external stakeholder. It also does not provide enough details or feedback to understand the nature and implications of the new regulation.

Performing inquiries on the website of the traffic authority weekly does not allow the project team to influence the development of the new regulation or obtain reliable and updated information. It also does not enable the project team to build trust and rapport with the external stakeholder.

PMBOK Guide, 6th edition, Chapter 11: Project Risk Management1

Risk Management Professional (PMI-RMP)® Exam Cert Guide2

The project risk manager should monitor risk thresholds closely, as they represent the organization ' s risk appetite. In a project with a low risk appetite, it is essential to ensure that risks are managed within the defined thresholds to address stakeholders ' concerns and maintain their confidence in the project ' s success.

According to the PMI Risk Management Professional (PMI-RMP) Reference Materials, risk thresholds are the measure of acceptable variation around an objective that reflects the risk appetite of the organization1. Risk appetite is the degree of uncertainty an entity is willing to take on in anticipation of a reward2. In this case, the project has a significant impact on the organization and the stakeholders have a low risk appetite, meaning they are not willing to accept much deviation from the project objectives. Therefore, the project risk manager should monitor the risk thresholds closely to ensure that the project risks do not exceed the acceptable level of variation and impact the project performance negatively. By monitoring the risk thresholds, the project risk manager can also identify when risk responses are needed and evaluate their effectiveness.

The process of assessing the likelihood and impact of each identified risk is part of the Perform Qualitative Risk Analysis process. This process helps prioritize risks based on their probability and impact, allowing the project team to focus on the most significant risks. By doing so, the project manager and team can allocate resources and effort to address the risks that pose the greatest threat or opportunity to the project.

The process of assessing the likelihood and impact of each risk is part of the Perform Qualitative Risk Analysis process, which is the process of prioritizing individual project risks for further analysis or action by assessing their probability of occurrence and impact as well as other characteristics. This process helps the project manager and the team to focus on the high-priority risks that have the most influence on achieving the project objectives. The other processes are not relevant to the question scenario. Plan Risk Management is the process of defining how to conduct risk management activities for a project. Perform Quantitative Risk Analysis is the process of numerically analyzing the effect of identified risks on overall project objectives. Monitor and Control Risk is the process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project. References: PMI Risk Management Professional (PMI-RMP) Examination Content Outline and Specifications, page 71. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, pages 397-3982.

Whenever new organizational directives or changes in risk thresholds are communicated, the risk manager is required to assess the impact and update the risk management plan to reflect these changes. The PMBOK® Guide states:

“When organizational risk thresholds or tolerances are changed, the risk management plan and associated processes must be updated to ensure alignment with current requirements.”

— PMBOK® Guide, 6th Edition, Section 11.1.3.1 (Risk Management Plan: Updates)

This ensures that risk responses, monitoring, and reporting are in accordance with the most current strategic direction and tolerances.

In this situation, the departure of a key project resource was an anticipated risk, and a transition plan was established as a response. However, implementing this plan has introduced new risks, known as secondary risks, which may impact the completion dates of other project-related tasks. According to PMI ' s risk management framework, it ' s essential to address these secondary risks in alignment with the predefined risk management plan. This involves assessing the new risks ' probabilities and impacts, determining appropriate response strategies, and updating the risk register accordingly. By systematically managing secondary risks as outlined in the risk management plan, the project manager can mitigate potential adverse effects on the project ' s schedule and objectives.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide highlights the necessity of managing secondary risks, stating that " secondary risks should be identified, analyzed, and planned for in the same manner as primary risks, ensuring that all potential threats to project objectives are adequately addressed. "