Project Management Professional (PMP)® Examination Content Outline

C. Conduct a thorough analysis of the regulatory requirements and their impact on the project.

When critical, previously unaddressed requirements emerge, the project manager must first understand their nature and impact. A thorough analysis provides the necessary information to make informed decisions and effectively engage with stakeholders.

D. SPI = 0.83, CPI = 0.83

SPI = EV / PV. Since Work Package A is complete, EV = BAC for Work Package A = $200,000. PV = Planned Value, which is the value of work planned to be completed. If it took 12 weeks for 10 weeks of planned work, PV is still $200,000 because all planned work for WP A is now complete. So SPI = $200,000 / $200,000 = 1. Oh, wait. This is a common trick. For SPI, 'planned' refers to the *rate* or *duration* of planned work, not just the total budget. If it took 12 weeks to do 10 weeks of work, then the actual *rate* of progress is slower. SPI should be calculated based on the earned value (what was planned to be done) divided by the planned value (what was actually planned to be done by the actual time spent). For a completed work package, EV is the planned cost (BAC) of that package. The PV for the duration it actually took would be proportionally higher if the work was completed in more time. Let's re-evaluate based on standard definitions: EV = Earned Value, AC = Actual Cost, PV = Planned Value. SPI = EV / PV. CPI = EV / AC. For Work Package A: Planned Duration (PD) = 10 weeks, Planned Cost (PV_total) = US$200,000. Actual Duration (AD) = 12 weeks, Actual Cost (AC) = US$240,000. Since Work Package A is complete, the Earned Value (EV) for Work Package A is its total planned cost: EV = US$200,000. To calculate SPI, we need the Planned Value (PV) for the duration it actually took. The planned value for 12 weeks, if the work was planned to take 10 weeks for $200,000, is not simply $200,000. It's the budgeted cost for the work that was *scheduled* to be completed by the point in time the measurement is made. If the work was *planned* to be completed in 10 weeks for $200,000, and it took 12 weeks, then the PV for the *actual* duration of 12 weeks would technically be higher if we were looking at a point in time before completion. However, once a work package is *completed*, the EV is the BAC for that package, and the PV used for SPI is typically the BAC of the work that *should have been completed* by the reporting date. If the work package was planned to be finished by week 10, then by week 12, the PV for that work package is still its total planned value, $200,000, assuming it was meant to be 100% complete by week 10. Let's use the simplest and most common interpretation for a completed work package: EV = BAC (Budget at Completion for Work Package A) = US$200,000. PV = BAC (Budget at Completion for Work Package A) = US$200,000 (because the work was planned to be completed). AC = Actual Cost = US$240,000. SPI = EV / PV = US$200,000 / US$200,000 = 1.0. This can't be right if it took longer. The correct way to interpret SPI for a completed task that took longer than planned is: EV is the value of the work *actually performed* (which is the full planned value once completed), and PV is the value of the work that *should have been performed* by the actual completion time if it had stayed on schedule. Another way to think about it is: SPI = (Budgeted Cost of Work Performed) / (Budgeted Cost of Work Scheduled). If it took 12 weeks to do 10 weeks of work, then the work was performed at 10/12ths the planned rate relative to time spent. SPI = Planned Duration / Actual Duration = 10 weeks / 12 weeks = 0.833. CPI = EV / AC = US$200,000 / US$240,000 = 0.833. Therefore, SPI = 0.83 and CPI = 0.83.

A. Facilitate continuous communication and collaboration between the different teams/components to align requirements and dependencies.

In a hybrid environment, integrating different methodologies with their distinct approaches to requirements (fixed vs. evolving) is a significant challenge. The MOST critical integration activity is fostering continuous communication and collaboration. This enables teams to align their understanding, manage dependencies, and resolve discrepancies proactively, rather than relying solely on documentation or rigid processes.

B. Communicate the issue, its impact, and proposed solutions to relevant stakeholders.

After identifying an issue and analyzing its impact, the next critical step is to communicate this information to relevant stakeholders. This ensures transparency, allows for collaborative decision-making, and manages expectations.

B. Actively manage their expectations and ensure their requirements are met, involving them as needed.

For stakeholders with high influence but low interest (often categorized in a Power/Interest Grid as 'Keep Satisfied'), the most effective strategy is to actively manage their expectations and ensure their requirements are met. This involves engaging them strategically, not excessively, to maintain their satisfaction without overwhelming them or wasting their time, thereby leveraging their influence positively.

B. Archive all project documents and historical information.

Archiving all project documents and historical information is crucial for future reference, audits, and organizational learning. It ensures that valuable project data is not lost and can be used for future projects.

D. Conduct a lessons learned session with the project team and key stakeholders.

While all options are part of project closure, conducting a lessons learned session is crucial for organizational learning and continuous improvement. It captures valuable knowledge that can benefit future projects.

A. Exploit

