Project Management Professional PMP (PMP) — Questions 301–375

This is the correct course of action because the primary responsibility is to execute the pre-planned risk response to manage the identified risk effectively. Once the response is implemented, the project manager must accurately assess the actual impact on the project schedule. Any resulting deviation from the baseline schedule then necessitates a formal change request, which will be processed through the integrated change control system to obtain approval for adjusting the project baselines.

Discovering a nonconformance during a quality audit mandates formal documentation as an output of the Control Quality process. Subsequently, performing a root cause analysis is crucial to identify the underlying reasons for the defect, preventing recurrence rather than just fixing the symptom. Finally, implementing corrective actions addresses the root cause and brings the deliverable into conformance, ensuring project quality objectives are met and continuous improvement is fostered.

A core responsibility of an agile project manager, or Scrum Master, is to establish a clear vision and well-defined sprint goals, along with necessary operational boundaries. This provides the team with the "what" and "why," enabling them to self-organize and determine the "how." Trusting the team to deliver within these parameters fosters autonomy, increases motivation, and leverages their collective expertise, aligning with servant leadership principles.

A facilitated charter workshop lets the team collaboratively define ground rules, values and communication protocols, securing genuine commitment rather than imposed rules. This directly establishes the clear behavioural and communication expectations the project manager seeks when forming the new team.

Collaborative problem-solving directly addresses the technical disagreement by having both senior members jointly own the solution, which restores team morale. This is the integrative approach in the PMBOK conflict model, satisfying the stem's need to resolve conflict while preserving working relationships.

A sprint retrospective directly addresses the stem's constraint: three consecutive velocity drops with team-reported overwhelm and shifting 'done' criteria. It provides the empirical inspect-and-adapt forum where the team itself surfaces root causes and collaboratively agrees corrective actions, satisfying the "FIRST" requirement since diagnosis must precede any process change.

Scheduling a private meeting with the sponsor is the most appropriate and professional first step. This direct, one-on-one communication allows the project manager to respectfully clarify roles, responsibilities, and the agreed-upon project communication plan, ensuring alignment and preventing future misunderstandings. It demonstrates proactive problem-solving and reinforces established project governance without creating conflict or undermining authority. This approach aims to resolve the issue collaboratively.

This is the most appropriate first action as it immediately mitigates the risk of further scope creep and resource misallocation by halting unauthorized work. Following this, engaging directly with the executive stakeholder demonstrates proactive leadership, reinforces the project's established change control procedures, and educates them on the correct channels for future requests, thereby safeguarding project integrity and scope.

Adding resources from non-critical path activities to critical path tasks is a valid schedule compression technique known as crashing. By reallocating existing resources that have float to activities directly impacting the project's end date, the duration of critical path tasks can be reduced. This approach effectively shortens the overall project schedule without necessarily incurring additional direct costs for new resources, making it a cost-effective method when internal resources are available.

Assessing the regulatory requirement's impact on scope, schedule, and cost precedes any change request, because the change control process needs that analysis. Submitting a request first, or simply implementing the requirement, bypasses integrated change control in this regulated context.

When a risk event occurs, the project manager must first re-evaluate the effectiveness of the existing risk response plan, which in this case might have been "accept." This involves analyzing the impact of the vendor's inability to deliver and determining if a new proactive or reactive strategy, such as mitigation or contingency, is now required. If a new response significantly alters baselines or the project management plan, a formal change request must be submitted through the integrated change control process.

When a project experiences performance issues, the most appropriate first step for a project manager overseeing a portfolio is to conduct a benefits review and reassess its alignment with organizational strategy. This critical analysis determines if the project still delivers expected value and contributes to strategic objectives, even with current challenges. This data-driven approach provides the foundation for a sound recommendation to the steering committee regarding continuation, modification, or potential termination, ensuring portfolio optimization.

This is the most appropriate initial action. A project manager's primary responsibility is to proactively analyze the situation, quantify the potential impact on critical project constraints like schedule and cost, and then develop potential mitigation strategies or alternative solutions. This data-driven approach allows for informed decision-making and demonstrates leadership before escalating or taking drastic measures.

