Free Practice Questions for PMI PMI-RMP Exam

If client ' s experts express discomfort with some activities at a critical stage, the first step for the risk manager is to conduct a risk assessment process for that stage. This assessment will help identify the specific risks associated with the activities in question, evaluate their potential impact, and develop appropriate mitigation strategies. This ensures that the project plan is robust and that all stakeholders are confident in its execution​.

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.

An Ishikawa diagram, also known as a fishbone or cause-and-effect diagram, is a tool used to systematically identify potential factors causing an overall effect. In the context of risk management, it helps in pinpointing specific triggers that could lead to identified risks. By categorizing potential causes, the project team can visualize and analyze the root causes of risks, ensuring that risk triggers are well-defined and understood. This clarity enhances the effectiveness of response actions when risks materialize.

PMI Risk Management Study Guide References:

The PMI-RMP Exam Preparation Study Guide discusses the use of Ishikawa diagrams in risk identification, stating that they " assist teams in uncovering root causes of potential risks by visually mapping out cause-and-effect relationships. "

Regression analysis is a data analysis tool that helps identify variables that impact the schedule and determine how these factors interact. It is used to forecast future performance based on historical data and the relationship between variables. (Reference: PMBOK Guide, 6th Edition, p. 248)

According to the PMI Risk Management Professional (PMI-RMP) Reference Materials, regression analysis is a data analysis tool that examines the relationship between one or more independent variables and a dependent variable1. Regression analysis can be used to forecast future performance based on historical data and trends2. In this case, the risk manager wants to identify which variables will impact the schedule (the dependent variable) and determine how these factors interact (the independent variables). Therefore, the risk manager should use regression analysis to create a mathematical model that can predict the schedule performance based on the values of the variables. Regression analysis can also help the risk manager to assess the significance and strength of the relationship between the variables and the schedule3.

 A SWOT analysis is a risk identification technique that helps to identify high-level and strategic project risks by examining the internal and external factors that may affect the project objectives. A SWOT analysis involves listing the strengths, weaknesses, opportunities, and threats of the project, and then analyzing how they may impact the project positively or negatively. A SWOT analysis can help to uncover potential risks that may not be obvious from other techniques, such as prompt lists, interviews, or brainstorming12

 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

The first thing the risk manager should do is analyze the situation and meet with the risk owner. This will allow the risk manager to understand the challenges faced by the risk owner and work with them to find a solution. Conducting a cost-benefit analysis or changing the risk response strategy may be necessary, but it is important to first understand the situation before taking any action.

According to the PMI-RMP Exam Content Outline, one of the tasks in the domain of Risk Response Planning is to “assist the risk owners in developing and implementing risk response strategies and actions based on the agreed-upon risk response plan”. Therefore, the first thing the risk manager should do is to analyze the situation and meet with the risk owner to understand the root cause of the challenges and the cost overrun, and to discuss possible solutions or alternatives. Highlighting this situation to the project manager, conducting a cost-benefit analysis, or changing the risk response strategy are possible actions that can be taken after the analysis and meeting, but not before. References: PMI-RMP Exam Content Outline, Domain 3: Risk Response Planning, Task 31

In risk management, it is standard practice to document risks to the extent that they are identifiable and reasonably foreseeable. If an undocumented risk is realized, the risk manager should address the concern by explaining that risks are documented to the practicable extent possible. This means that while every effort is made to identify and document risks, some risks may not be captured due to their low probability, lack of historical precedence, or other factors.

PMI’s guidelines on risk management recognize that not all risks can be foreseen and documented, and risk management processes should focus on those risks that are most likely to impact the project​​.

A low CPI value (0.53) indicates that the project is over budget. This may be due to an inaccurate cost baseline, which means the initial budget estimation was not correct. This would not necessarily mean that cost control processes are ineffective, actual reported costs are inaccurate, or cost-related risks are effectively managed.

The CPI value is calculated by dividing the earned value (EV) by the actual cost (AC). A CPI value of less than 1 indicates that the project is over budget, meaning that the actual cost is higher than the planned cost. A low CPI value can have several possible causes, such as poor estimation, scope creep, change requests, or inaccurate reporting. However, in this case, the SPI value is greater than 1, which indicates that the project is ahead of schedule, meaning that the earned value is higher than the planned value. This suggests that the cost baseline, which is derived from the planned value, is inaccurate and does not reflect the true cost of the work. Therefore, the risk manager should interpret such a low CPI value as a sign of an inaccurate cost baseline, and not as a result of ineffective cost control processes, inaccurate actual costs, or effective cost related risk management. References: PMI-RMP® Certification Handbook1, page 9; PMBOK® Guide, page 267.

According to the PMI Risk Management Professional (PMI-RMP)® Examination Content Outline1, one of the tasks in the domain of Risk Response is to call for a project team meeting to review risk strategies and make required adjustments, as needed, based on risk monitoring and reporting1. In this scenario, the risk manager should do this to address the situation of the availability of experts, which is a key risk for the project. The project team meeting will help the risk manager and the project team to evaluate the effectiveness of the current risk response plan, identify any new risks or changes in existing risks, and develop alternative risk strategies and actions to deal with the staffing issue. The project team meeting will also facilitate the communication and collaboration among the project team members and other stakeholders, and ensure that the project objectives and expectations are aligned. The risk manager should not implement a disciplined tracking method and report to stakeholders accordingly, because that is not a proactive risk response strategy, but rather a passive risk monitoring and reporting technique2. The risk manager should not escalate the staffing topic to the sponsor and request more budget for contingencies, because that is not a feasible or appropriate risk response strategy, as it does not address the root cause of the risk or provide a solution to the problem3. The risk manager should not revisit the project charter for scope adjustments and sign them off with the customer, because that is not a risk response strategy, but rather a scope management process that may have negative impacts on the project quality, cost, and schedule, and may violate the contractual agreement with the customer4. References: 1: PMI Risk Management Professional (PMI-RMP)® Examination Content Outline, page 102: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4563: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 4364: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, page 133.

The risk manager should have their team review the scope of work and requirements to ensure they understand the project ' s objectives and deliverables. Additionally, reviewing the risk management plan will help the team understand the risk management process, roles, and responsibilities, and prepare for the risk identification workshop.

According to the PMBOK® Guide – Sixth Edition1, the scope of work and requirements are key inputs for the risk identification process, as they define the project boundaries, deliverables, assumptions, and constraints. The risk management plan is also an essential input, as it provides the guidelines and framework for how risk management will be performed throughout the project. The other options are not relevant for risk identification, as they are either related to other processes (such as Monte Carlo analysis for quantitative risk analysis) or not directly related to the project risks (such as the list of pre-approved contractors or the organization chart for city permit department). References: PMBOK® Guide – Sixth Edition, pages 397-398.