Project Management Professional PMP (PMP) — Questions 1–75

Option A is correct because collaborating with the team to create or update coding standards directly addresses the root cause of the conflict—ambiguity or disagreement over the standards themselves. By involving the entire team, you foster ownership, alignment, and a shared understanding, which reduces future friction. This approach aligns with the agile principle of self-organizing teams and the PMI People domain focus on collaborative conflict resolution.

The PM should first address the issue directly with the executive stakeholder, explaining the impact of bypassing the project manager and reinforcing the communication plan. This is a proactive communication approach that aligns with PMI's stakeholder management principles.

Meetings (B) are a key tool and technique in the Plan Risk Management process because they bring stakeholders together to define the risk management approach, establish risk categories, and agree on risk thresholds. These meetings produce the risk management plan, which outlines how risk activities will be structured and performed throughout the project.

Lessons learned should be accurate and transparent to benefit future projects. The PM should explain the importance of honest lessons learned and include the information, but may anonymize or phrase it constructively.

Option C is correct because the Scrum framework explicitly requires the product owner to maintain a stable sprint backlog once the sprint has started. Introducing new requirements mid-sprint violates the sprint goal and causes scope creep, which undermines team velocity and morale. As the Scrum Master or project leader, your role is to coach the product owner to defer new ideas to the product backlog for future sprint planning, preserving the integrity of the current sprint.

The daily standup is for identification, not problem-solving. The Scrum Master should facilitate a separate discussion after the standup to resolve the issue without holding up the team.

The correct first step is to address the root cause of the velocity drop—the team's overburden from external work. As the project manager lacks direct authority, you must collaborate with the functional managers who control the team members' assignments to negotiate a reduction in external workload. This aligns with the PMI principle of servant leadership and removing impediments, which is the immediate priority before adjusting plans or escalating.

Option D is correct because, as a project manager leading a hybrid team, your first responsibility is to de-escalate the conflict and create a structured environment for resolution without disrupting the daily stand-up. Acknowledging the disagreement preserves team dynamics and ensures the technical decision is made collaboratively, leveraging both developers' expertise rather than imposing a unilateral solution. Scheduling a separate meeting allows focused discussion, preventing the stand-up from losing its purpose of synchronization.

Option A is correct because a shared collaboration tool that highlights time zones directly addresses the challenge of coordinating across different time zones. By making time zone differences visible, team members can schedule meetings and deadlines more effectively, reducing communication breakdowns and missed deadlines. This is a practical, technology-enabled solution that supports asynchronous collaboration.

PMI recommends addressing the stakeholder's behavior professionally and reinforcing the change control process.

Option B is correct because PMI requires all scope changes to follow the formal change control process, even if informally agreed. The PM must ensure proper documentation and approval.

Option C is correct because creating a psychologically safe environment encourages open communication and reduces the fear of judgment, which is critical for team members experiencing cultural adjustment. This aligns with the PMI Talent Triangle's 'People' domain, emphasizing emotional intelligence and team building.

Option A is correct because the product owner is responsible for backlog prioritization, and reducing ambiguity in user stories directly addresses unclear priorities. By clarifying requirements, the team can focus on high-value work without wasting time interpreting vague tasks, which helps restore velocity.

The correct approach is to log the request and follow the change control process. Option A is correct. Option B bypasses change control; Option C ignores the request and may cause dissatisfaction; Option D assumes approval without assessment.

PMI emphasizes addressing conflict early and collaboratively. The PM should facilitate a constructive discussion to resolve the issue.

Since the project is already over budget and behind schedule, and the vendor issue affects the critical path, the best action is to evaluate options such as schedule compression techniques and then submit a change request to address the delay.

Option C is correct because the PMBOK Guide requires that any change to the project baseline, including scope, schedule, or budget, must follow the formal integrated change control process. The first step is to submit a change request to analyze the impact on quality, risks, and other constraints before making a decision. This ensures that the sponsor and stakeholders understand the trade-offs, such as increased defect risk or rework costs, before approving the reduction.

Option C is correct because the project has a contingency reserve specifically allocated for schedule risks, and the two-day delay caused by the security compliance failure is a known risk that the reserve is designed to cover. Using the contingency reserve allows the team to properly reconfigure and retest the server, ensuring security compliance without compromising project quality, while formally extending the schedule with sponsor awareness.

Cross-training reduces the impact of the risk by having a backup. This is a mitigation strategy because it reduces the probability or impact of the risk.

Option B is correct because the core issue is cross-functional collaboration due to differing priorities and jargon, which is a communication and team dynamics problem. A team-building workshop focused on communication styles and shared goals directly addresses these root causes by fostering mutual understanding and aligning the team around common objectives, which is a key leadership practice in the PMBOK Guide's 'Manage Team' process. This approach builds trust and cohesion without resorting to punitive or siloed measures.