The norming stage is where team members begin to resolve differences, develop cohesion, and establish working norms and relationships. However, teams in this stage often prioritize harmony, leading to an avoidance of deeper, constructive conflict that could challenge established comfort zones. Encouraging diverse viewpoints and facilitating healthy debate is crucial here to prevent groupthink, foster innovation, and enable the team to address complex issues more effectively, thus maturing towards higher performance.

Coaching the Product Owner is the most appropriate initial action, as it addresses the root cause through education and collaboration rather than immediate escalation. This reinforces their accountability for maintaining a stable sprint goal, which is crucial for the Development Team's focus and predictability. Guiding them to manage changes exclusively through the product backlog upholds Scrum principles, ensuring transparency and proper prioritization for future sprints.

This approach balances efficiency and engagement by defining clear boundaries for decision authority. Involving the team in setting criteria gives them ownership and transparency, while centralizing critical decisions ensures speed. It aligns with PMP principles of servant leadership and situational decision-making, such as using a RACI or decision matrix to clarify roles and responsibilities.

A project audit revealing skipped Quality Assurance (QA) inspections indicates a critical process breakdown. The Project Manager's primary responsibility is to investigate the root cause of this non-conformance, as QA focuses on process adherence to prevent defects proactively. Reinforcing preventive activities ensures that established quality processes are followed, thereby maintaining quality standards and reducing the likelihood of future quality issues and rework. This action directly addresses the identified process deviation and upholds the project's quality management plan.

This approach embodies servant leadership and emotional intelligence by actively listening to team concerns and validating their feelings. Facilitating a discussion about the appropriate balance between project manager guidance and team autonomy, followed by collaboratively establishing clear decision-making boundaries, empowers the team. This fosters a sense of ownership, improves psychological safety, and promotes self-organization, aligning perfectly with agile values and principles for continuous improvement.

Because the requirement is mandatory and affects scope, the change must pass through integrated change control before any work begins. Submitting a change request and assessing impact on schedule, cost and resources satisfies the stem's constraint, enabling the CCB to authorise the two-week implementation.

The most appropriate first step is to leverage Earned Value Management (EVM) tools for an objective assessment of the project's financial performance. Calculating the Cost Performance Index (CPI) provides a critical efficiency ratio, indicating cost efficiency, while the Estimate at Completion (EAC) forecasts the total project cost based on current performance trends. This data-driven analysis is essential for accurately understanding the magnitude of the overrun, identifying its root causes, and formulating effective, evidence-based corrective or preventive actions.

Publicly appreciating individual contributions directly addresses the fundamental human need for recognition, fostering a sense of value and boosting morale within the team. Involving the team in key decisions empowers them, leveraging their collective expertise and increasing their sense of ownership and commitment to the project's outcomes. This approach aligns with servant leadership principles, promoting psychological safety and sustained intrinsic motivation, which are crucial for an ongoing project's success under new leadership.

Facilitating a retrospective is the most appropriate action as it embodies the principles of continuous improvement and team self-organization in Agile frameworks. This structured event allows the entire team to collaboratively inspect past performance, identify the true root causes of challenges, and collectively decide on actionable improvements for future sprints or iterations. It fosters a culture of transparency, learning, and shared ownership, leading to sustainable solutions and enhanced team effectiveness.

This is the most effective solution because it proactively addresses the core challenges of virtual team communication through structured planning and appropriate technological enablement. Reviewing and updating the communication management plan ensures that communication requirements, methods, and responsibilities are clearly defined for a distributed environment. Simultaneously, establishing a shared collaboration platform with explicit guidelines provides the necessary tools and framework for consistent, accessible, and efficient information exchange, bridging geographical and temporal gaps.

This is the correct action as it upholds project governance and the integrity of the project baselines. The project manager must ensure that all proposed changes, regardless of their perceived magnitude or the stakeholder's influence, are formally submitted, analyzed for impact, and approved or rejected according to the established change control process. This ensures transparency, traceability, and controlled evolution of the project scope, schedule, and budget.

This is the correct agile approach. The Product Owner should explain that any new feature requests or changes must be added to the product backlog. This allows for proper evaluation, refinement, and prioritization against other existing backlog items, ensuring that the most valuable work is selected for future sprints. Maintaining a stable sprint commitment is crucial for team focus and predictable delivery.

