Project Management Professional PMP (PMP) — Questions 751–825

Option A is correct because a retrospective directly addresses the root cause of unsustainable overtime, enabling the project manager to implement process improvements that prevent recurrence. Sustaining team performance requires addressing systemic issues, not just short-term relief. This aligns with the PMI talent triangle's emphasis on leadership and team motivation through continuous improvement.

The correct action is to engage stakeholders and understand their concerns. PMI emphasizes communication and stakeholder engagement to address resistance and facilitate change management.

Option D is correct because the project manager's primary responsibility is to balance stakeholder expectations with project constraints while protecting the quality of deliverables. By explaining the risks of skipping testing and proposing a risk-based testing approach, the PM demonstrates leadership by negotiating a solution that addresses the sponsor's time concerns without compromising critical quality. This aligns with the PMP's focus on leading the team and managing stakeholder communication effectively.

The PM should facilitate a discussion between the product owner and the team to clarify expectations. This demonstrates servant leadership and proactive communication. Adjusting the acceptance criteria for future sprints ensures alignment.

Option A is correct because the project manager's first responsibility is to facilitate a data-driven discussion between the sponsor and the team. By presenting trade-offs—such as the waterfall's rigid phase-gate structure versus agile's iterative feedback loops—the PM can align the project's delivery approach with its business environment and benefit realization strategy, without prematurely escalating or bypassing authority.

PMI emphasizes communication and stakeholder engagement. The PM should meet with the stakeholder to clarify roles and communication protocols.

Avoid, Transfer, and Mitigate are the three primary strategies for dealing with negative risks or threats as defined in the PMBOK Guide. Avoid involves eliminating the threat entirely by changing the project plan, Transfer shifts the impact of the threat to a third party (e.g., insurance, fixed-price contracts), and Mitigate reduces the probability or impact of the threat to an acceptable threshold. These strategies are specifically designed to address risks with a negative impact on project objectives.

Skipping testing violates quality management principles and introduces significant risk of defects reaching production, which can cause rework, cost overruns, and reputational damage. As a project manager, you must protect the project's quality baseline and stakeholder confidence. Option A correctly addresses this by explaining the risks and proposing viable alternatives like reducing test scope or adding resources, which aligns with the PMI's focus on proactive risk management and stakeholder negotiation.

The correct action is to follow the change control process. Any change to scope must be formally evaluated and approved before implementation. Simply adding to the backlog or refusing without analysis bypasses proper governance.

Option C is correct because the project manager should first assess and address the workload imbalance that is causing burnout, which is a key responsibility under the 'Manage Team' process. By discussing workload distribution with the team and considering adjustments, the PM uses a collaborative approach to optimize resource utilization without compromising the project's schedule or budget. This aligns with the PMBOK Guide's emphasis on servant leadership and proactive team management.

Option D is correct because the project manager has a fiduciary and ethical duty to prioritize safety and regulatory compliance over schedule pressure. Skipping a mandatory quality inspection violates regulations and could lead to legal liability, project shutdown, or harm. The PM must clearly communicate these risks to the sponsor and recommend against the action, as per the PMI Code of Ethics and Professional Conduct.

Option D is correct because after informal discussions have failed, the project manager should follow a structured performance management process. Having a formal meeting to discuss the issue and create a performance improvement plan (PIP) documents the problem, sets clear expectations, and provides a timeline for improvement, which aligns with the PMI's emphasis on addressing performance issues systematically before considering escalation or replacement.

Option C is correct because the question states the cost overrun trend (15% above budget) is expected to continue. The formula EAC = BAC / CPI is the appropriate 'typical' estimate at completion when current cost performance is projected to persist. With EV = $100,000 and AC = $115,000, the CPI is 0.87, and dividing the BAC by this CPI yields the forecasted total cost assuming the same efficiency.

The scrum master should facilitate the team in adjusting the sprint backlog and then communicate the impact to the product owner for reprioritization.

Resource leveling is the correct technique because it adjusts the schedule to account for resource constraints, such as a resource being available only 50% of the time. This technique modifies start and finish dates based on resource availability, ensuring the resource is not over-allocated. In this scenario, leveling would spread the resource's work across the schedule to match the 50% availability, potentially extending the project duration.

The correct answer is C because the team's velocity drop and demotivation are symptoms of underlying issues that need to be uncovered through a retrospective. In agile, the retrospective is the primary mechanism for continuous improvement, allowing the team to inspect its processes, identify root causes (e.g., technical debt, unclear requirements, or interpersonal friction), and adapt. Reassigning work or replacing team members would bypass the team's self-organization and likely worsen morale, while increasing sprint length treats a symptom without addressing the cause.

Option A is correct because the project manager should first address performance issues through direct, private communication to understand root causes and collaboratively develop an improvement plan. This aligns with the PMI People domain, emphasizing servant leadership and coaching to resolve team member performance gaps before escalating or reassigning tasks. The informal conversations have not worked, so a structured approach with clear expectations and support is the next logical step.