Skipping testing compromises quality. The PM should communicate the risks and seek a formal change to the project plan through change control.

The PM should first attempt to resolve the minor issues through negotiation and follow the project's change control process if needed. Formal acceptance is crucial for project closure, so the PM should work with the customer to address concerns without gold-plating.

Option A is correct because after informal conversations have failed to resolve performance issues, the next step in progressive discipline is to formally document the issues and implement a Performance Improvement Plan (PIP). This aligns with the PMI People domain, which emphasizes addressing performance gaps through structured, documented processes before considering escalation or removal.

Option A is correct because during the forming stage of Tuckman's model, team members are often polite and uncertain; planned team-building activities help establish trust and social bonds, which are essential for later stages. This aligns with the PMBOK Guide's emphasis on developing the team as a key process in the People domain.

Option A is correct because the PMBOK Guide emphasizes proactive leadership in fostering an inclusive team environment. By organizing a cultural awareness session, you address the root cause of exclusion without waiting for a formal complaint, which aligns with the 'Servant Leadership' principle and the 'Manage Team' process. This approach prevents escalation and improves team cohesion, directly tackling low morale.

Option D is correct because the first step when a mandatory regulation arises is to analyze its impact on the project's scope, schedule, and budget, then submit a formal change request to integrate the new requirements. This aligns with the PMBOK Guide's change control process, ensuring the change is evaluated and approved before implementation, even under urgent compliance deadlines.

The storming stage is characterized by conflict and uncertainty about roles. Facilitating a session to establish ground rules and clarify roles directly addresses the root cause of storming by creating structure and mutual understanding, which is the key to moving into norming where collaboration begins. This action aligns with Tuckman's model and the PM's role as a servant leader.

In a hybrid project environment, the project manager should first facilitate a collaborative discussion between the conflicting parties to resolve the issue at the lowest level. This approach aligns with the PMP's emphasis on conflict resolution techniques, specifically 'collaborating/problem-solving,' which seeks a win-win outcome. By directly addressing the coding standards conflict, you preserve team autonomy and ownership, which is critical for maintaining morale and productivity in a hybrid approach where Agile principles like self-organization are valued.

Option C is correct because the daily stand-up is a team synchronization event for inspecting progress toward the sprint goal, not a technical Q&A session. The product owner's interruptions violate the event's timebox and purpose, causing the team to withhold information and reducing velocity. The project manager should first coach the product owner privately on the Scrum Guide's definition of the daily stand-up, emphasizing that detailed technical discussions should be deferred to separate sessions.

The risk has occurred, so the first step is to implement the planned risk response. This is proactive and follows the risk management plan.

Option A is correct because in a hybrid project, any scope change—even one that adds value and doesn't affect the critical path—must go through a formal change control process. The project manager should submit a change request to evaluate the full impact on cost, schedule, and resources before approval. This aligns with the PMBOK Guide's integrated change control and ensures that trade-offs are understood and documented.

The Cost Performance Index (CPI) is calculated as EV / AC. Here, EV = $50,000 and AC = $55,000, so CPI = 50,000 / 55,000 = 0.909, which rounds to 0.91. A CPI less than 1 indicates the project is over budget, as the cost incurred ($55,000) exceeds the value of work performed ($50,000).

Option A is correct because once a change request is approved by the CCB, the project management plan and other relevant documents must be updated to reflect the new regulatory requirement. This ensures that the project baseline (scope, schedule, cost) is formally revised and that all stakeholders are working from the same approved version, maintaining control over the project's execution.

The Scrum Master's primary role is to coach the team in self-management and continuous improvement. Since the team identified that the sprint backlog is too ambitious, the best action is to coach them on estimating and committing to a realistic amount of work based on their historical velocity. This empowers the team to make accurate commitments, directly addressing the root cause of missed sprint goals and demotivation.

According to PMI, any change to scope must go through the formal Integrated Change Control process. The project manager should document the request, assess its impact on cost, schedule, and resources, and then present it to the change control board for a decision. Option A bypasses change control; Option D is too rigid; Option C delays the process unnecessarily.

Option C is correct because it respects cultural diversity by providing alternative channels for participation, such as anonymous feedback or smaller groups, which can reduce the social pressure that inhibits contribution in larger, hierarchical settings. This approach aligns with the PMI Talent Triangle's emphasis on emotional intelligence and inclusive leadership, recognizing that a one-size-fits-all communication style may exclude team members from collectivist or high-power-distance cultures.