The PERT expected duration is calculated as (O + 4M + P) / 6. Plugging in the values: (5 + 4*8 + 17) / 6 = (5 + 32 + 17) / 6 = 54 / 6 = 9 days. This weighted average gives more weight to the most likely estimate and is used to account for uncertainty in activity duration estimates.

Before any decision regarding a change, a thorough impact analysis is crucial. This involves evaluating how the proposed change will affect the project's scope baseline, schedule baseline, cost baseline, and quality requirements. Understanding these potential ramifications enables the project manager and stakeholders to make an informed decision, ensuring the change aligns with project objectives and constraints.

Arranging a mediation session provides a structured and neutral environment for team members to articulate their perspectives and learn about each other's cultural norms. This facilitated dialogue fosters empathy, builds mutual respect, and equips the team with practical strategies for navigating future cross-cultural interactions constructively. It directly addresses the root cause of conflict by promoting understanding and inclusivity, which are essential for a globally diverse team's success.

A focused retrospective surfaces the specific drivers behind the unplanned support load, such as missing documentation or unclear ownership, rather than accepting the generic symptom. Identifying root causes lets the team design targeted countermeasures instead of repeatedly absorbing the same interruptions.

When a previously identified risk event materializes during project execution, the project manager's immediate and primary responsibility is to execute the pre-defined risk response strategy. This proactive implementation, as detailed in the risk register, is crucial for mitigating the potential negative impact and ensuring the project stays on track. Delaying this action to perform other tasks would contradict the purpose of risk planning and increase adverse consequences. It is the direct output of the 'Implement Risk Responses' process.

This statement is correct. The business case is a critical pre-project document that provides the necessary information to determine if a proposed project is strategically aligned and financially viable. It articulates the problem or opportunity, analyzes various options, and presents a detailed justification for undertaking the project based on its expected business value, return on investment, and contribution to organizational objectives. This document is fundamental for decision-makers to authorize the project.

The Scrum Master's role includes facilitating Scrum events and helping the team improve its processes and effectiveness, aligning with the servant-leader mindset. By facilitating a discussion during the retrospective, the Scrum Master empowers the team to collaboratively identify root causes for standup inefficiencies and propose solutions, fostering continuous improvement and reinforcing the team's self-managing capabilities.

Meeting privately with the involved parties, Maria and John, is the most appropriate first step for a project manager to address a technical disagreement constructively. This approach allows the project manager to actively listen to each perspective, understand the underlying reasons for the conflict, and identify common ground or alternative solutions. By facilitating a direct conversation, the PM can guide them towards a mutually acceptable resolution, strengthening team collaboration and ownership.

A drop in velocity, particularly when linked to unplanned work, signals a systemic issue that requires root cause analysis rather than superficial adjustments. This option directly addresses the problem by investigating why unplanned work is occurring and empowering the team to devise strategies to mitigate these interruptions. This proactive, team-centric approach aligns with agile principles of continuous improvement and problem-solving, ensuring sustainable velocity rather than just temporary fixes.

The Scrum Master's core responsibility is to ensure the team understands and commits to the Sprint Goal, acting as a servant leader and impediment remover. A decrease in velocity often signals a lack of clarity, shared understanding, or alignment with the current goal, hindering the team's ability to focus and deliver. Facilitating a discussion to review and clarify the Sprint Goal directly addresses this potential root cause, empowering the team to regain focus and improve performance.

This is the correct approach because all proposed changes, regardless of project methodology (predictive, agile, or hybrid), must be formally evaluated through the Integrated Change Control process. The Product Owner, as the representative of stakeholder needs, is the appropriate party to formally submit a change request, which then allows for a structured assessment of its impact on scope, schedule, cost, resources, and risks before a decision is made. This ensures project baselines are maintained and all stakeholders are informed.

Implementing daily stand-up meetings is a core agile practice that fosters regular communication and transparency within the team. For a distributed team spanning multiple time zones, rotating the meeting time ensures equitable participation, preventing any single group from consistently attending at inconvenient hours. This approach enhances team cohesion, identifies impediments promptly, and maintains a shared understanding of progress and upcoming tasks.

In agile, empowering the self-organizing team to collaboratively define their own working agreements, such as coding standards, is a highly effective conflict resolution strategy. This approach fosters a strong sense of ownership and commitment among team members, as they are directly involved in creating the solution. By reaching a consensus, the team builds a shared understanding and mutual respect, which significantly reduces future conflicts and improves adherence to the agreed-upon standards. This aligns with agile values of individuals and interactions over processes and tools.