After addressing the issue directly with the individuals and it persists, the project manager should escalate the issue formally by documenting it in the issue log and involving the functional manager or HR if necessary. Option A is too lenient, B may escalate prematurely, and D is not the best first step after direct discussion.

The core issue is a misalignment between what the team delivered and what the product owner expects, despite following the prioritized backlog. The project manager should facilitate a retrospective to review the definition of done and acceptance criteria, as this ensures both parties have a shared understanding of what constitutes a completed, valuable feature. This aligns with agile principles of continuous improvement and stakeholder collaboration, directly addressing the root cause of the dissatisfaction.

The PM should first document the issue in the issue log (A), then evaluate alternatives to mitigate the delay (B), and communicate with stakeholders about the impact (D). Waiting for the supplier to resolve (C) is passive, and escalating to the sponsor (E) may be premature before exploring options.

Option C is correct because the immediate priority for a project manager is to de-escalate the conflict privately and understand each developer's perspective before making any decisions. This aligns with the PMI People domain principle of servant leadership and conflict resolution, where the first step is to listen and mediate in a safe, private environment to preserve team trust and psychological safety.

The correct approach is to analyze root causes and develop options. Option D includes root cause analysis and schedule compression, which are appropriate. Options A, B, C are reactive or incomplete.

Option A is correct because the first step in resolving this conflict is to have a private, collaborative discussion with the product owner to clarify roles, responsibilities, and the agreed communication protocols. This aligns with the PMI-ACP and PMP focus on servant leadership and stakeholder management, where direct confrontation is avoided in favor of coaching and realignment. Bypassing the Scrum Master undermines the agile framework and can lead to scope creep, so addressing the root cause with the product owner is the most appropriate initial action.

Option D is correct because the project manager's first responsibility in a conflict between team members is to facilitate a collaborative resolution. By bringing both developers together to discuss their perspectives, the PM demonstrates servant leadership and leverages the team's expertise to find a compromise, which aligns with the PMP's focus on leading people and managing conflict constructively. This approach directly addresses the root cause—disagreement on technical approach—without imposing a top-down decision or avoiding the issue.

Option D is correct because the first step in any project management issue is to analyze the impact and explore alternatives before taking action. Since the component is on the critical path, any delay directly affects the project finish date, so you must evaluate schedule impact and identify options like sourcing from another vendor to mitigate the risk.

Option A is correct because as a servant leader, the best course is to facilitate a retrospective to collaboratively identify root causes of the velocity drop, such as technical debt and unclear requirements, and then develop an improvement plan. This aligns with the Agile principle of continuous improvement and empowers the team to address issues at their source rather than applying top-down fixes.

Option B is correct because a virtual team with core overlap hours and collaboration tools directly addresses the challenge of a distributed team across three time zones. This structure maximizes communication by synchronizing work during overlapping hours and leverages technology (e.g., Slack, Zoom, Jira) for asynchronous collaboration, ensuring frequent decision-making without requiring physical co-location.

The project is over budget and behind schedule. The PM should analyze variances, implement corrective actions, and communicate with stakeholders. Simply asking for more budget or compressing schedule without analysis is premature.

The stakeholder is bypassing the agreed process. The PM should communicate the importance of following the change control process and reinforce the roles and responsibilities.

Option C is correct because it directly addresses the root cause of the conflict—the executive stakeholder's bypassing behavior—through a private, respectful conversation. This aligns with the PMP's focus on stakeholder engagement and conflict resolution, as it seeks to reinforce the project's communication protocols without escalating the issue publicly. By discussing the importance of following the plan, you maintain the authority of the project manager while preserving the stakeholder relationship.

Option A is correct because it aligns with the project manager's responsibility to optimize the budget without compromising quality. By analyzing the budget, you can identify non-critical areas for cost reduction, such as administrative overhead or non-essential resources, while preserving team training which directly impacts long-term performance and quality. This approach demonstrates proactive cost management and stakeholder negotiation, key aspects of the 'People' domain in leading projects.

When current CPI is expected to continue, the formula EAC = BAC/CPI is appropriate. BAC is not given but can be derived: BAC = PV * 2 = $1,000,000. So EAC = $1,000,000 / 0.82 ≈ $1,219,512.

Option B is correct: The new regulation represents a change in requirements. Following the change control process is necessary. Option A ignores the regulation, C is premature, D violates contract terms.

Change control process: receive, log, evaluate, submit to CCB, and implement if approved.

Option A is correct because it demonstrates proactive risk management and stakeholder negotiation. By explaining the risks of skipping testing and proposing a compromise—such as testing critical functions first—you address the sponsor's urgency while preserving the project's quality objectives. This aligns with the PMBOK Guide's emphasis on managing technical aspects through iterative validation and risk-based testing prioritization.

Option A is correct because the core issue is declining team interaction and psychological safety, which directly impacts collaboration in a distributed team. Virtual team-building exercises and encouraging open communication address the root cause by rebuilding trust and engagement, which is essential for effective daily stand-ups and raising blockers. This aligns with the PMP focus on servant leadership and fostering a collaborative team environment.

