Free Practice Questions for PMI PMI-RMP Exam

When a team member is struggling to ensure the coverage of all risks in a complex project, the risk manager should develop a risk breakdown structure (RBS). An RBS helps in systematically identifying risks by categorizing them into different levels and areas, making it easier to ensure that all potential risks are considered. This structured approach is particularly useful in complex projects where risks may arise from multiple sources.

PMI advocates the use of an RBS as a best practice for comprehensive risk identification, particularly in large or complex projects where the range of potential risks can be extensive​​.

By hiring a licensed contractor to complete the complex activity, the project manager is transferring the risk associated with that activity to the contractor. This is an example of risk transfer, as the responsibility for managing the risk is shifted from the project manager to the contractor.

According to the PMI Risk Management Professional (PMI-RMP)® Handbook1, one of the domains of the PMI-RMP exam is Risk Response Planning, which involves developing options and actions to enhance opportunities and reduce threats to project objectives1. One of the strategies for negative risks or threats is risk transfer, which involves shifting the impact of a threat to a third party, such as a contractor, a vendor, or an insurer2. In this situation, the project manager is performing risk transfer by hiring a licensed contractor to complete the work that is too complex to complete internally. By doing so, the project manager is transferring the responsibility and liability of the activity to the contractor, who is expected to have the expertise and resources to handle the complexity. The project manager is not performing risk mitigation, which involves reducing the probability and/or impact of a threat2. The project manager is not performing risk acceptance, which involves acknowledging the existence of a threat and making a conscious decision to accept it without taking any action2. The project manager is not performing risk avoidance, which involves changing the project plan to eliminate the threat or protect the project objectives from its impact2. References: 1: PMI Risk Management Professional (PMI-RMP)® Handbook, page 62: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 436.

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.

A stakeholder impact and influence analysis is a technique to identify the level of interest and power of each stakeholder, and to assess how they may affect or be affected by the project outcomes. It can help the risk manager to understand the stakeholder’s perspective and expectations, and to communicate with them effectively. In this case, the risk manager should perform a stakeholder impact and influence analysis to understand why the major investor is about to drop their intention to continue executing the project, and to address their concerns and needs. A risk impact analysis, a risk reserve analysis, and a procurement analysis are not relevant to the stakeholder’s decision, and would not help the risk manager to understand their rationale. References: PMI Risk Management Professional (PMI-RMP)® Exam Content Outline1, PMI Practice Standard for Project Risk Management2, Risk Management Professional (PMI-RMP)® Cert Guide3

Best practice in risk management is to immediately assess the impact of identified risks and develop appropriate response plans. The PMBOK® Guide confirms:

" When a risk is identified, its impact and likelihood should be assessed as soon as possible, and risk response strategies developed and agreed upon. "

— PMBOK® Guide, 6th Edition, Section 11.5

This is especially important for critical dependencies such as vendor deliverables.

In this scenario, the risk manager is considering a response that could lead to a significant residual risk—excessive additional costs due to overtime. Before proceeding, it is crucial to confirm that the project sponsor is comfortable with the risk appetite for this potential outcome. This step is essential to ensure that the decision to allow overtime aligns with the sponsor ' s tolerance for additional costs and the overall project risk management strategy. According to the Risk Management Procedure, understanding and aligning with the sponsor ' s risk appetite is a critical step before implementing risk responses that could impact the project ' s financials​. This approach ensures that all stakeholders are aware of and agree to the potential consequences of the chosen risk response strategy.

To determine the total story points for the entire initiative, we must sum up the estimates provided in the backlog from the email exhibit. The backlog includes the following user stories with their respective story point estimates:

New log-in screen – 6

Save passwords – 4

Defect fixing – triaged top 10 – 8

Accessibility – color blind – 4

Increase security – 21

Shopping cart – 7

Accept credit card payments – 5

Accept bank drafts – 9

New sort order – 3

Add AI chatbot – 5

Total story points calculation:

6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72 story points

Thus, the total number of story points for the initiative is 72, making option A the correct answer.

In risk management, when a residual risk is identified, it is crucial to reassess its impact on the project ' s overall risk profile. Residual risks are those risks that remain even after all mitigation strategies have been applied. According to best practices and the procedures outlined in the documents provided, particularly in the " Risk Management Procedure " and the " Risk Assessment " guidelines, the appropriate steps to manage residual risks involve:

1.     Reassessing the Risk: The first step involves reviewing the impact of the residual risk in the context of existing budget reserves. This ensures that the project has adequate resources to address any potential consequences of the residual risk.

2.     Documenting in the Risk Register: After reviewing the residual risk, it should be documented in the risk register with updated details on its impact and any required actions. This aligns with the standard procedure for managing risks throughout a project ' s lifecycle as described in the " Consolidated Risk Register " section of the Risk Management Procedure​.

3.     Budget Reserves: Specifically, the focus on budget reserves is crucial because it directly relates to the financial management of risks. According to PMI ' s Risk Management guidelines and the practices outlined in the provided documents, ensuring that sufficient contingency funds are available to address residual risks is a key aspect of comprehensive risk management. This approach helps in maintaining the financial health of the project while accounting for unforeseen events​.

In summary, option D is the correct answer because it reflects the necessary actions that should be taken when dealing with residual risks: reassessing their impact on budget reserves and ensuring that the risk register is updated to reflect these considerations. This process is vital for maintaining control over the project ' s risk profile and ensuring that any remaining risks are managed effectively and within the project ' s financial constraints.

According to the PMI Risk Management Professional (PMI-RMP) Reference Materials, the project management plan is the document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates all the subsidiary plans and baselines from the project management processes1. The project management plan should be updated whenever there are changes in the project scope, schedule, cost, quality, resources, communications, risks, procurements, or stakeholder engagement2. In this case, the project team has decided to log the opportunities in the current project’s risk register, which is a component of the project management plan. Opportunities are positive risks that may have a beneficial effect on the project objectives, such as cost savings, schedule acceleration, or quality improvement3. Therefore, the project team should update the project management plan to ensure the results of the opportunities are captured and reflected in the relevant subsidiary plans and baselines. For example, if an opportunity leads to a cost saving, the project team should update the cost management plan and the cost baseline accordingly.

 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.