This is the most appropriate action as it directly addresses the conflict by leveraging the project manager's role as a facilitator and integrator. By bringing the sponsor and product owner together, the PM can guide a discussion to understand their respective concerns and objectives, ultimately leading to a tailored hybrid approach. This strategy promotes stakeholder alignment, ensures transparency, and allows for the integration of both predictive planning and agile exploration, optimizing project delivery for complex environments.

This is the most effective approach as it directly addresses the conflict through collaborative problem-solving, which is a key PMP-recommended technique. By mediating, the project manager facilitates open communication, allowing both developers to express their perspectives and work together to find a mutually acceptable resolution. This fosters a sense of ownership over the solution, strengthens team cohesion, and builds trust, leading to a more sustainable outcome than imposed solutions.

Facilitating a meeting lets both developers voice concerns and agree on working norms, addressing the interpersonal conflict's root cause rather than suppressing it. This collaborative approach satisfies the need to resolve the conflict while preserving the working relationship and unblocking project delays.

Cherry-picking the bug fix commit to the feature branch first applies the specific changes from that commit as a new commit on the feature branch, ensuring the fix is present where it's needed. Subsequently, reverting the original commit on main creates a new commit that cleanly undoes the bug fix on main without rewriting history. This two-step process safely isolates the fix to the feature branch while removing it from main in a non-destructive manner.

Coaching the team member individually is a primary responsibility of an agile leader or Scrum Master, focusing on understanding the underlying causes of missed commitments rather than just the symptoms. This approach respects the individual's autonomy while providing targeted support to identify skill gaps, external blockers, or motivational issues. By addressing the root cause, the team member can develop sustainable solutions and improve their performance within the self-organizing team structure. This fosters personal growth and strengthens team capability.

Scheduling one-on-one meetings demonstrates proactive engagement and respect for individual perspectives, which is crucial for virtual teams. This approach allows the project manager to gather direct, unfiltered feedback on specific barriers, such as time zone conflicts, cultural communication norms, or perceived value of contributions, without public pressure. This aligns with effective stakeholder engagement and conflict resolution techniques, aiming to understand the underlying issues before formulating solutions.

Virtual pair programming directly addresses knowledge sharing and complex problem-solving in distributed teams. By having two team members collaboratively work on the same code or task remotely, it facilitates real-time knowledge transfer, immediate feedback, and joint problem-solving. This approach significantly enhances code quality, reduces defects, and builds collective understanding, which is crucial for complex deliverables where individual expertise might be insufficient.

This action directly addresses the root cause of the audit finding by strengthening the project's change control system. By mandating written approval *before* implementation, the project ensures that all future changes are properly authorized and documented, aligning with compliance requirements and preventing similar issues from arising in subsequent audits. This is a crucial preventative action for long-term project governance and audit readiness.

A team charter is a foundational document that establishes clear ground rules, shared values, and mutual expectations for team members, including specific guidelines for meeting conduct and participation. By collaboratively defining these expectations, the team builds a sense of ownership and psychological safety, encouraging all members to contribute actively and respectfully in virtual settings. This proactive approach addresses the root cause of low participation by setting a common standard for engagement.

This is the correct Estimate At Completion (EAC) calculated using the formula EAC = BAC / CPI, which assumes that future cost performance will continue at the same rate as the historical performance. Given a Budget At Completion (BAC) of $500,000 and a Cost Performance Index (CPI) of 0.85, the calculation is $500,000 / 0.85, yielding approximately $588,235. This indicates the project is projected to finish significantly over its initial budget due to current cost inefficiencies.

The Daily Scrum is strictly time-boxed to a maximum of 15 minutes for a typical sprint, regardless of the team size or sprint length. Enforcing this time-box ensures the meeting remains focused on the three key questions (what was done, what will be done, any impediments) and prevents it from becoming a detailed problem-solving session, which should occur separately with relevant individuals after the standup. This discipline maintains efficiency and respects team members' time, aligning with Scrum's lean principles.