Exploit is a strategy for positive risks (opportunities) where the organization seeks to eliminate the uncertainty associated with an opportunity to ensure it definitely happens. By investing in training and configuration for a tool that 'could significantly reduce deployment time,' the project manager is taking proactive steps to ensure the opportunity's realization.

B. Facilitate a discussion with stakeholders and the team to clarify compliance requirements and update the product backlog.

In an agile environment, addressing stakeholder concerns and ensuring compliance is critical. Clarifying requirements and updating the backlog allows the team to incorporate the necessary changes effectively and prevents similar issues in the future.

D. Prioritize the features collaboratively with stakeholders and manage the product backlog accordingly.

In agile projects, prioritizing features with stakeholders and managing the product backlog is crucial for delivering maximum value within constraints. This ensures that the most important features are developed first.

D. Establish clear communication protocols and utilize asynchronous and synchronous tools strategically.

For geographically dispersed teams with communication and coordination challenges, establishing clear communication protocols and strategically using both asynchronous (e.g., shared documents, forums) and synchronous (e.g., video conferencing) tools is crucial. This addresses scheduling conflicts and ensures effective information exchange.

B. Waterfall (Predictive)

Given a well-defined scope, stable requirements, and the goal of quick and efficient delivery, a Waterfall (predictive) methodology is often the most suitable. It allows for thorough upfront planning and sequential execution, which can be highly efficient when requirements are unlikely to change.

D. Analyze the feedback with the team and product owner to understand the usability issues and potential solutions.

User acceptance is crucial for successful system adoption. Even if functional requirements are met, usability issues can hinder project success. Analyzing the feedback with the team and product owner is the next logical step to understand the problem and determine if changes are necessary.

C. Integrate accessibility requirements into the project's planning, design, development, and testing phases.

Ensuring compliance, especially with strict regulations, is most effective when integrated throughout the entire project lifecycle. This 'build-in quality' approach prevents costly rework and ensures adherence from the outset, rather than trying to fix it at the end.

A. Submit a change request to formally assess the impact of the new regulation on the project's scope, schedule, and budget.

New regulations represent a significant change to the project's scope and requirements. The formal change control process, initiated by a change request, is the appropriate mechanism to evaluate the impact, get approval, and integrate these changes into the project baselines.

A. Develop a tailored communication plan that addresses the specific needs and engagement levels of different stakeholder groups.

Effective communication management involves tailoring communication to the specific needs of different stakeholders. A communication plan ensures that the right information is delivered to the right people, at the right time, and through the right channels.

A. A formal project status report.

A formal project status report is the most appropriate way to provide a comprehensive and structured update on budget, schedule, scope, issues, and risks to a project sponsor, especially in a predictive lifecycle. It ensures clarity, formality, and serves as a record.

D. Mitigate

Identifying an alternative supplier and establishing a backup contract is an action taken to reduce the probability or impact of a negative risk (threat). This falls under the 'Mitigate' risk response strategy.

C. CPI = 0.89, indicating the project is over budget.

The Cost Performance Index (CPI) is calculated as Earned Value (EV) divided by Actual Cost (AC). In this case, EV = US$250,000 and AC = US$280,000. So, CPI = 250,000 / 280,000 = 0.89. A CPI less than 1.0 indicates that the project is over budget, meaning it is getting less value for the money spent.

A. Agile (Scrum)

For projects with unknown technical challenges, evolving requirements, and the need for periodic working prototypes to gather feedback, an Agile (Scrum) methodology is most appropriate. It embraces change, allows for iterative development, and focuses on delivering value incrementally through short cycles.

B. Develop a project-specific data handling plan that explicitly addresses all regulatory compliance requirements.

When existing organizational processes are insufficient for critical project compliance needs, the project manager must proactively develop a project-specific plan. This ensures that the project meets all regulatory requirements, especially for sensitive areas like medical devices and data privacy, which can have severe consequences if not adhered to.

A. Work with the team to analyze the root cause of the defects and plan for their immediate resolution.

Critical defects identified during UAT require immediate attention. The most appropriate initial step is to work with the team to understand the root cause and plan for resolution, as these defects prevent the system from meeting core requirements.

C. A strong centralized Project Management Office (PMO) with clear authority over project standards and decisions.

For complex, high-risk projects involving multiple external parties and strict regulatory compliance, a strong, centralized PMO provides the necessary control, standardization, and oversight. This structure ensures consistent decision-making, adherence to standards, and effective management of risks and external dependencies.

C. Convene an urgent meeting with the project team and procurement to develop contingency plans and identify alternative solutions.

When an unanticipated risk occurs, the project manager's immediate priority is to assess the impact and work with the team to develop a response. Engaging procurement and the team to find alternative solutions is a proactive and collaborative approach to mitigate the damage.

B. Investigate the root cause of the extended curing time and assess its impact on the project schedule and cost.

When an issue arises, the first step is always to understand its nature and impact. Investigating the root cause provides the necessary information to develop an effective solution, rather than reacting without full understanding.