Option B is correct because involving the resistant team member in the agile transition planning directly addresses the root cause of resistance—lack of ownership and understanding. By participating in planning, the team member can see how agile practices (e.g., iterative delivery, adaptive planning) still incorporate upfront analysis but in a more flexible, value-driven way. This collaborative approach leverages the team member's experience while aligning with agile principles, reducing friction without forcing change.

Options A, C, and D are correct because facilitating a negotiation, reviewing the project priorities, and escalating if needed are appropriate steps. Option B is incorrect because making a unilateral decision disempowers the leaders and may cause resentment. Option E is incorrect because involving the sponsor should be a last resort after attempting resolution.

Option B and C are correct because after approval, the PM must update the project management plan and communicate the changes. Option A is incomplete, D is not a direct action for this change, E may be part of plan but not immediate.

Option C is correct because the root cause of the velocity drop needs to be understood before taking corrective action. A retrospective is the appropriate forum to discuss process improvements.

The PM should facilitate a retrospective to identify the root causes and collaboratively develop action items. This aligns with agile principles of continuous improvement.

Any change to requirements must go through the change control process. The PM should assess the impact and submit a change request.

The team charter establishes shared expectations for collaboration, communication, and conflict resolution. Since the team is co-located but working in silos, the first step is to revisit or create the team charter to realign norms and rebuild a collaborative culture, which directly addresses the root cause of decreased collaboration.

Option D is correct because, in a predictive project, the first step when a critical path delay is identified is to analyze the schedule impact and evaluate recovery options like crashing or fast-tracking. This aligns with the PMBOK Guide's 'Plan Schedule Management' and 'Control Schedule' processes, where you assess the variance and determine corrective actions before escalating. Immediately notifying stakeholders or switching vendors without understanding the impact could lead to unnecessary panic or premature decisions.

Option D is correct because the team is in the performing stage, characterized by high autonomy, trust, and self-organization. Empowering the team to make decisions within agreed boundaries leverages their maturity and maintains productivity, while periodic check-ins provide necessary oversight without micromanagement. This approach aligns with the Tuckman model and servant leadership principles, ensuring the team remains effective in the project manager's absence.

The PM should first communicate with the vendor to understand the root cause and explore solutions, and also review the contract to enforce penalties if appropriate. Escalating to senior management or terminating the contract are later steps.

Initiating team-building activities and setting clear expectations early helps form a cohesive team quickly. This aligns with the Forming stage of Tuckman's model and PMI's emphasis on team charter.

Option C is correct because it directly addresses the root cause of disconnection and overlooked input by rotating meeting times to accommodate different time zones and using video conferencing with collaboration tools to foster inclusion. This aligns with the hybrid project management principle of adapting communication methods to ensure all team members can actively participate, which is a key leadership responsibility in the People domain.

Stakeholder management: identify, analyze, plan, engage, and monitor.

In a hybrid environment, any scope change must follow the defined change control process. Option D is correct because the PM should document the request and follow the formal process. Option A bypasses governance; Option B ignores the request prematurely; Option C adds work without approval.

Option C is correct because the PMBOK Guide requires that any potential solution affecting scope must first be analyzed for its impact on the triple constraint (scope, schedule, cost) before submitting a formal change request to the Change Control Board (CCB). This ensures that the decision is based on objective data and follows the established change control process, which is critical when the project is already over budget due to unforeseen technical challenges.

Quality assurance ensures processes are followed. The PM should investigate the issue and take corrective action to prevent nonconformance.

The correct first step is to perform an impact analysis of the proposed scope reduction and submit a change request. As a project manager, you must follow the formal change control process: any change to scope, even if suggested by an executive, requires an analysis of its impact on cost, schedule, quality, and risks before any decision is made. This aligns with the PMBOK Guide's guidance that scope changes must be evaluated through a change request to ensure informed decision-making and maintain project baselines.

Resource leveling is used to address resource constraints or conflicts. Since team members are idle due to dependency conflicts, leveling can smooth resource usage and reduce idle time.

Option C is correct because it aligns with the Agile principle of self-organizing teams, where the team collaborates with the product owner to co-create a solution for unclear requirements. The project manager acts as a facilitator, empowering the team to resolve the issue collectively rather than imposing a top-down process or ignoring the problem. This approach fosters ownership, collaboration, and continuous improvement, which are core to Agile frameworks like Scrum.

Option A is correct because, as a servant leader, your primary responsibility is to protect the project's value and stakeholder interests. Cutting the quality assurance phase introduces significant technical debt and risk of defects, which could lead to rework, schedule delays, and higher costs later. By explaining these risks and proposing alternatives like scope reduction or resource optimization, you demonstrate ethical leadership and a focus on long-term project success.