Project Management Professional PMP (PMP) — Questions 376–450

Option B is correct because a daily stand-up meeting at a rotating time ensures that all team members across different time zones have an equal opportunity to participate, fostering regular communication and alignment. This directly addresses miscommunication and missed deadlines by creating a predictable, inclusive cadence for sharing progress and blockers.

Option A is correct because it aligns with the agile principle of self-organizing teams and collective ownership. By encouraging the team to collaboratively define a coding standard, you empower them to reach a consensus that everyone can commit to, which directly addresses the root cause of the conflict and improves morale and productivity. This approach fosters team cohesion and ensures the standard is practical and accepted by all, rather than being imposed externally.

Option D is correct because the PM should educate the sponsor on the benefits of agile for uncertain work while respecting governance. A hybrid approach can satisfy both needs.

Option A is correct because, as a project manager leading a global virtual team, the best approach to resolve a conflict between two senior developers from different cultures is to mediate a meeting where they can openly discuss their concerns. This aligns with the PMP's focus on collaborative problem-solving and emotional intelligence, allowing both parties to express their perspectives on time zone respect and micromanagement, leading to a mutually agreed solution. Mediation fosters trust and understanding, which is critical for virtual team cohesion and productivity.

Facilitating a meeting to discuss and resolve differences (D) is the best approach because it directly addresses the root cause of the conflict—work style incompatibility—by fostering open communication and collaborative problem-solving. As a project manager, you act as a servant leader, using conflict resolution techniques like 'confronting' or 'problem-solving' to turn the disagreement into a constructive dialogue that aligns the team toward project goals. This approach preserves team cohesion and leverages the developers' expertise without escalating or avoiding the issue.

Option B is correct because it preserves a clean Git history by first cherry-picking the bug fix commit from main to the feature branch (ensuring the fix is applied where intended), then reverting the commit on main to remove the accidental change without rewriting history. This avoids merge commits or destructive operations, maintaining a linear and traceable project history.

Option B is correct because the first step in addressing a participation issue in a virtual team is to understand the root cause through direct, private conversations. This aligns with the PMP principle of 'servant leadership' and the 'People' domain, where you must first investigate barriers (e.g., time zone fatigue, cultural norms, or tool discomfort) before implementing solutions. A one-on-one meeting builds psychological safety and gathers specific feedback, which is essential for an effective corrective action.

Virtual pair programming sessions are correct because they enable real-time, collaborative problem-solving on complex tasks, directly addressing knowledge sharing and collaboration gaps in a distributed team. This technique fosters active learning and mentorship, which is especially valuable when team members have varying levels of experience and work across different time zones.

Option D is correct because a team charter establishes agreed-upon norms for meeting behavior, including expectations for participation, which proactively addresses the root cause of silence in a diverse, distributed team. This aligns with the PMBOK Guide's emphasis on creating a team charter to define ground rules and foster a collaborative environment, especially when virtual communication challenges exist.

When current cost performance is expected to continue, EAC = BAC/CPI. BAC = $500,000, CPI = 0.85, so EAC = $500,000 / 0.85 ≈ $588,235.

To improve daily standups, the Scrum Master should enforce time-boxing, encourage focused updates, and perhaps change the format or location to keep them concise. Assigning a rotating facilitator can also help.

Option B is correct because protecting the team from external interruptions and scope changes during the sprint is a core agile practice that enables self-organization. Without this protection, the team cannot maintain focus on their committed work, and external pressures undermine their autonomy to manage their own process. This aligns with the Scrum principle of a stable sprint backlog and the product owner's role in shielding the team.

Option C is correct because video conferencing adds a visual and non-verbal communication layer that significantly improves personal connection in distributed teams. This aligns with agile principles of face-to-face communication and helps reduce the sense of isolation, directly addressing the team's feeling of disconnection.

The correct action is to submit a change request through the Integrated Change Control process. PMI requires formal assessment and approval before implementing any change that impacts scope, schedule, or cost. Proceeding without change control violates the project management plan.

Option C is correct because any change that impacts the business case must go through the change control process. Option A bypasses approval, option B is premature without analysis, option D escalates without proper documentation.

When a new regulation arises, the PM should first analyze the impact, then submit a change request to formally propose the changes, and finally update the project management plan and documents after approval. Informing the team immediately is premature without analysis. Escalating to the change control board is part of the process but not the first step.