Protecting the team from external interruptions and scope changes during the sprint is a critical responsibility of an agile project manager, acting as a servant leader. This shielding creates a stable environment, allowing the development team to maintain focus on the sprint goal and manage their own workflow effectively. It prevents distractions that could derail progress, ensuring the team can deliver committed increments and sustain their self-organizing rhythm.

For distributed agile teams, leveraging video conferencing for all team meetings is critical for fostering stronger personal connections and mitigating the challenges of physical distance. Seeing facial expressions and body language significantly enhances non-verbal communication, builds rapport, and promotes a sense of shared presence, which is vital for team cohesion, trust, and effective collaboration in an agile context. This practice helps to reduce feelings of isolation and improve overall team dynamics.

This is the most appropriate and proactive action when a risk event occurs. During the Plan Risk Responses process, specific strategies (e.g., avoid, mitigate, transfer, escalate, accept) are developed for identified risks and documented in the risk register. When a risk event materializes, the project manager's primary responsibility is to execute the pre-defined response plan, which is designed to minimize the impact or likelihood of the risk. This demonstrates effective risk management and adherence to the project management plan, leveraging prior planning efforts.

This is the correct and most professional approach according to PMI principles. Any proposed change that affects a project's baselines—scope, schedule, or cost—must be formally documented as a change request and processed through the Integrated Change Control process. This ensures a thorough impact analysis is conducted, allowing stakeholders to make informed decisions regarding approval or rejection, thereby maintaining project governance and control.

Submitting a formal change request is the correct project management practice, initiating a structured process to evaluate the proposed feature's comprehensive impact on the project's scope, schedule, cost, quality, and risks. This ensures that any potential changes to the project baselines are thoroughly assessed against the business case and formally approved by the appropriate authority, such as a Change Control Board, before implementation.

This is the most appropriate and professional project management approach. A formal performance review ensures objective assessment and documentation of the specific issues, providing a clear record. Creating a Performance Improvement Plan (PIP) with defined expectations and timelines offers a structured path for the team member to address deficiencies, aligning their performance with project objectives and organizational standards while demonstrating supportive leadership.

Servant leadership removes impediments so the team can deliver; unclear requirements are exactly such an impediment. The product owner owns requirement clarity, so the project manager facilitates that clarification rather than directing the team or reassigning work, restoring the flow the sprint depends on.

Updating the project management plan and other project documents is a critical final step in the formal change control process, occurring only after a change request has been thoroughly reviewed and officially approved. This ensures all project baselines, subsidiary plans, and relevant documentation accurately reflect the new requirements, maintaining project integrity and providing a current, reliable reference for all stakeholders and future project activities.

Enforcing the 15-minute timebox is a critical technique for maintaining the efficiency and focus of the daily standup. This constraint encourages team members to be concise, prioritize key updates, and defer detailed discussions to separate follow-up meetings. Adhering to the timebox prevents the standup from becoming a lengthy problem-solving session or a general discussion forum, ensuring it remains a quick coordination event.

Synchronous video conferencing directly addresses the communication breakdowns caused by onshore/offshore distribution, restoring real-time dialogue that asynchronous channels cannot provide. It satisfies the hybrid methodology's need for structured, frequent interaction across time zones, enabling immediate clarification and reducing the misunderstandings fuelling conflict.

Fast tracking is a schedule compression technique where activities or phases that would normally be performed sequentially are instead performed in parallel or overlapped. This approach reduces the overall project duration by starting subsequent activities before their predecessors are fully complete, particularly on the critical path. While it can significantly shorten the schedule, fast tracking inherently increases project risk, potentially leading to rework, quality issues, or communication challenges due to the increased concurrency.

In agile, a decreasing velocity signals a process or environmental issue, not necessarily a performance deficit. A retrospective is the prescribed event for the team to inspect its past sprint, identify root causes for the velocity drop (impediments), and collaboratively determine actionable improvements for the next sprint. This fosters continuous improvement and team ownership in adapting their working processes.

This is the correct project management action. Any new requirement, even if mandatory or regulatory, constitutes a change to the project baseline and must be formally managed through the integrated change control process. Initiating a change request ensures the requirement is documented, its impact on scope, schedule, cost, quality, and resources is thoroughly assessed, and stakeholders can make informed decisions before implementation. This systematic approach prevents uncontrolled scope creep and maintains project control.

