PMP - PMI Study Hall - Process Domain

During project execution, key stakeholders request a change to ensure that the final product will satisfy their requirements. Why should the project manager submit a change request?

• To record the requirements needed for the stakeholders' sign-off in order to update the issues log.

• To ensure that the request is formally documented and incorporated according to the integrated change control process.

• To provide justification for any impact the change might have on the project's budget or schedule.

• To ensure stakeholder responsibility regarding potential impact of the change on project budget and schedule.

Answer explanation

Solution: B. To ensure that the request is formally documented and incorporated according to the integrated change control process.

A change request formally documents a proposed modification to the project plan, and is the first step of implementing a change.

The project manager's responsibilities include verifying that changes are registered, assessed, approved, tracked, and communicated to stakeholders.

The other choices do not describe the purposes of a change request.

This question and rationale were developed in reference to:

PMBOK Guide Sixth Edition (2018) ///4.2.3.1 PROJECT MANAGEMENT PLAN [Item]

| PMBOK Guide Sixth Edition (2018) PMI/PMI/4/119 [Item]

| Project management : A Systems Approach to Planning, Scheduling, and Controlling (2009) Harold Kerzner/John Wiley/11/15551 (kindle) [Item]

An organization is updating its production capacity by modernizing its computer systems and machinery. The existing systems and machinery will need to keep running while the upgrades are being made. To minimize potential risks, agile methodologies will be used for the systems upgrades while the machinery acquisition, installation, and integration will use waterfall. The co-located project team agrees that communication is critical for the project to succeed.

How should the project manager proceed to ensure the project will be completed on schedule?

• 1. Schedule weekly co-located sessions with the project team and key stakeholders.

• Email weekly status updates to the project team.

• Meet individually with the stakeholders once a week to provide status updates.

• 1. Conduct daily teleconference sessions with the sponsor.

Answer explanation

Solution: A. Schedule weekly co-located sessions with the project team and key stakeholders.

In this situation, where communication is critical and the project involves both agile and waterfall methodologies, scheduling weekly co-located sessions with the project team and key stakeholders is the most effective approach. This allows for face-to-face interaction, promotes collaboration, and enables timely discussions and decision-making. 

The other answer choices are incorrect. Emailing weekly status updates to the project team may not be sufficient for effective communication and collaboration, especially when dealing with a project that involves different methodologies and complex integration requirements. Meeting individually with stakeholders once a week may not facilitate cross-team communication and may lead to siloed information. It may also consume significant time and hinder overall coordination efforts. Conducting daily teleconference sessions with the sponsor can be excessive and impractical, as daily meetings may not be necessary for the entire project team. Weekly sessions are usually sufficient for stakeholders to stay informed and engaged.

This question and rationale were developed in reference to:

O'Reilly Platform (No Date) /// [Item Mastering Project Time Management, Cost Control, and Quality Management: Proven Methods for Controlling the Three Elements that Define Project Deliverables

By Randal Wilson]

| PMBOK Guide Sixth Edition (2018) PMI/PMI/10/365 [Item]

A project manager is developing the schedule for a new software development project. The project network diagram shows two separate paths:

Path A: Tasks 1-2-3-4 (all with a duration of 5 days each)
Path B: Tasks 5-6-7 (durations of 3, 7, and 2 days respectively)
There are no external dependencies between these paths.

What is the critical path for this project?

• 1. 1-2-3-4

• 1. 5-6-7

• 1. 1-2-3-4-5-6-7

• 1. 1-2-6-7

Answer explanation

Solution: A. 1-2-3-4

The critical path refers to the longest sequence of dependent tasks that must be completed on time for the entire project to finish on schedule. Since there are no external dependencies between Path A and Path B, analyze their individual durations. Path A: Tasks 1-2-3-4 (all with a duration of 5 days each) has a total duration of 20 days (5 days/task * 4 tasks = 20). Path B: Tasks 5-6-7 (durations of 3, 7, and 2 days respectively) has a total duration of 12 days (3 days + 7 days + 2 days = 12). Because Path A has a longer total duration (20 days) compared to Path B (12 days), it represents the critical path for this project.

The other answer choices are incorrect. The combination of both paths is not necessary since the paths are independent, thus there's no dependency between tasks 1-2-3-4 and 5-6-7, nor tasks 1-2 and 6-7.

This question and rationale were developed in reference to:

