PMP Flashcards — Free Project Management Professional PMP Study Cards

Facilitate a meeting to discuss and resolve differences.

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.

Initiate a formal performance improvement plan.

The project manager has already attempted informal resolution, and the continued impact on the critical path requires a formal performance improvement plan (PIP) to document the issue, set clear expectations, and provide a structured path for improvement. This aligns with the PMI's progressive discipline approach, where informal coaching precedes formal action to protect the project's schedule and maintain team accountability.

Facilitate a meeting between the team and product owner to co-create a solution.

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.

Hold a daily video call at a time that rotates across time zones.

Rotating the daily video call across time zones ensures that no single team is consistently disadvantaged by an inconvenient meeting time, promoting equitable participation and alignment. This synchronous communication method is most effective for real-time collaboration and immediate clarification, which is critical for a geographically distributed team to maintain shared understanding and project momentum.

Use anonymous polling tools to gather opinions before decisions.

Anonymous polling tools create a psychologically safe environment where team members from diverse cultural backgrounds can contribute without fear of judgment or loss of face. This aligns with the PMI Talent Triangle's emphasis on emotional intelligence and inclusive leadership, as it removes power dynamics and cultural barriers that inhibit verbal participation in meetings.

Facilitate a meeting to discuss both perspectives and find a solution that meets core needs.

Facilitating a meeting to discuss both perspectives aligns with the PMP's 'Manage Conflict' process under the 'People' domain. This collaborative approach, known as 'collaborating' or 'problem-solving,' seeks a win-win solution that addresses the core needs of both team members—ensuring quality while meeting delivery timelines—without forcing a compromise that dilutes value or ignoring the issue.

Explicitly invite the developer to share and reassure that all ideas are valued.

The project manager's first action should be to directly invite the hesitant developer to share their idea in the moment, explicitly stating that all ideas are valued. This immediate, public invitation and reassurance directly addresses the fear of criticism and models psychological safety, which is a foundational behavior for fostering an innovative team culture. In the PMP context, this aligns with the 'Servant Leadership' principle and the 'Team Performance Domain,' where the PM actively creates an environment of trust and safety.

Document the change request and conduct a formal impact analysis

The PMBOK Guide mandates that all change requests must be formally documented and analyzed for impact before any approval or rejection. Even though the project has a contingency reserve, the change introduces a new feature, which is a scope change requiring a formal change control process. The project manager must first document the request and conduct a thorough impact analysis to assess alternatives, risks, and stakeholder implications before deciding on the change.

Facilitate a retrospective with the product owner and team to review the definition of done and acceptance criteria

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.

Estimate activity resources

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.

97.5%

The critical path duration is 120 days with a standard deviation of 5 days. Completing within 130 days is 2 standard deviations above the mean (130 - 120 = 10, 10/5 = 2). In a normal distribution, approximately 95% of data falls within ±2 standard deviations, so the probability of being at or below +2σ is 50% + (95%/2) = 97.5%.

0.91

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).

Cause-and-effect diagram

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.

The project is behind schedule and under budget.

An SPI of 0.85 indicates the project is behind schedule (less than 1.0), while a CPI of 1.10 indicates the project is under budget (greater than 1.0). Therefore, the project is behind schedule but under budget, making option B correct.

Document the change request in the change log.

The first step in the formal change control process, as defined by the PMBOK Guide, is to document the change request in the change log. This ensures that all proposed changes are formally recorded and tracked before any analysis or approval activities occur. Without this initial documentation, there is no official record of the request, which undermines the integrity of the change control system.

Cherry-pick the bug fix commit to the feature branch, then revert the commit on main.

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.

Business case

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.

Facilitate a meeting with the sponsor and team to discuss trade-offs.

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.