Scheduling a dedicated meeting exemplifies a proactive and collaborative Agile approach to resolving customer dissatisfaction. This allows for a focused discussion to thoroughly review the customer's current expectations, understand the root cause of the perceived gap, and collaboratively explore potential adjustments to the product backlog. This aligns with the "inspect and adapt" principle and fosters strong stakeholder relationships by demonstrating responsiveness and a commitment to delivering value.

A comprehensive virtual collaboration platform directly addresses the challenges of distributed teams across multiple time zones. It integrates real-time communication (video conferencing, chat) for synchronous interactions and asynchronous tools (shared documents, discussion boards) for flexible updates. This holistic approach fosters immediate problem-solving, maintains team cohesion, and ensures all team members have access to the latest information and discussions regardless of their location or working hours.

EAC equals BAC divided by CPI, so $1,000,000 ÷ 0.85 = $1,176,471. Using the typical CPI assumption assumes remaining work continues at the same cost efficiency, directly reflecting the 0.85 cost performance index reported in the earned value analysis.

Having a formal meeting with the team member is the most appropriate first step, aligning with PMP principles of proactive performance management and clear communication. This allows the Project Manager to formally articulate the specific performance gap, reiterate project expectations, understand potential root causes from the team member's perspective, and collaboratively establish a corrective action plan. Documenting this discussion, including agreed-upon actions and potential consequences for continued non-compliance, is crucial for tracking progress and ensuring accountability.

This is the most appropriate first step, aligning with PMP principles of managing team performance through proactive engagement and support. A private meeting allows for a confidential, non-confrontational discussion to understand the challenges, provide constructive feedback, and collaboratively identify solutions such as coaching, mentoring, or targeted training. This supportive approach fosters a positive team environment, demonstrates commitment to the team member's growth, and is most likely to result in improved performance.

This is the most appropriate and effective first step, demonstrating proactive stakeholder management and conflict resolution. A private meeting allows the project manager to respectfully engage the sponsor, understand their perspective, and reiterate the importance of adhering to established communication protocols. This direct, diplomatic approach facilitates a collaborative discussion to realign expectations and agree on a mutually acceptable communication channel, thereby preserving the professional relationship and maintaining project control.

A team charter is a foundational document created during the Plan Resource Management process. It defines team values, operating guidelines, communication protocols, and decision-making processes. By explicitly outlining norms for respectful communication and a structured approach to conflict resolution, it proactively establishes an inclusive environment, minimizing misunderstandings and fostering psychological safety for all diverse team members. This proactive approach is critical for effective team development and performance.

As an agile coach, the Project Manager's primary role is to facilitate and remove impediments, which includes improving team processes and capabilities. Coaching the Product Owner on crafting clear, testable acceptance criteria directly enhances the quality of user stories and reduces ambiguity for the development team. Simultaneously, empowering the self-organizing team to voice concerns during backlog refinement fosters proactive communication and shared understanding, addressing the root cause of potential issues before they impact sprint execution. This approach strengthens the team's autonomy and the Product Owner's effectiveness, aligning with agile principles.

When a previously identified risk event occurs, the project team's primary responsibility is to execute the specific, agreed-upon risk response strategy documented in the risk register. This proactive approach ensures that the project is prepared to mitigate threats or leverage opportunities, as these responses were developed and approved during the Plan Risk Responses process. Implementing the pre-planned response minimizes disruption and maintains project control, aligning with the Monitor Risks process.

As a Project Manager, your primary responsibility is to provide objective, data-driven information to project governance bodies, such as the steering committee, when a project's viability changes. Presenting an updated business case, reflecting current conditions, enables informed strategic decisions regarding project continuation, modification, or termination. Recommending a formal decision review ensures adherence to organizational governance frameworks and stakeholder alignment, preventing unilateral actions and promoting accountability. This approach empowers the appropriate authority to make a strategic choice based on the latest financial and market realities.

Time-boxing the Daily Scrum to 15 minutes is a core Scrum principle, ensuring the meeting remains concise and focused on immediate coordination for the next 24 hours. Utilizing a talking stick can further enhance this by enforcing a single speaker, promoting active listening, and preventing individuals from dominating the discussion or veering off-topic, thereby maintaining efficiency and adherence to the time-box.