e-Reads (No Date) ///A Practical Guide to Earned Value Project Management, 2nd. CH17. Critical Chain Project Management [Item]

| PMBOK^® Guide--Fifth Edition (5th) PMI/PMI//pmbok 6.3.3.1 Project Schedule Network Diagrams ( p159-160) [Item]

A project manager is assigned to a project that has completed the planning phase. The project sponsor is confident that the project management plan has allowed for sufficient budget and scheduled time. The project manager believes that unforeseen events could affect the ability to complete the project successfully.

What should the project manager do?

• 1. Identify and evaluate potential risks and develop a risk action plan.

• Meet with the project sponsor to request additional funding to mitigate potential risks.

• 1. Discuss the risk potential with the functional manager and identify resources that could ensure project success.

• 1. Document potential constraints and limitations in the risk management plan.

Answer explanation

Solution: A. Identify and evaluate potential risks and develop a risk action plan.

The correct response is to identify and evaluate risks, and develop an action plan. The project manager needs to be proactive and anticipate uncertain events and create plans to avoid, mitigate, transfer, or accept them.

Requesting additional funding is premature until the risks are understood, as are other resource discussions with the functional manager.

The risk management plan describes the process by which the project approaches risk, and nothing in the question indicates that it is inadequate; documenting constraints and limitations also is premature.

This question and rationale were developed in reference to:

Fundamentals of Technology Project Management, 2nd Ed (2015) Colleen Garton, Erika McCulloch/Mc Press/10/369 [Item]

| PMBOK Guide Sixth Edition (2018) PMI/PMI/11/321 [Item]

A project manager for a cross-functional team realizes that there is a lack of commitment from stakeholders to the project following a review meeting. This could lead to project failure.

Which three of the following actions should be avoided to mitigate this risk? (Choose 3).

• 1. Creating a weak communication plan

• 1. Allowing stakeholders to use information radiators

• 1. Not prioritizing stakeholders’ communication needs

• 1. Using fishbowl windows and remote pairing

• 1. Not updating the communication plan

Answer explanation

Solution: A, C, and E. Creating a weak communication plan, Not prioritizing stakeholders’ communication needs, and Not updating the communication plan

The three actions that should be avoided by the project manager to mitigate the risk are those that are most likely to lead to a lack of commitment from stakeholders. A weak communication plan, not prioritizing stakeholders' communication needs, and not updating the communication plan as the project progresses are all likely to lead to misunderstandings and a lack of information for stakeholders. This can lead to stakeholders feeling like they are not being kept in the loop, which can damage relationships and lead to a lack of commitment to the project.

The other two options, stakeholders using information radiators and using fishbowl windows and remote pairing, are not as likely to lead to a lack of commitment from stakeholders. Information radiators are visual displays of project information that can be helpful in keeping stakeholders informed. Fishbowl windows and remote pairing are techniques that can be used to improve communication and collaboration between stakeholders, which can help to build relationships and increase buy-in.

This question and rationale were developed in reference to:

Agile Practice Guide (2017) PMI/PMI//46 [Item]

A new project is initiated to develop several new financial products and services for a company with offices in several countries. The project manager has researched the regulations for each of the countries. Based on the research, the project manager is concerned that some new products and services do not offer enough protection for the consumer.

What should the project manager do first?

• Identify all of the project risks.

• 1. Quantify the project risks in the risk register.

• 1. Develop a risk response strategy.

• 1. Perform scheduled risk audits.

Answer explanation

Solution: A. Identify the high-level project risks.

The correct answer is to identify all of the project risks.
The first step is to identify the risks, which is the process of determining and documenting the risks that might affect the intended outcomes. Regulations are requirements imposed by a governmental body. These requirements can establish product, process, or service characteristics, including applicable administrative provisions that have government-mandated compliance. The project manager has to account for the regulations of each country and identify the risks associated with those regulations.
Once the risks are identified, they can be quantified and a response strategy can be developed and a schedule for a risk audit can be developed. A risk audit would not be helpful if all of the risks have not been identified. Periodic audits should be performed to determine strengths and weaknesses in handling risks within the project.

This question and rationale were developed in reference to:

This question and rationale were developed in reference to:
Fundamentals of Technology Project Management, 2nd Ed (2015) Colleen Garton, Erika McCulloch/Mc Press//80 [Item]
| PMBoK, Sixth edition (2021) PMI/PMI/3/ [Item Project Management Plan Components]
PMBOK Guide Seventh Edition (2022) /// [Item Regulations]