Establishing regular video conference meetings (A) is correct because it enables synchronous, face-to-face communication, which is critical for bridging cultural and time-zone gaps in distributed teams. Video conferencing reduces misunderstandings by allowing non-verbal cues and real-time clarification, directly addressing the communication breakdowns described in the scenario.

The scrum master is responsible for removing impediments. Option B is correct because the scrum master should escalate the issue to remove the blocker for the team.

Crashing adds resources to critical path tasks; fast-tracking performs tasks in parallel. Both are schedule compression techniques.

The PM should facilitate a retrospective to identify root causes. Option C is correct because it addresses the issue using agile ceremonies. Option A avoids the problem; Option B adds pressure; Option D is reactive.

Option B is correct because a virtual collaboration platform that integrates chat, video conferencing, and shared document repositories directly addresses the core challenges of distributed teams: real-time interaction, synchronous meetings, and centralized document access. This combination reduces communication latency across time zones and ensures all team members have a single source of truth for project artifacts, which is essential for effective collaboration in a multi-timezone environment.

When the current cost performance is considered typical and expected to continue, the EAC is calculated as BAC / CPI = $1,000,000 / 0.85 ≈ $1,176,471. This is the most common formula for EAC when variances are expected to persist.

The PM should address performance issues formally by documenting the issue and discussing it with the team member, setting clear expectations and consequences. This follows a progressive discipline approach.

The PM should first discuss the issue privately with the team member to understand the root cause and offer support, such as training or resources. This aligns with servant leadership.

Options A, C, and E are correct because establishing a team charter with norms for respect, using inclusive language, and celebrating differences all foster inclusion. Option B is incorrect because ignoring cultural differences reduces collaboration. Option D is incorrect because focusing communication in one language may exclude non-native speakers.

The PM should facilitate a conversation between the team and the product owner to improve the definition of ready. This empowers the team and improves collaboration.

When a risk event that was identified and included in the risk register occurs, the project manager should first implement the agreed-upon risk response that was already planned and documented. This is because the risk response plan was developed during risk planning and approved by stakeholders, making it the immediate and correct action to take. Implementing the pre-agreed response ensures a timely, consistent, and controlled reaction to the risk, minimizing disruption to the project schedule.

The project manager should present the updated business case and recommend a formal review to decide whether to continue or terminate. Sunk costs should not drive decisions.

Effective daily standups are time-boxed (e.g., 15 minutes) and focus on progress, plans, and impediments. Using a visual board helps keep the discussion focused.

D is correct because the PMBOK Guide mandates that any change, including a new regulatory requirement, must first be processed through a formal change request to evaluate its impact on scope, schedule, and cost. Since the project is already halfway through its schedule, the project manager must follow the integrated change control process to ensure the change is assessed before any action is taken. This prevents unauthorized changes that could disrupt project baselines.

Team development: identify needs, acquire, build, set rules, and train.

Option A is correct because, as a project manager, your first responsibility is to address the sponsor's request directly by communicating the quality risks and negotiating a balanced solution. Risk-based testing allows you to prioritize critical test cases, reducing overall testing time while still mitigating the highest-priority quality risks, which aligns with the hybrid project's need for both agility and governance.

The business case documents the justification for the project, including alignment with organizational strategy, expected benefits, and ROI. For a CRM implementation, the business case would confirm that the system supports strategic goals like improving customer retention or sales efficiency, making it the correct reference for value alignment.

Option A is correct because a team charter establishes clear communication norms, meeting times, and collaboration tools, which directly addresses the root cause of disconnection in a virtual team. By defining these expectations upfront, the charter reduces ambiguity and ensures all members are aligned on how and when to communicate, fostering cohesion. This aligns with the PMBOK Guide's emphasis on creating a team charter to set ground rules and improve team performance.

Option D is correct because the project manager's role includes facilitating conflict resolution among team members to maintain team cohesion and project progress. By mediating a meeting, the PM addresses the root cause of the delays—technical disagreement—while empowering the team to find a mutually acceptable solution, which aligns with the PMP's emphasis on servant leadership and collaborative problem-solving.

Option C is correct because the first step in addressing a potential performance issue is to gather information through a private, respectful conversation. The project manager should schedule a one-on-one meeting to understand the team member's workload and challenges before taking any corrective action, aligning with the PMI's emphasis on servant leadership and emotional intelligence.