Any change, even to accepted work, must go through the change control process to assess impacts on schedule, cost, and scope before approval.

Crashing the schedule involves adding resources to critical path activities to compress the schedule, which is appropriate when float is negative.

In the schedule development process, after defining activities and sequencing them, the next step is to estimate the resources required for each activity (option A). This is because resource availability and constraints directly impact activity durations, and you must know what resources are available before you can estimate how long each activity will take. The PMBOK Guide's schedule management process follows the order: Plan Schedule Management → Define Activities → Sequence Activities → Estimate Activity Resources → Estimate Activity Durations → Develop Schedule.

A change request for corrective action is appropriate to fix the defect. Updating the quality management plan is not required unless a process change is needed.

D is correct because the PMBOK Guide requires the project manager to first analyze the impact of a change on the triple constraint (scope, schedule, cost) before taking any action. Since the team is at full capacity, immediate incorporation (A) or stopping work (B) would be premature without understanding the regulation's effect. Updating the risk register (C) without analysis skips the necessary impact assessment step.

Option A is correct because PMI's leadership model emphasizes that providing opportunities for professional development and learning is a key motivator that aligns with the 'Servant Leadership' approach. This practice fosters intrinsic motivation by helping team members grow their skills, which directly supports high performance and retention. It is grounded in PMI's Talent Triangle and the principle of empowering the team through continuous improvement.

Option A is correct because anonymous polling or chat-based feedback tools create a safe, low-pressure channel for team members who may be hesitant to speak up due to cultural norms about hierarchy. This approach bypasses the social dynamics of face-to-face meetings, allowing everyone to contribute equally without fear of contradicting senior members or violating cultural protocols. It directly addresses the root cause—hesitation due to hierarchy—by removing the need for verbal participation in a hierarchical setting.

Regulatory changes are a common cause of project change requests because new laws or compliance requirements (e.g., GDPR, HIPAA, or PCI DSS) can mandate modifications to project scope, deliverables, or processes. These external mandates often require immediate adjustments to avoid legal penalties, making them a frequent trigger for formal change requests in technology projects.

The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is the correct tool for root cause analysis because it systematically maps potential causes of a defect across categories like people, process, technology, and environment. In this software testing scenario, the project manager would use it to brainstorm and visually trace the critical defect back to its underlying technical root cause, such as a coding logic error or integration failure, rather than just observing symptoms.

Option A is correct because inaccurate estimation techniques can lead to consistently missed velocity targets. By reviewing and recalibrating estimation methods (e.g., story points, planning poker), the PM ensures the team's capacity is realistically measured, which is critical for sprint planning in a hybrid methodology.

Limiting work-in-progress (WIP) can reduce context switching and improve focus. Implementing a change control process for scope changes during a sprint helps stabilize requirements. Both address root causes of velocity drop.

Regular video calls with structured agendas foster connection and effective communication in virtual teams.

Option A is correct because the PMBOK Guide requires that when a new regulation is announced, the project manager must first analyze its impact on the project's compliance requirements. Since the regulation will be in effect before project completion, proactive assessment is needed to determine if a change request is necessary to align the project with future legal obligations. This follows the 'plan-do-check-act' cycle and ensures the project remains compliant without unnecessary disruption.

Option A is correct because the addition of a new reporting module represents a change to the approved scope baseline. According to the PMBOK Guide, any change to scope must go through the Integrated Change Control (ICC) process, which includes submitting a formal change request, assessing impacts on scope, schedule, cost, and quality, and obtaining approval before implementation. This ensures that all changes are evaluated and controlled, preventing scope creep and maintaining project alignment with business objectives.

The project is behind schedule (SPI < 1) and over budget (CPI < 1). Option B is correct: analyze root causes and take corrective action. Option A is wrong because EAC may change; Option C is wrong because you communicate after analysis; Option D is a possible technique but not the next step.

To prevent scope creep, the PM should educate the team on the change control process so they know not to accept informal requests. Additionally, the PM should reinforce the communication plan to ensure all requests go through the proper channels. Option A is reactive; Option D is not the best practice.

CPI = EV/AC = $120,000/$130,000 = 0.92. A CPI less than 1 indicates the project is over budget.

Options B, C, and D are correct: facilitating a retrospective, removing impediments, and ensuring sustainable pace are key agile practices to improve team performance.

The PM should clarify the proper process and communicate with the executive. Option B is correct because it addresses the bypass and reinforces change control. Option A escalates without conversation; Option C ignores the issue; Option D violates process.

Option B is correct because lessons learned must capture both positive and negative outcomes to provide a balanced view for future projects. Including the budget overrun with root causes and recommendations enables continuous improvement, which is a core principle of project management. The PMBOK Guide emphasizes that lessons learned should document what went well and what did not, along with actionable insights.

Option C is correct because a team charter establishes ground rules for communication, decision-making, and conflict resolution, which directly reduces misunderstandings and interpersonal conflicts within the team. This aligns with the PMBOK Guide's emphasis on the team charter as a tool to foster a collaborative and respectful team environment.