PMP StudyPMP 2026: Structured study and 210 exercises

Learning goals

• In an invoice AI pilot, finance may prioritize avoiding incorrect payments while engineering prioritizes response time. Agree who decides exceptions and how quality and time are measured before acceptance.

Key points

• A shared direction explains whose outcomes matter, beyond a deliverables list. Translate conflicting departmental language into measurable outcomes and priorities. Revisit assumptions with the relevant decision makers when circumstances change.
• Identify whether disagreement concerns facts, relationships or decision procedures. Collaboration explores underlying interests for a joint solution. Urgent safety situations need protective action; ordinary disagreements should not automatically be delegated upward.
• Working agreements define observable collaboration and decision behavior. Psychological safety enables reporting concerns and mistakes without removing accountability or quality standards. Address violations through agreed behavior and observed impact.
• Match support to skill, experience and risk. Give experienced specialists clear outcomes and room to act; provide newcomers with staged practice and feedback. Removing impediments differs from doing all the team’s work.
• Separate outcome accountability, execution and decision authority. A responsibility matrix supports discussion but does not replace agreement. Compare skills and available capacity, then address gaps through development, allocation or external support.
• Stakeholders include operators, communities and partners affected by delivery, not just sponsor and users. Power, interest and impact change over time. Significant effects on low-power groups still require attention and appropriate engagement.
• Engagement is more than broadcasting updates. Give affected people suitable ways to influence decisions and follow through on commitments. Resistance can reflect losses or prior experience, so combine listening with evidence rather than assuming ignorance.
• Explore interests behind stated positions and compare feasible alternatives. Conflicting budget, timing and outcome expectations require authorized trade-offs. Assess impacts before making commitments rather than promising every request immediately.
• Expectations can change after initial agreement. Define testable acceptance conditions and compare demonstrations with real user experience. Conformance and customer value are related but distinct; new expectations need explicit change or priority decisions.
• Transfer decision context and experiential knowledge as well as documents. Make records findable, maintained and appropriately restricted. Knowledge sharing does not mean indiscriminate disclosure of confidential information.
• Mentoring develops perspective and judgment; coaching can help a learner find their own solution. Turnover requires transfer of relationships, authority, knowledge and open decisions. Confirm readiness with the incoming person rather than relying on introductions alone.
• Match recipient, purpose, urgency, channel, frequency and owner. Across time zones, combine asynchronous records with fair access to live discussion. Sending is not understanding; close the loop through feedback and decision readiness.

Workplace uses

• Workplace applicationIn an invoice AI pilot, finance may prioritize avoiding incorrect payments while engineering prioritizes response time. Agree who decides exceptions and how quality and time are measured before acceptance.

Learning topics mapped to ECO tasks (site curriculum)

• Shared direction and success criteria
• Diagnosing disagreements
• Working agreements and speaking up
• Situational leadership and coaching
• Roles, delegation and capability
• Discovering affected stakeholders
• Trust and meaningful involvement
• Reconciling expectations
• Customer feedback and acceptance
• Capturing reusable project knowledge
• Mentoring and continuity through turnover
• Distributed communication and reporting

Learning resources

• Examination scope reference ↗
• PMP exam guide / study guide ↗

Learning goals

• A rollout can retain a fixed approval gate while iterating on screens and prompts. Test small increments and retain required controls. CPI = EV/AC and SPI = EV/PV, but ratios alone do not establish root causes.

Key points

• Predictive work benefits from stable requirements and baselines; adaptive work uses feedback and reprioritization. Hybrid delivery needs explicit interfaces between fixed and exploratory work. Integrate scope, timing, resources, costs and quality to expose dependencies and conflicts.
• Elicit requirements from intended outcomes and connect rationale, ownership, acceptance and deliverables. Traceability supports impact analysis and test completeness. Use observation and prototypes as well as interviews so quieter users and implicit needs are represented.
• A WBS decomposes deliverables into manageable work packages and helps expose scope gaps and overlap. Scheduling determines sequence separately. Quality verification and formal acceptance serve related but different purposes.
• Priorities consider benefits, delay cost, risk, dependencies and learning cost. Deliver a useful small increment to test assumptions early. Financial comparisons such as NPV depend on assumptions and should be considered with strategic and mandatory constraints.
• Adaptive delivery refines work by value and clarifies iteration goals and completion conditions. Reviews inspect outcomes; retrospectives inspect ways of working. New requests during an iteration require discussion of goal impacts rather than unlimited work injection.
• Resource planning checks skills, quantities and availability. Leveling adjusts dates to capacity constraints and may extend completion. Smoothing normally uses available float without extending completion. Extra staff can also add coordination and learning effort.
• Fixed price, cost reimbursement and time-and-materials allocate uncertainty differently. Select based on scope clarity, market conditions, oversight and change terms. Fixed price does not remove the buyer’s acceptance, scope or dependency risks.
• After award, track outputs, payment, quality, timing and obligations. Address delays using evidence and terms rather than threats alone. Negotiations need authority, objectives and alternatives, followed by a formal record of agreement.
• State estimate scope, assumptions, accuracy and basis. Distinguish contingency for identified risks from management reserve for unforeseen work. Contingency normally belongs in the cost baseline, management reserve outside it; check authority before use.
• EV values completed work at budget rates, PV values planned work, and AC is actual cost. CPI=EV/AC and SPI=EV/PV; CV=EV−AC and SV=EV−PV. Forecast formulas depend on remaining-work assumptions; SPI alone does not determine calendar delay.
• Separate prevention, appraisal and internal/external failure costs. Improve causes rather than relying only on extra inspection. Pareto charts help prioritize, fishbones organize hypotheses, and control charts assess stability.
• Link tests to requirements, conditions, evidence and decision owners. After a fix, check the corrected behavior and relevant regression effects. Agree business scenarios for user acceptance and keep failures visible even near deadlines.
• Schedules combine dependencies, durations, resources and constraints. The longest dependent path controls completion; total float is usually LS−ES or LF−EF. Multiple critical paths and changing constraints mean speeding only noncritical work may not shorten completion.
• Three-point estimates make uncertainty visible. The PERT mean is (O+4M+P)/6. Crashing adds cost to reduce duration; fast tracking overlaps suitable work. Both require assessment of quality, feasibility and rework risk.
• WIP limits favor finishing rather than merely starting work. In a stable system, Little’s law relates average WIP, throughput and cycle time. Velocity uses team-specific estimation units and should not become a cross-team individual ranking.
• Align status dates, definitions and sources. Spending or starts alone do not demonstrate completion. Tailor artifacts and manage approved versions, history and access. Concealing unfavorable evidence prevents informed correction.
• Closure includes acceptance, contractual/financial reconciliation, knowledge transfer and resource release. Handover requires operational ownership, monitoring, support, recovery and training readiness, not just file transfer. Assign continuing benefit measurement explicitly.

