Free PMP Practice Test

According to PMI standards, the project manager must tailor the development approach to the project's specific characteristics. A "plan the work and work the plan" approach describes a predictive (waterfall) life cycle, which is only suitable when requirements are well understood and stable. Because the project manager has identified that the project objectives will undergo frequent changes, maintaining a predictive approach will result in excessive change control overhead, scope creep, and inefficiencies. An adaptive (change-driven or agile) life cycle is explicitly designed to accommodate high levels of change, complexity, and uncertainty. Therefore, the project manager should proactively propose switching to a change-driven approach to the PMO to ensure the methodology aligns with the project's dynamic nature.

A. Relying on a predictive change control process for frequent changes creates excessive administrative burden and delays, failing to address the root misalignment of the project life cycle.
B. The project manager is responsible for determining and recommending the appropriate development approach based on project characteristics, rather than passively seeking the client's opinion on a misaligned plan.
D. "Dynamic backlog reduction style" is a fabricated distractor term and is not a recognized project management methodology or life cycle within PMI standards.

1. Project Management Institute (PMI). (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 1.2.4.1 (Development Life Cycles)

p. 19. (Defines predictive vs. adaptive/change-driven life cycles and their appropriate use cases).

2. Project Management Institute (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 2.3 (Development Approach and Life Cycle Performance Domain)

pp. 32-38. (Discusses tailoring the development approach based on the degree of certainty and rate of change).

3. Project Management Institute (PMI). (2017). Agile Practice Guide. Section 3.1 (Characteristics of Project Life Cycles)

Table 3-1

p. 18. (Contrasts predictive and agile approaches

explicitly stating agile is designed for projects with frequent changes and high uncertainty).

In project management, particularly within highly regulated environments like healthcare, regulatory compliance is a continuous obligation rather than a one-time event. The project manager must proactively manage regulatory bodies' requirements by conducting regular compliance reviews and documenting ongoing compliance throughout the project lifecycle. This aligns with PMI's quality and governance principles, ensuring that project deliverables consistently meet legal and regulatory standards. Continuous monitoring and documentation prevent costly rework, mitigate legal risks, and satisfy high-power stakeholders (such as regulatory bodies) by providing verifiable proof that the project adheres to mandated health record standards.

A: The project manager is ultimately accountable for project requirements and compliance; delegating this entirely to the legal department abdicates core project management responsibilities. C: Reporting regulatory concerns only at project closure is too late; compliance must be monitored, documented, and addressed continuously to prevent project failure or severe legal penalties. D: Providing only preliminary reports is insufficient; managing regulatory requirements demands ongoing, systematic compliance reviews and continuous documentation throughout the entire project execution phase.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.5 (Delivery Performance Domain), specifically addressing compliance and regulatory requirements, p. 89.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 8.2.2.5 (Quality Audits), detailing the need to verify compliance with organizational and regulatory policies, p. 294.

3. Project Management Institute. (2016). Governance of Portfolios, Programs, and Projects: A Practice Guide. Section 3.3 (Governance Domains - Compliance), emphasizing continuous monitoring and documentation of regulatory adherence, pp. 45-46.

According to official PMI standards, a Team Charter (also referred to as a Project Team Charter or Social Contract/Working Agreement) is the formal mechanism used to establish team values, agreements, operating guidelines, and clear behavioral expectations. While the Project Charter formally authorizes the project and high-level objectives, it does not govern team interactions or internal ground rules. When working with cross-departmental stakeholders who must collaborate directly, developing a team charter through structured alignment meetings secures explicit consensus on operating norms, roles and responsibilities, conflict resolution processes, meeting cadences, and behavioral ground rules.

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

Section 2.2 (Project Team), p. 19 (Defines the Project Team Charter as the artifact recording values, agreements, operating guidelines, and acceptable behavior expectations).

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

Section 9.1.3.2 (Team Charter), pp. 319–320 (Details the components: team values, communication guidelines, decision-making criteria, conflict resolution, meeting guidelines, and ground rules).

Project Management Institute (PMI) & Agile Alliance. Agile Practice Guide.

Section 5.1 (Charter the Project and the Team), pp. 49–50 (Covers team charters, working agreements, and establishing ground rules to resolve conflicting priorities and build collective buy-in).

Project Management Institute (PMI). Process Groups: A Practice Guide

Section 5.9 (Plan Resource Management), pp. 165–168 (Identifies the Team Charter as the primary tool to set clear expectations and minimize organizational friction across functional silos).

Academic Journal: Mathieu, J. E., & Rapp, T. L. (2009). Laying the foundation for successful team performance: Connecting early team charters, team mental models, and performance trajectories. Journal of Applied Psychology, 94(1), 90–103.

https://doi.org/10.1037/a0013257 (Demonstrates empirical evidence on the role of formal team charters in aligning operational expectations, behavioral norms, and project performance).

According to PMI principles, when a project manager encounters a new constraint, risk, or regulatory change, the immediate next step is to assess and evaluate its impact before taking any formal action. Because the change involves complex regulatory policies regarding data storage and processing, the project manager must consult with subject matter experts (compliance experts) to accurately determine how the policy affects the project. Only after this expert evaluation is complete can the project manager formulate a response, submit a formal change request, or update project baselines and documents. Acting without expert assessment risks implementing incorrect or non-compliant changes.

Option A: Reevaluating the scope and WBS is premature; the project manager must first understand the specific impact of the regulation by consulting experts before planning changes.
Option C: Informing the sponsor and reviewing the budget should only occur after the project manager has assessed the actual impact and formulated a potential response strategy.
Option D: Updating the project scope directly bypasses the Perform Integrated Change Control process and is premature without a thorough impact assessment.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 4.6 (Perform Integrated Change Control), pp. 113-115. (Details the necessity of assessing the impact of a change before updating baselines).

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 11.3.2.1 (Expert Judgment), p. 422. (Highlights the use of subject matter experts to evaluate risks and regulatory compliance impacts).

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.8 (Navigating Complexity), p. 90. (Discusses consulting experts to navigate complex project environments, such as new regulatory policies).

In iterative and agile projects, the most effective way to manage high complexity and overcome stakeholder hesitation is by delivering tangible value early and often. By ensuring early iterations deliver "early wins" (working, tested features that incorporate some of the complex business rules), the project manager demonstrates the team's capability and the viability of the product. This empirical approach builds stakeholder trust and credibility far more effectively than theoretical plans or past successes. It directly addresses the stakeholders' specific concerns about the current product's complexity while simultaneously reducing project risk through early feedback loops.

A: Seeking advice is a good general practice but does not provide the tangible proof needed to alleviate stakeholder concerns about this specific product's complexity. B: Devising a theoretical plan to build credibility does not demonstrate actual capability; iterative frameworks rely on empirical evidence and working deliverables to build trust. C: Presenting past projects does not prove the team can successfully navigate the unique, high complexity and specific business rules of the current innovative product.

1. Project Management Institute (PMI). Agile Practice Guide. (2017). Section 3.1.1 (Iterative Life Cycles), p. 14; Section 4.3.2 (Frequent Delivery), p. 44. (Details how frequent, early delivery of working increments builds stakeholder trust and manages high-uncertainty/complex work).

2. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. (2021). Section 2.3.4 (Delivery on the Cadence), p. 46; Section 2.1.1 (Stakeholder Engagement), p. 11. (Explains how delivering early wins and value on a regular cadence fosters stakeholder confidence and mitigates complexity risks).

To increase the accuracy of predictive models for cost estimation, such as analogous or parametric estimating, the historical data used must be highly relevant and comparable to the current project. According to PMI standards, these estimating techniques rely heavily on historical information from projects with similar parameters, scope, and complexity. Using data from projects with similar parameters ensures that the underlying variables driving costs are aligned, thereby improving the reliability and validity of the cost overrun predictions. Including dissimilar projects would skew the statistical model and reduce its predictive accuracy.

A. Including public domain projects introduces external variables, such as different organizational cultures, resource rates, and accounting methods, which can distort the model and reduce accuracy.
B. Projects still in progress lack final, actual cost data, making them incomplete and unreliable for accurately modeling final cost overruns.
C. Using only successful projects introduces survivorship bias, eliminating the very data (projects with actual cost overruns) needed to accurately model overrun scenarios.

1. Project Management Institute (PMI). (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 7.2.2.2 Analogous Estimating (p. 244) and Section 7.2.2.3 Parametric Estimating (p. 244). (Specifies that estimating is most reliable when previous activities are similar in fact and not just in appearance).

2. Project Management Institute (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 2.4.3 Estimating (p. 55). (Discusses the reliance on historical data and comparable project parameters for accurate forecasting).

According to PMI standards, when a new risk is identified during project execution, the project manager must first document it in the risk register and facilitate a structured analysis to determine its probability and impact. Skipping analysis to appease a sponsor's demand for speed or relying on a majority vote violates the standard risk management process. By assessing the risk's characteristics and root causes collaboratively, the project manager ensures that any subsequent response strategy (mitigate, accept, monitor) aligns with the project's approved risk thresholds and constraints, enabling an evidence-based decision.

Option A: Implementing mitigation without formal analysis bypasses the risk management plan and fails to evaluate the actual probability, impact, or cost-effectiveness of the response.
Option C: Assuming a newly discovered risk is implicitly accepted is incorrect; all new risks must be formally documented, analyzed, and managed throughout the project lifecycle.
Option D: Escalating to the sponsor without first analyzing the risk and formulating recommendations abdicates the project manager's responsibility to manage project risks effectively.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.8 (Uncertainty Performance Domain), pp. 119-122. (Details the necessity of evaluating threats and opportunities continuously throughout the project lifecycle).

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 11.3 (Perform Qualitative Risk Analysis), pp. 419-427. (Specifies the process of prioritizing individual project risks for further analysis or action by assessing their probability of occurrence and impact).

3. Project Management Institute. (2009). Practice Standard for Project Risk Management. Chapter 6 (Perform Qualitative Risk Analysis), pp. 27-32. (Provides the framework for structured risk assessment and decision-making based on organizational thresholds).

In a functional organization, the functional manager controls resources, performance evaluations, and reporting lines, leaving the project manager with little to no formal authority. To prevent team disengagement following the transition from a projectized structure, the project manager must rely on influencing and negotiating skills. By collaborating with the functional manager to integrate project-specific goals into the team members' formal performance evaluations, the project manager ensures that project work remains a recognized and rewarded priority. This alignment of project objectives with the new functional reporting structure maintains team motivation and accountability, directly addressing the risk of disengagement caused by the loss of direct project manager authority.

B. Requesting additional resources does not address the root cause of the current team's potential disengagement or lack of motivation due to the new reporting structure.
C. While updating the resource management plan is a necessary administrative task, it is a passive documentation update that does not proactively solve the human resource engagement issue.
D. Claiming the changes are transparent (unnoticeable) is factually incorrect and dismissive; the shift to a functional structure significantly impacts the team's reporting and evaluation processes.

1. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 2.4.4 "Organizational Structure Types" and Table 2-1 (Influence of Organizational Structures on Projects), pp. 47-48. (Details the shift in PM authority and resource control from Projectized to Functional structures).

2. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 9.5.2.2 "Project Performance Appraisals", p. 348. (Highlights the necessity of the PM communicating with functional managers to ensure proper feedback and goal alignment for team members).

3. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.2 "Team Performance Domain", pp. 16-19. (Emphasizes the importance of shared ownership, motivation, and aligning individual goals with project outcomes).

The Cost Performance Index (CPI) measures the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost.

• Given:
• Planned Value (PV) = $500,000
• Earned Value (EV) = $400,000
• Actual Cost (AC) = $420,000
• Formula:
• CPI = EV \ AC
• Calculation:
• CPI = $400,000 \ $420,000 approx 0.9524

Standard EVM rounding conventions round indices to two decimal places, yielding 0.95. Planned Value (PV) represents baseline work scheduled and is extraneous to the CPI calculation (it is used to derive schedule metrics like SPI = EV \ PV. A CPI of 0.95 indicates that the project is currently over budget, generating $0.95 of work value for every $1.00 spent.

Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 7.4.2.2 "Control Costs: Data Analysis (Earned Value Analysis)", Table 7-1 "Earned Value Calculations Summary Table", p. 267.

Project Management Institute. Practice Standard for Earned Value Management. Chapter 4 "EVM Analysis", Section 4.3.1 "Cost Performance Index (CPI)", pp. 27–28.

Project Management Institute (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 2.7 "Measurement Performance Domain", Subsection 2.7.4.1 "Earned Value Analysis", pp. 100–101.

Anbari, F. T. (2003). "Earned Value Project Management Method and Extensions." IEEE Transactions on Engineering Management, 50(1), pp. 12–23. DOI: 10.1109/TEM.2002.808208

Christensen, D. S. (1998). "The Cost Performance Index - An Early Indicator of Final Cost." Project Management Journal, 29(2), pp. 24–30. DOI: 10.1177/875697289802900205

In PMI methodology, evaluating and documenting vendor performance is a critical activity during the Control Procurements process. By documenting the vendors' performance regarding quality, delivery time, and overall compliance, the project manager updates the Organizational Process Assets (OPAs). These updated OPAs, specifically vendor performance evaluations and lessons learned registers, become invaluable inputs for future projects during the Plan Procurement Management process. This historical data allows future project managers to make informed decisions, select high-performing vendors, and proactively mitigate risks associated with poor quality or delayed delivery, directly addressing the variance experienced in the current project.

Option A: Negotiating future prices is premature without a defined future project scope and does not address the historical quality and performance risks.
Option C: Updating contact information is a basic administrative task that fails to capture the critical performance data needed to mitigate future quality risks.
Option D: Demanding better future performance without an active contract is ineffective; internal documentation (OPAs) is the standard PMI method to guide future vendor selection.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 12.3.3.3 Organizational Process Assets Updates (Vendor performance evaluation documentation), pp. 499-500.

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 2.8.2.4 Procurement (Procurement closure and performance reviews), p. 75.