Option C is correct because, as a project manager, your first responsibility is to address the sponsor's request professionally by communicating the risks of skipping quality inspections—such as potential rework, safety failures, and cost overruns—and then collaboratively exploring alternatives (e.g., parallel testing, reduced sampling) to meet the deadline without compromising quality. This aligns with the PMP's emphasis on stakeholder engagement and proactive risk management, not blind compliance or refusal.

The PM should address the issue directly with the stakeholder to clarify roles and communication protocols. This is a stakeholder management and communication issue that requires a proactive conversation.

Resource levelling can be resolved by adjusting the schedule or adding resources. The PM should evaluate options and communicate with stakeholders.

Per PMI, any new risk should be documented in the risk register, and then the PM should plan a response. The first step is to add it to the register.

Option D is correct because rotating meeting times periodically ensures equitable access to synchronous decision-making for all team members, directly addressing the core issue of inclusion in a virtual team with diverse time zones. This approach aligns with the PMP's emphasis on servant leadership and stakeholder engagement by proactively mitigating the negative impact of time zone differences on team cohesion and participation.

Option B is correct because regular virtual team-building activities directly address feelings of isolation by fostering interpersonal connections and trust among remote team members. Option D is correct because creating a shared project vision and team charter aligns the team around common goals, expectations, and values, which counteracts disconnection from project objectives. Together, these actions improve both social cohesion and goal alignment, which are critical for virtual team success.

The PM should implement the agreed-upon contingency plan as per the risk response strategy. This is proactive and follows the plan.

The benefits realization report tracks whether the expected business outcomes from the cloud migration are being achieved. If the project's deliverables (e.g., migrated applications, infrastructure) do not fully support the expected benefits—such as cost savings from auto-scaling or performance gains from cloud-native services—then the benefits will not materialize, regardless of schedule or team skill. This is the most direct cause because benefits depend on the alignment between deliverables and the defined benefit criteria.

Option B is correct because it follows the PMI conflict resolution principle of 'collaborate/problem-solve' by first gathering individual perspectives privately before facilitating a joint discussion. This approach ensures each developer feels heard, reduces emotional tension, and allows the project manager to identify the underlying technical merits of each argument without group bias. It is the best first step because it addresses the root cause of the conflict—differing technical opinions—before attempting any resolution or escalation.

Option A is correct because providing diversity and inclusion training addresses the root cause of the misunderstanding—cultural differences in communication styles—by educating the entire team on high-context vs. low-context cultures. This aligns with the PMP's focus on fostering a collaborative team environment through mutual understanding, rather than singling out or forcing change on one individual. It promotes team cohesion by building awareness and respect for diverse communication norms, which is essential for leading projects in a global context.

Schedule development includes defining activities, estimating, sequencing, applying leads/lags, and determining the critical path.

Option D is correct because creating a team charter with agreed-upon meeting norms proactively establishes a framework for respectful and balanced participation, addressing cultural differences without singling out individuals. This aligns with the PMBOK Guide's emphasis on team charter development as a tool to define ground rules and foster a collaborative, inclusive environment from the start.

Option A is correct because, as the project manager, your first responsibility is to address interpersonal conflicts directly and collaboratively. Scheduling a meeting with both developers to discuss the issue and find a mutually agreeable solution aligns with the PMI's emphasis on conflict resolution techniques like 'collaborating/problem-solving,' which seeks a win-win outcome. This approach preserves team morale and productivity by involving the stakeholders in the decision, rather than imposing a solution or avoiding the problem.

Strategic alignment (A) is a key consideration because it ensures the proposed project directly supports the organization's overarching goals and competitive strategy, which is the primary filter in portfolio selection. Without alignment, even a profitable project can divert resources from more critical strategic initiatives, leading to suboptimal portfolio value.

Option A is correct because, as a project manager, your first responsibility is to address performance issues directly with the team member through a private, supportive conversation. This aligns with the PMI People domain's emphasis on servant leadership and conflict resolution, allowing you to understand root causes (e.g., unclear requirements, personal challenges) before taking corrective action. In a predictive project, reassigning tasks or escalating prematurely can damage trust and team morale, while ignoring the issue risks further schedule slippage.