Workplace uses

• Workplace applicationA rollout can retain a fixed approval gate while iterating on screens and prompts. Test small increments and retain required controls. CPI = EV/AC and SPI = EV/PV, but ratios alone do not establish root causes.

Learning topics mapped to ECO tasks (site curriculum)

• Choosing an approach and integrating plans
• Requirements and traceability
• Scope decomposition and acceptance
• Prioritizing outcomes and increments
• Backlogs and iterative feedback
• Resource allocation and leveling
• Sourcing and contract selection
• Supplier delivery and negotiation
• Estimates, budgets and reserves
• Earned value and forecast assumptions
• Quality costs and cause analysis
• Testing and user acceptance
• Dependency networks and critical paths
• Three-point estimates and compression
• WIP, flow and forecasting
• Status metrics and trustworthy records
• Closure and operational readiness

Learning resources

• Examination scope reference ↗
• PMP exam guide / study guide ↗

Learning goals

• Saving 20 review hours a month does not automatically create equivalent profit. Include human review and operating costs and validate how the freed capacity will be used.

Key points

• Governance defines who decides what and when escalation or approval is needed. Separate daily management from investment and strategic decisions, with explicit thresholds for scope, cost and benefits. Use organizational standards and preserve evidence and accountability.
• Apply responsibility, fairness, respect and honesty to decisions. Conflicts of interest concern impartiality, not just personal convenience; disclose and manage them through the appropriate process. Report unfavorable evidence accurately while protecting legitimate confidentiality.
• Identify applicable legal, contractual, safety and information-use obligations. Assign interpretation and evidence ownership. Calling an obligation an accepted risk does not satisfy it; assess changes with qualified owners and appropriate expertise.
• Consider operation, maintenance, disposal, resources and social impacts as well as purchase price. Compare consistent boundaries, periods and units, make trade-offs explicit, and verify environmental claims rather than relying on a label alone.
• Align change discovery, recording, impact analysis, authorization, implementation and plan updates. Predictive and adaptive systems use different control units but both need transparent effects on value and constraints. Informal assent is not automatically formal approval.
• Treat occurred events as issues, with owners, impacts, dates and action, rather than only probabilities. Determine whether an impediment is within the team’s authority and choose priority and escalation accordingly. Verify resolution and remaining impacts.
• Risk is uncertainty affecting objectives, including threats and opportunities. Separate causes, events and impacts; prioritize using probability, impact and relevant timing or detectability. Keep owners and responses connected and update as evidence changes.
• Choose responses such as avoidance, mitigation, transfer or acceptance for threats, and exploitation, enhancement, sharing or acceptance for opportunities. Track residual and response-created risks. Transfer does not eliminate all impact or monitoring responsibilities.
• Expected monetary value weights outcomes by probability. It helps compare repeated or portfolio choices but does not cap the loss on one project. Evaluate response cost, remaining exposure, tolerance and mandatory constraints together.
• Connect causes, response hypotheses and outcome measures. Test small changes and side effects, then update standards when evidence supports them. Assign actions and dates from retrospectives; holding the meeting is not the improvement itself.
• Change needs more than a launch announcement. Examine affected work, capability, roles, incentives and culture. Match training, support, participation and organizational adjustments to the causes of resistance, then track usage and outcomes.
• Monitor market, regulatory, technological and geopolitical changes and assess effects on benefits, scope and dependencies. Sunk spending does not justify future investment by itself; present continue, adapt or stop options to the appropriate decision maker.
• AI can assist drafting and analysis, but requires checks for purpose fit, data rights, errors, bias and monitoring. Generated suggestions do not replace evidence or authority. Assign human accountability and reassess after model or process changes.

Workplace uses

• Workplace applicationSaving 20 review hours a month does not automatically create equivalent profit. Include human review and operating costs and validate how the freed capacity will be used.

Learning topics mapped to ECO tasks (site curriculum)

• Decision rights and governance thresholds
• Ethics, conflicts of interest and truthful reporting
• Compliance requirements and evidence
• Sustainability across the life cycle
• Assessing and authorizing changes
• Active issues and impediments
• Identifying and prioritizing uncertainty
• Responses to threats and opportunities
• Expected values and decision uncertainty
• Improvement experiments and organizational learning
• Adoption, culture and organizational change
• External shifts and continued justification
• AI use, evidence and human decisions

Learning resources

• Examination scope reference ↗
• PMP exam guide / study guide ↗