A new project manager joins a project overseen by a senior project manager. The sponsor asks the new project manager to develop the quality management plan.

Why should the project manager initially consult with the senior project manager?

• To learn the established quality processes and plans and how appropriate standards were selected.

• To determine what product requirements have already been collected and to gather more as needed.

• To develop cost-benefit analyses and benchmarking samples to be used for risk management.

• To draft a change request for revision to the quality metrics and quality checklists.

Answer explanation

Solution: A. To learn the established quality processes and plans and how appropriate standards were selected.

The new project manager should consult with the senior project manager to find out what practices and processes are already in place.

Product requirements are not captured in the quality management plan.

Developing cost-benefit analysis and benchmarking samples are not something the new project manager should start doing when the new project manager joins the project.

The new project manager needs to understand what quality metrics and quality checklists are in place before making any changes to them.

This question and rationale were developed in reference to:

Information Technology Project Management, 7th Ed. (2015) Kathy Schwalbe//8/315-317 [Item]

| PMBOK Guide Sixth Edition (2018) PMI/PMI/8/286 [Item]

| PMBoK, Sixth edition (2021) PMI/PMI/8/ [Item Plan Quality Management]

While reviewing the approved project schedule, the project manager realizes that the milestones are unrealistic due to longer-than-expected procurement lead times for certain key project components. The project manager needs to update the schedule baseline to reflect the long lead times.

What should the project manager do first?

• 1. Modify the work breakdown structure (WBS).

• 1. Update the assumption log.

• 1. Modify the procurement management plan.

• 1. Submit a change request.

Answer explanation

Solution: D. Submit a change request.

Change request is the correct answer as every baseline change should go through an integrated change control process.

Procurement lead times are the issue here. Therefore, there is no need to modify the WBS nor to update the assumption log. It is the lead times that were defined but not accounted in schedule baseline. There is no need to change the procurement management plan.

This question and rationale were developed in reference to:

Fundamentals of Technology PM, 2nd Ed (2nd) Colleen Garton, Erika McCulloch/Mc Press/4/134 [Item]

| PMBOK Guide Sixth Edition (2018) PMI/PMI/4/81 [Item]

During a status review meeting, it was determined that the product will not meet project scope requirements in a particular scenario. What should the project manager do?

• 1. Perform risk analysis and update project scope.

• 1. Initiate integrated change control process.

• Review the baselines to determine the critical path.

• 1. Inform customer and negotiate an extended deadline.

Answer explanation

Solution: B. Initiate integrated change control process.

The product not meeting project scope is a "Risk" that needs to be managed. This is managed through Integrated Change Control Process. Project scope may change to include this particular scenario after the CCP is initiated.

There is no baseline review nor renegotiation with the customer until after the CCP is initiated.

This question and rationale were developed in reference to:

e-Reads (No Date) ///Fundamentals of Effective Program Management: A Process Approach Based on the Global Standard by Paul Sanghera, Chapter 4 - Program Scope Management [Item]

| PMBOK Guide Sixth Edition, 6th edition (2017) PMI/PMI/4/115 [Item 4.6 Perform Integrated Change Control]

| PMBoK, Sixth edition (2021) PMI/PMI/11/ [Item Plan risk Management]

| PMBOK^® Guide--Fifth Edition (5th) PMI/PMI//5.1 Plan Scope Management. Pages 107-110. [Item]

A project manager is managing an agile project where the team is regularly missing user story due dates. What should the project manager do to resolve this situation?

• Work with the sponsor to move out the deliverable hand over date.

• Review the time allotted to iterations and sprints, adjusting them as needed.

• Meet with the project team to identify if further agile methodologies training is necessary.

• 1. Implement a reward program for the project team to encourage completing stories on the due dates.

Answer explanation

Solution: C. Meet with the project team to identify if further agile methodologies training is necessary.

It is important for the project manager to meet with the team and analyze the issue before proceeding. This will help identify gaps in training to ensure user story due dates are met.

Then, the project manager and team members can review the time allotted to iterations and sprints, adjusting them as needed. Working with the sponsor to push delivery dates will be unnecessary when the issue is resolved and a reward system may not work for a team with differing preferences. 

This question and rationale were developed in reference to:

O'Reilly Platform (No Date) //Essential Scrum - chapter 19 - Sprint planning/ [Item]

| The Agile Practice Guide (No Date) PMI/PMI/5/58 [Item]