PMP 2026 Cheat Sheet

Last revised: September 28, 2026

Cheat sheet for the current PMI Project Management Professional (PMP) exam: lifecycle choices, roles, artifacts, formulas, and exam traps.

Use the tables for a quick pre-exam check. Expand a topic’s notes for explanations, examples, and additional distinctions.

Scope and study context

PMP questions often ask what the project manager, product owner, servant leader, sponsor, or team should do next. The best answer is usually the one that:

Protects business value and project objectives.
Follows the agreed governance approach.
Uses collaboration before escalation.
Assesses impact before acting.
Respects the delivery approach: predictive, agile, or hybrid.
Addresses root causes, not only symptoms.
Maintains transparency with stakeholders.

PMP Scenario Mindset

If the question says…	Think first	Usually avoid
“What should the project manager do first?”	Assess, review relevant artifact, consult team/stakeholders	Immediately escalate, replace people, approve change alone
“A stakeholder requests a change”	Log/evaluate the change; use change control if baseline is affected	Implementing without impact analysis
“An agile team receives a new feature request”	Product owner evaluates and prioritizes backlog	Forcing a fixed-scope change process unless governance requires it
“Team conflict occurs”	Facilitate discussion, identify root cause, collaborate	Punishment, avoidance, escalation as first step
“A risk occurs”	If identified, execute planned response; if not, create workaround and update records	Ignoring because it was not in the plan
“Performance is behind schedule”	Analyze causes and options; use approved compression or adaptive reprioritization	Adding people automatically
“Customer rejects deliverable”	Clarify acceptance criteria, validate scope/control quality distinction	Blaming customer or bypassing acceptance process
“Vendor problem occurs”	Review contract, procurement documents, and escalation path	Informal side agreements that bypass contract terms
“Regulatory, safety, or ethical concern”	Act transparently and responsibly; follow required reporting path	Concealment, shortcuts, retaliation

Delivery Approach Selector

Approach	Best fit	Planning style	Change handling	Team/customer interaction	Exam cues
Predictive	Stable requirements, known technology, regulated or contract-heavy work	Detailed upfront planning and baselines	Formal change control after baselines	Periodic reviews, phase gates, sign-offs	WBS, baselines, change control board, critical path
Agile	Evolving requirements, high uncertainty, need for frequent feedback	Adaptive planning, iterative/incremental delivery	Product backlog reprioritization	Continuous collaboration, frequent demos	Sprints, backlog, product owner, velocity, servant leadership
Hybrid	Some stable components and some adaptive components	Mix of upfront roadmap and iterative elaboration	Formal governance for fixed elements; backlog for adaptive elements	Combined phase gates and iterative feedback	Hardware plus software, fixed compliance needs with evolving features
Incremental	Deliver usable portions progressively	Release-focused	Future increments can change	Feedback after each increment	MVP, releases, value delivery
Iterative	Refine solution through repeated cycles	Learning-focused	Design evolves through feedback	Frequent inspection and adaptation	Prototypes, uncertainty, discovery
Lean/Kanban	Flow efficiency, operational or service work	Continuous prioritization	Pull-based flow; WIP limits	Visual workflow and bottleneck management	Cycle time, throughput, Kanban board, WIP

“What Should the Manager Do Next?” Decision Table

Situation	Best next action	Why
New issue appears	Analyze impact, document, engage appropriate people	PMP favors informed action
Stakeholder is unhappy	Meet to understand concern and expectations	Manage engagement before escalation
Sponsor asks for extra scope	Document request and assess impact	Sponsor authority does not bypass governance
Team member lacks skill	Coach, train, pair, or remove impediment	Servant leadership and team development
Functional manager pulls a resource	Discuss impact, negotiate, update plans if needed	PM manages constraints and relationships
Critical vendor delay	Review contract, assess schedule impact, discuss recovery options	Procurement terms matter
Agile team cannot finish sprint work	Facilitate team discussion; product owner may adjust scope	Team owns sprint plan; PO owns priority
Customer wants early value	Consider MVP, phased release, or backlog reprioritization	Value delivery over rigid output
Defect found before delivery	Follow quality process, fix root cause, update lessons learned	Prevention and continuous improvement
Risk trigger occurs	Execute risk response plan	Risk planning is actionable
Unknown risk becomes issue	Implement workaround, update issue/risk records	Unplanned risks need active management
Stakeholder bypasses PM and directs team	Clarify communication and decision paths	Protects team focus and governance
Ethical concern	Gather facts, act honestly, report through proper channels	PMI ethics emphasize responsibility, fairness, honesty, respect

Role Reference

Role	Primary responsibility	High-yield distinction
Project manager	Integrates work, stakeholders, constraints, risks, delivery approach	Does not make every technical or product decision alone
Sponsor	Provides authority, funding, strategic direction, escalation support	Owns business need and major approvals
Product owner	Maximizes product value and prioritizes product backlog	In agile, owns “what” and priority, not “how”
Scrum master / agile lead	Servant leader, removes impediments, coaches agile practices	Does not assign tasks command-and-control style
Project team	Performs work, estimates, self-organizes where appropriate	Cross-functional ownership is key in agile
Customer/user	Defines needs, provides feedback, accepts value	Acceptance criteria matter
PMO	Provides standards, governance, support, methods, or direct control depending on type	PMO authority varies by organization
Functional manager	Manages department resources and technical staff assignments	Common source of matrix conflict
Change control board	Reviews and approves/rejects significant changes in governed environments	Not used for every agile backlog reorder unless required
Business analyst	Elicits, analyzes, and manages requirements	Helps bridge stakeholder needs and solution requirements
Procurement officer/legal support	Supports contracting, compliance, claims, and seller management	PM should not ignore procurement process

Lifecycle and Process Flow

Stage / Process group concept	Main purpose	Common artifacts	PMP trap
Initiating	Authorize project or phase; identify key stakeholders	Business case, benefits documents, project charter, stakeholder register	Starting execution before charter/authorization
Planning	Define scope, approach, baselines, governance, risk responses	Management plans, scope baseline, schedule, budget, risk register	Treating the plan as static rather than progressively elaborated
Executing	Perform work and manage people, communications, quality, procurements	Deliverables, team assessments, issue log, work performance data	PM doing all work instead of enabling the team
Monitoring and controlling	Compare performance to plan; manage changes and variances	Work performance reports, change requests, forecasts	Skipping impact analysis
Closing	Confirm completion, transition deliverables, close contracts, capture learning	Accepted deliverables, final report, lessons learned, archived records	Forgetting formal acceptance and knowledge transfer

Predictive Artifact Map

Artifact	What it answers	Use when	Do not confuse with
Business case	Why should the organization invest?	Project selection and justification	Project charter
Benefits management plan	How and when benefits will be realized	Value tracking beyond delivery	Schedule baseline
Project charter	Who authorizes the project and PM?	Initiation	Detailed project management plan
Project management plan	How the project will be managed	Integrated planning	A single schedule file
Scope statement	What is included/excluded?	Scope definition	Requirements documentation
WBS	How is scope decomposed into deliverables/work packages?	Planning and control	Activity list
WBS dictionary	Details for WBS components	Clarifying work packages	Requirements traceability matrix
Requirements traceability matrix	How requirements map to deliverables/tests	Managing requirement changes	Stakeholder register
Schedule baseline	Approved schedule model	Measuring schedule variance	Preliminary timeline
Cost baseline	Approved time-phased budget excluding management reserve	Cost control	Total project funding
Risk register	Individual risks and responses	Risk management	Issue log
Issue log	Current problems requiring action	Execution/control	Risk register
Change log	Status of change requests	Integrated change control	Backlog
Lessons learned register	Learning captured during project	Continuous improvement	Final retrospective only
Stakeholder engagement plan	Desired engagement strategies	Stakeholder management	Communications management plan
Communications management plan	Who gets what information, when, how	Information flow	Stakeholder analysis itself

Agile and Hybrid Artifact Map

Artifact / concept	Purpose	Exam note
Product vision	Shared direction for product value	Aligns backlog decisions
Product roadmap	High-level expected evolution	Less detailed than release/sprint plan
Product backlog	Ordered list of product work	Product owner prioritizes
Sprint backlog	Work selected for current sprint	Development team owns execution
Increment	Potentially releasable product outcome	Must meet definition of done
Definition of done	Shared quality/completion standard	Prevents hidden unfinished work
Definition of ready	Optional readiness criteria for backlog items	Helps avoid sprint churn
MVP	Smallest useful release to validate value	Not low quality; it is minimal viable value
Burnup chart	Work completed vs total scope	Shows scope changes clearly
Burndown chart	Remaining work over time	Useful for sprint/release tracking
Cumulative flow diagram	Flow, WIP, bottlenecks	Kanban/flow-oriented
Information radiator	Visible project/team information	Promotes transparency
Retrospective action items	Improvement experiments	Should be acted on, not merely recorded

Integrated Change Control

Use formal integrated change control when a requested change affects approved baselines, constraints, contracts, or governance commitments.

    flowchart TD
	    A[Change request received] --> B[Document request]
	    B --> C[Assess impact on scope, schedule, cost, quality, risk, resources, procurement, stakeholders]
	    C --> D{Baseline or governance impact?}
	    D -- No --> E[Handle within team authority and update records]
	    D -- Yes --> F[Submit to change control process]
	    F --> G{Approved?}
	    G -- Yes --> H[Update baselines/plans and communicate]
	    G -- No --> I[Record decision and communicate]
	    H --> J[Implement and monitor]
	    I --> J

Notes and examples

Change scenario	Predictive response	Agile/adaptive response
Customer requests new feature	Log change, impact analysis, CCB/approval if baseline affected	Product owner evaluates and orders backlog
Defect against accepted criteria	Corrective action; may not be scope change	Fix according to definition of done/quality policy
Regulatory requirement changes	Analyze mandatory impact; seek approval and replan	Reprioritize backlog and adapt release plan
Team discovers better technical approach	Assess impact; may be preventive/corrective change	Team may adapt design if product goals and standards remain met
Sponsor demands faster finish	Analyze options: crashing, fast tracking, descoping, phased delivery	Reprioritize for highest value; consider MVP/release slicing

Scope, Requirements, and Acceptance

Concept	Definition	Exam distinction
Requirement	Condition or capability needed by stakeholder/product	Must be elicited, analyzed, prioritized, and traced
Scope	Work and deliverables required to meet objectives	Product scope plus project work
Product scope	Features/functions of product/service/result	Validated by customer/user needs
Project scope	Work required to deliver product scope	Managed through WBS in predictive work
Acceptance criteria	Conditions deliverable must meet to be accepted	Prevents subjective acceptance disputes
Validate scope	Formal acceptance of completed deliverables	Customer/sponsor acceptance focus
Control quality	Check correctness of deliverables	Internal quality verification focus
Gold plating	Adding unrequested features	Usually wrong even if intended to please customer
Scope creep	Uncontrolled expansion of scope	Prevent through change control/backlog discipline

Schedule and Estimating Reference

Topic	Key points	Exam use
Rolling wave planning	Plan near-term work in detail, future work at higher level	Uncertain or long projects
Progressive elaboration	Continuously refine information as more is known	Not uncontrolled change
Decomposition	Break deliverables/work into smaller components	WBS and activity planning
Analogous estimating	Uses similar past projects; fast, less precise	Early estimates
Parametric estimating	Uses statistical relationship, e.g., cost per unit	Scalable when data is reliable
Three-point estimating	Optimistic, most likely, pessimistic	Uncertainty-aware estimates
Bottom-up estimating	Estimate detailed components then aggregate	More accurate, more effort
Critical path	Longest path through network; determines shortest project duration	Activities on critical path usually have zero total float
Total float	LS - ES or LF - EF	Delay allowed without delaying project finish
Free float	Delay allowed without delaying successor	More local than total float
Lead	Acceleration/overlap between activities	“Start successor 2 days before predecessor finishes”
Lag	Waiting time between activities	“Wait 3 days after concrete pour”
Fast tracking	Perform activities in parallel	Adds risk/rework
Crashing	Add resources to shorten duration	Adds cost; only works on compressible critical path work
Resource leveling	Adjust schedule to resource constraints	May change critical path/end date
Resource smoothing	Adjust within float	Does not change critical path/end date

Cost, Earned Value, and Forecasting Formulas

Formula	Meaning	Interpretation
EV = percent complete x BAC	Earned value	Budgeted value of completed work
PV	Planned value	Budgeted value of scheduled work
AC	Actual cost	Actual cost incurred
SV = EV - PV	Schedule variance	Positive = ahead; negative = behind
CV = EV - AC	Cost variance	Positive = under budget; negative = over budget
SPI = EV / PV	Schedule performance index	Greater than 1 = ahead; less than 1 = behind
CPI = EV / AC	Cost performance index	Greater than 1 = efficient; less than 1 = inefficient
EAC = BAC / CPI	Forecast if current cost efficiency continues	Common simple EAC
EAC = AC + ETC	Forecast using new estimate to complete	Use when original estimate is no longer valid
EAC = AC + (BAC - EV)	Future work expected at original rate	Past variance not expected to continue
EAC = AC + (BAC - EV) / (CPI x SPI)	Cost and schedule inefficiency both affect future	More conservative when both matter
ETC = EAC - AC	Estimate to complete	Expected remaining cost
VAC = BAC - EAC	Variance at completion	Positive = under budget
TCPI = (BAC - EV) / (BAC - AC)	Efficiency needed to meet BAC	If unrealistic, rebaseline/change may be needed
TCPI = (BAC - EV) / (EAC - AC)	Efficiency needed to meet EAC	Used against revised forecast
ROI = (benefit - cost) / cost	Return on investment	Higher is better
BCR = benefits / costs	Benefit-cost ratio	Greater than 1 generally favorable
PERT expected duration = (O + 4M + P) / 6	Weighted three-point estimate	Most likely estimate has highest weight
Standard deviation = (P - O) / 6	PERT uncertainty approximation	Larger means more uncertainty

Quality Reference

Concept	Meaning	PMP trap
Quality	Degree to which requirements are met	High grade is not the same as high quality
Grade	Category or rank of features	Low grade can still be high quality if requirements are met
Prevention	Build quality in	Preferred over inspection
Inspection	Find defects after work is done	Necessary but less efficient than prevention
Cost of conformance	Prevention and appraisal costs	Spending to avoid defects
Cost of nonconformance	Internal/external failure costs	Defects, rework, warranty, reputation loss
Quality assurance / manage quality	Process improvement and audit orientation	Focus on how work is performed
Quality control	Inspect/test deliverables	Focus on results
Accuracy	Closeness to true value	Different from precision
Precision	Repeatability/tight grouping	Can be precise but inaccurate
Control chart	Shows process stability over time	Out-of-control signals need investigation
Pareto chart	Prioritizes causes by frequency/impact	“Vital few”
Ishikawa/fishbone	Root cause analysis	Cause categories
Checksheet	Data collection tally	Not a trend chart
Scatter diagram	Relationship between variables	Correlation is not causation

Notes and examples

Quality management

Quality questions often distinguish prevention, inspection, process improvement, and customer acceptance.

Concept	Review point	Trap
Quality planning	Define standards and how to meet them	Waiting until testing to think about quality
Manage quality	Audit and improve processes	Confusing it with inspecting deliverables only
Control quality	Inspect/test deliverables and record results	Confusing it with formal customer acceptance
Validate scope	Customer/sponsor acceptance of deliverables	Not the same as control quality
Cost of quality	Prevention/appraisal plus failure costs	Ignoring prevention because it costs time
Continuous improvement	Improve process capability and reduce defects	Treating defects as isolated events only

Quality tool cues

Tool	Useful for
Cause-and-effect diagram	Root cause analysis
Pareto chart	Prioritizing major contributors
Control chart	Process stability over time
Histogram	Frequency distribution
Scatter diagram	Relationship between variables
Check sheet	Tallying occurrences
Flowchart	Understanding process steps
Audit	Checking process compliance and improvement opportunities

Best PMP answers often favor prevention over inspection and root cause analysis over blame.

Risk and Issue Reference

Item	Definition	Exam action
Risk	Uncertain event/condition that may affect objectives	Identify, analyze, plan responses
Issue	Current problem or event that has occurred	Assign owner, action, due date
Trigger	Warning sign that risk is about to occur	Execute response when trigger appears
Risk appetite	Organization’s general willingness to accept risk	Guides decisions
Risk threshold	Specific measurable limit	Escalate or act when exceeded
Risk register	Individual risks, owners, responses	Updated throughout project
Risk report	Overall risk exposure and trends	Useful for sponsor/governance
Residual risk	Risk remaining after response	May be accepted or further managed
Secondary risk	New risk caused by response	Add to risk register
Contingency reserve	For identified risks	Usually included in cost/schedule baseline
Management reserve	For unknown-unknowns	Controlled by management; not the cost baseline
Workaround	Response to an unplanned issue	Used when no planned response exists

Notes and examples

Risk Response Strategies

For threats	Meaning
Avoid	Eliminate threat or protect objective from impact
Mitigate	Reduce probability and/or impact
Transfer	Shift ownership/impact to third party, often contract/insurance
Accept	Take no proactive action beyond monitoring or reserves
Escalate	Move outside project authority to appropriate level

For opportunities	Meaning
Exploit	Ensure opportunity occurs
Enhance	Increase probability and/or impact
Share	Partner to capture opportunity
Accept	Take advantage if it occurs
Escalate	Move outside project authority

Risk and issue management

A risk is uncertain. An issue has occurred.

Topic	Quick review
Risk register	Documents risks, causes, probability/impact, owners, and responses
Risk owner	Person responsible for monitoring and response execution
Trigger	Warning sign that a risk may occur
Contingency plan	Planned response if a risk event occurs
Fallback plan	Backup if the primary response fails
Residual risk	Risk remaining after response
Secondary risk	New risk created by a response
Watchlist	Lower-priority risks monitored over time

Risk response strategies

Risk type	Strategy	Meaning
Threat	Avoid	Remove the threat or its cause
Threat	Mitigate	Reduce probability or impact
Threat	Transfer	Shift ownership/impact to another party, often contractually
Threat	Accept	Take no proactive action beyond monitoring or reserves
Threat	Escalate	Move outside project authority to appropriate level
Opportunity	Exploit	Ensure the opportunity happens
Opportunity	Enhance	Increase probability or benefit
Opportunity	Share	Partner to capture benefit
Opportunity	Accept	Take advantage if it occurs
Opportunity	Escalate	Move outside project authority to appropriate level

Risk traps

Treating an issue as if it were still a risk.
Ignoring positive risks/opportunities.
Choosing acceptance when mitigation is practical and valuable.
Failing to assign a risk owner.
Using management reserve casually instead of following governance.
Responding without updating the risk register or communicating impacts.

Stakeholder and Communications Reference

Concept	Purpose	Exam distinction
Identify stakeholders	Find people/groups affected by or able to affect project	Revisit throughout project
Stakeholder register	Stakeholder information and attributes	Sensitive; handle appropriately
Power/interest grid	Prioritize engagement effort	High power/high interest = manage closely
Engagement assessment matrix	Current vs desired engagement	Supports engagement planning
Communications management plan	Information needs, format, frequency, sender, receiver	Not all stakeholders need all details
Push communication	Sent to recipients	Email, memo; does not guarantee understanding
Pull communication	Recipient accesses as needed	Portal, repository
Interactive communication	Real-time exchange	Best for complex or sensitive topics
Communication channels	n(n - 1) / 2	More people means more complexity
Active listening	Confirm understanding	Essential for conflict and stakeholder resistance
Transparency	Make work/status visible	Especially high-yield in agile/hybrid

Notes and examples

Stakeholders and communication

Stakeholder questions usually test engagement, expectations, and communication discipline.

Topic	Quick review	Trap to avoid
Identify stakeholders	Find people/groups affected by or able to affect the project	Identifying only executives or only end users
Analyze stakeholders	Consider power, interest, influence, impact, and desired engagement	Treating all stakeholders the same
Engagement plan	Plan how to move stakeholders toward productive engagement	Communicating randomly or reactively
Manage expectations	Address concerns early and honestly	Hiding bad news
Monitor engagement	Reassess as the project changes	Assuming early stakeholder analysis stays valid
Communication plan	Defines who needs what information, when, how, and why	“More communication” is not always better

Communication methods

Method	Use when	Example
Interactive	Immediate feedback is needed	Meeting, workshop, call
Push	Information must be sent to recipients	Email, report, notification
Pull	Large audience accesses information as needed	Dashboard, repository, knowledge base

Communication channel count is often reviewed with:

\[ \text{Channels} = \frac{n(n-1)}{2} \]

If a new person joins, communication complexity increases; the answer may involve updating the communications management plan, not just adding another meeting.

Team, Leadership, and Conflict

Topic	PMP-preferred behavior
Servant leadership	Remove impediments, coach, enable team ownership
Psychological safety	Encourage candor, learning, and early problem disclosure
Empowerment	Let competent teams decide how to do the work
Motivation	Understand individual needs; use recognition appropriately
Coaching	Develop capability before replacing/escalating
Training	Close skill gaps proactively
Colocation / virtual collaboration	Choose communication methods that support team effectiveness
Conflict	Address early, privately when appropriate, and collaboratively
Negotiation	Seek win-win agreements where possible
Decision-making	Use data, team input, and governance authority
Diversity and inclusion	Leverage different perspectives; avoid bias

Notes and examples

Conflict technique	Use when	Caution
Collaborate/problem solve	Important issue, time available	Usually best long-term
Compromise/reconcile	Need acceptable middle ground	May not fully satisfy either side
Smooth/accommodate	Preserve relationship, low-stakes issue	Can leave root cause unresolved
Force/direct	Emergency or compliance need	Can damage commitment
Withdraw/avoid	Cooling-off or trivial issue	Usually weak if used to dodge real conflict

Procurement and Contract Types

Contract type	Buyer risk	Seller risk	Best fit
Firm fixed price (FFP)	Lower	Higher	Clear scope and stable requirements
Fixed price incentive fee (FPIF)	Low-medium	Medium	Cost/schedule incentives useful
Fixed price economic price adjustment (FP-EPA)	Medium	Medium	Long duration with inflation/price uncertainty
Cost plus fixed fee (CPFF)	Higher	Lower	Uncertain scope; seller fee fixed
Cost plus incentive fee (CPIF)	Medium-high	Medium	Shared cost targets/incentives
Cost plus award fee (CPAF)	Higher	Lower-medium	Subjective performance award criteria
Time and materials (T&M)	Medium-high	Medium	Staff augmentation or undefined level of effort

Notes and examples

Procurement situation	Best response
Seller misses milestone	Review contract, communicate formally, assess remedies
Scope ambiguity in contract	Clarify through procurement process; avoid informal expansion
Claim/dispute	Follow contract claims administration path
Need specialized skill temporarily	Consider T&M or staff augmentation if appropriate
Well-defined commodity purchase	Fixed price often fits
Build-or-buy decision	Compare internal capability, cost, risk, schedule, strategic value

Procurement and contracts

Procurement questions test whether you respect the contract, procurement process, and buyer/seller risk allocation.

Contract type	Basic idea	Risk tendency
Firm fixed price	Set price for defined work	More risk to seller if costs rise
Fixed price incentive fee	Fixed price with incentive terms	Shared performance motivation
Cost plus fixed fee	Reimburses allowable costs plus fixed fee	More cost risk to buyer
Cost plus incentive fee	Cost reimbursement with incentive formula	Shared cost/performance focus
Time and materials	Pay for time and materials used	Needs strong oversight to prevent cost growth

Procurement decision rules

If there is a seller dispute, review the contract and follow the claims/procurement process.
If scope is unclear, fixed price may be difficult or expensive because sellers price uncertainty.
If work is exploratory, cost-reimbursable or T&M may appear, but controls are important.
Do not bypass procurement policies because of schedule pressure.
Contract closure includes confirming work, resolving claims, finalizing payments, and archiving records.

Agile Events, Metrics, and Decision Points

Agile item	Purpose	Exam note
Sprint planning	Select sprint goal and work	Team forecasts work; PO clarifies priority
Daily standup	Inspect progress toward sprint goal	Not a status meeting for the PM
Sprint review	Demonstrate increment and get feedback	Stakeholder collaboration event
Retrospective	Improve process and teamwork	Actions should feed future work
Backlog refinement	Clarify, split, estimate upcoming work	Ongoing, not a one-time phase
Velocity	Amount of work completed per iteration	Planning aid, not a performance weapon
Cycle time	Time for one item to move through workflow	Flow efficiency
Lead time	Time from request to delivery	Customer-facing responsiveness
WIP limit	Caps work in progress	Exposes bottlenecks and improves flow
Story points	Relative size/complexity	Not directly comparable across teams
MoSCoW	Must, Should, Could, Won’t	Prioritization support
WSJF	Weighted shortest job first	Prioritizes high value/time-critical small jobs

Value, Benefits, and Product Thinking

Concept	What it helps decide
Business value	Whether work contributes to desired outcomes
Benefits realization	Whether delivered outputs produce expected benefits
MVP	What is the smallest useful release for learning/value?
Prioritization	What should be done first when capacity is limited?
Opportunity cost	What value is lost by choosing one option over another?
Product roadmap	How value may evolve over time
Release planning	When increments of value may be delivered
Feedback loop	Whether assumptions are valid
Pivot/persevere decision	Whether to change direction based on evidence

Tailoring Reference

Tailoring question	Consider
How much documentation is enough?	Risk, compliance, stakeholder needs, team size, complexity
How formal should change control be?	Baseline stability, contract terms, governance, regulatory impact
Which lifecycle fits?	Requirement certainty, technology uncertainty, delivery cadence, customer availability
How should stakeholders be engaged?	Power, interest, influence, impact, current vs desired engagement
How should progress be measured?	Predictive baselines, agile value increments, flow metrics, hybrid reporting
How should risk be managed?	Risk exposure, thresholds, organizational appetite
How much planning upfront?	Uncertainty level and cost of change
What governance is needed?	Organizational standards, sponsor needs, compliance, funding model

High-Yield Distinctions

Distinction	Know this
Corrective action vs preventive action	Corrective fixes current variance; preventive reduces chance of future variance
Defect repair vs change request	Defect repair fixes nonconformance; change request may alter baseline/scope
Validate scope vs control quality	Validate scope gets formal acceptance; control quality checks correctness
Issue vs risk	Issue has occurred; risk is uncertain
Risk audit vs risk review	Audit checks effectiveness of risk process; review updates risk status/exposure
Manage communications vs monitor communications	Manage distributes information; monitor ensures needs are met
Manage stakeholder engagement vs monitor stakeholder engagement	Manage works with stakeholders; monitor assesses relationships/strategies
Work performance data/information/reports	Data = raw observations; information = analyzed; reports = formatted for decisions
Leadership vs management	Leadership inspires/enables; management plans/controls
Product owner vs project manager	PO prioritizes product value; PM integrates project delivery/governance
Agile change vs predictive change	Agile reprioritizes backlog; predictive protects baselines through control
Lessons learned register vs repository	Register is active during project; repository is organizational archive

Common PMP Traps

Trap answer	Why it is usually wrong
Escalate immediately	PM should often analyze, collaborate, or attempt resolution first
Fire or replace a team member	Coaching and root-cause analysis usually come first
Accept stakeholder demand without review	Bypasses governance and impact analysis
Ignore a minor stakeholder	Stakeholders can gain influence or create risk
Add resources to a late project automatically	May increase cost/communication burden and not help critical path
Compress schedule without checking critical path	Non-critical activities may not improve finish date
Use agile to avoid planning	Agile still requires planning, prioritization, and discipline
Use predictive control for every agile backlog item	Adaptive work expects reprioritization
Gold plate to satisfy customer	Adds unauthorized scope and risk
Hide bad news until fixed	Violates transparency and can worsen impact
Measure agile teams by utilization only	Value, flow, quality, and outcomes matter
Treat retrospective as optional	Continuous improvement is central to adaptive delivery
Confuse sponsor with customer	Sponsor funds/champions; customer/user accepts or uses deliverable

Final Review Checklist

Before the exam, make sure you can quickly answer:

Is the scenario predictive, agile, or hybrid?
Is this a risk, issue, change request, defect, or stakeholder problem?
Which artifact should be reviewed or updated?
Who owns the decision: PM, sponsor, product owner, team, CCB, customer, or seller?
Should the next step be assess, facilitate, update, escalate, approve, or implement?
Does the answer preserve transparency, ethics, value, and governance?
Are scope, schedule, cost, quality, risk, resources, procurement, communications, and stakeholders considered before acting?
Would the best answer solve the root cause rather than the symptom?

Notes and examples

Quick final review checklist

Before a mock exam, confirm you can answer these without hesitation:

How do predictive and adaptive change handling differ?
When should a project manager escalate?
What is the difference between risk and issue?
Who prioritizes the product backlog?
What is the difference between a review and a retrospective?
What does CPI below 1 mean?
What does SPI below 1 mean?
When would you crash versus fast track?
What is the difference between control quality and validate scope?
How do you respond to stakeholder resistance?
What should happen before implementing a requested scope change?
How do you handle vendor disputes?
What makes an answer ethical, transparent, and fair?
How do business value and benefits influence project decisions?
What document or artifact should be updated after the action?

The PMP answer mindset

Most difficult PMP questions test judgment. A strong answer usually reflects these principles:

Scenario signal	Prefer	Avoid
Unclear facts	Assess, review documents, ask clarifying questions	Acting immediately without diagnosis
Conflict	Facilitate collaboration and root-cause problem solving	Escalating first or ignoring the issue
Change request in predictive work	Log, analyze impact, follow change control	Implementing because a stakeholder asked
New priority in adaptive work	Reprioritize through the product backlog and product owner/customer	Treating all change as formal baseline change
Risk	Identify, analyze, assign owner, plan response	Waiting until the risk becomes an issue
Stakeholder resistance	Analyze interest/influence, engage, communicate value	Replacing communication with authority
Team performance issue	Coach, remove impediments, build capability	Punish, blame, or micromanage
Vendor issue	Review contract, document facts, use procurement process	Informal side deals or ignoring contract terms
Compliance concern	Follow required governance and escalate appropriately	Prioritizing schedule over compliance
Ethical issue	Be honest, fair, responsible, and transparent	Concealing facts to protect the project

Notes and examples

A fast scenario-reading algorithm

Identify the delivery approach: predictive, adaptive, or hybrid.
Find the real problem: risk, issue, change, conflict, quality, stakeholder, procurement, compliance, or value alignment.
Notice the question wording: “first,” “next,” “best,” “should have done,” or “most likely.”
Use the right level of authority: team, project manager, product owner, sponsor, change control board, governance body, or procurement function.
Choose the proactive, ethical, value-focused answer.
Reject extreme answers: cancel, replace, escalate, accept, or implement without analysis unless the scenario clearly justifies it.

    flowchart TD
	    A[Read the scenario] --> B{Delivery approach clear?}
	    B -->|Predictive| C[Use baselines, plans, formal change control]
	    B -->|Adaptive| D[Use backlog, iteration goals, feedback loops]
	    B -->|Hybrid| E[Match the action to the affected component]
	    B -->|Not clear| F[Infer from terms: baseline vs backlog, phase vs iteration]
	    C --> G{What is the issue?}
	    D --> G
	    E --> G
	    F --> G
	    G --> H[Assess facts and root cause]
	    H --> I[Use the agreed process]
	    I --> J[Communicate and update records]
	    J --> K[Escalate only when appropriate]

Delivery approaches: predictive, adaptive, and hybrid

PMP questions often turn on whether the project is plan-driven, change-driven, or a mix.

Approach	Best fit	Key practices	Common exam trap
Predictive	Requirements are stable; scope can be defined early; compliance or contract constraints are strong	Charter, detailed planning, WBS, baselines, integrated change control, formal acceptance	Implementing changes without impact analysis and approval
Adaptive	Requirements evolve; frequent feedback is valuable; product discovery matters	Product backlog, iterations, increments, reviews, retrospectives, servant leadership	Assuming “agile” means no planning, no documentation, or no control
Hybrid	Some elements are fixed while others need iterative discovery	Predictive governance for fixed constraints plus adaptive delivery for evolving work	Applying one method blindly to the whole project

Notes and examples

Decision rules

If the question mentions baselines, change control board, WBS, or formal acceptance, think predictive control.
If it mentions backlog, iteration, sprint, product owner, increment, or retrospective, think adaptive delivery.
If a project has regulatory milestones but iterative product development, think hybrid: preserve required governance while allowing iterative learning.
Tailoring is central: the “right” method is the one that fits project complexity, uncertainty, risk, stakeholders, and organizational context.

Project integration: keep the whole project aligned

Integration is the project manager’s “connective tissue.” Many PMP scenarios are really integration questions.

Concept	Quick review	Exam decision point
Project charter	Formally authorizes the project and gives the project manager authority	If no authority exists, secure authorization rather than acting informally
Business case	Explains why the project is worth doing	If the project no longer supports value, raise it with sponsor/governance
Project management plan	Integrated plan plus subsidiary plans and baselines	Review the plan before taking process-driven action
Work performance data/information/reports	Raw observations become analyzed information and then reports	Do not confuse raw data with actionable reporting
Lessons learned	Captured throughout, not only at closing	Use prior lessons when planning or solving repeated issues
Change control	Evaluates impact before approving changes	Do not implement unapproved scope, schedule, or cost changes
Closure	Confirms acceptance, transitions deliverables, archives records, releases resources	Closure is more than “the work is finished”

Notes and examples

Change control in predictive work

A common PMP trap is choosing an answer that is too fast.

Document the change request.
Review the project management plan and change process.
Analyze impact on scope, schedule, cost, quality, risk, resources, procurement, and stakeholders.
Submit to the authorized decision process when required.
If approved, update baselines/plans and communicate.
If rejected, document the decision and continue with the approved plan.

Change in adaptive work

Adaptive work expects change, but not chaos.

Situation	Better answer
Stakeholder wants a new feature	Add/refine/prioritize it in the product backlog
Stakeholder wants to disrupt current iteration	Product owner and team evaluate impact; protect iteration goals unless change is justified
Customer feedback changes priorities	Reorder backlog based on value, risk, and learning
Team discovers technical debt	Make it visible, prioritize appropriately, and include it in planning
Scope is unclear	Use progressive elaboration, prototypes, spikes, or iterative feedback

People and leadership

PMP scenarios frequently test whether you lead through influence instead of command-and-control authority.

Team leadership essentials

Area	High-yield review	Best-answer pattern
Servant leadership	Remove impediments, support self-management, coach the team	Ask what the team needs; facilitate, do not dictate
Emotional intelligence	Understand emotions, motivations, conflict, and stakeholder concerns	Listen first, then respond deliberately
Psychological safety	Team members can raise problems without fear	Encourage transparency and learning
Conflict management	Conflict can be productive if handled well	Collaborate/problem-solve for durable resolution
Motivation	People need purpose, autonomy, mastery, recognition, and fair treatment	Address root causes, not just symptoms
Virtual teams	Need communication norms, trust building, and clear working agreements	Improve collaboration structure, not just meeting frequency
Team development	Skills, cohesion, and performance improve over time	Coach, train, mentor, and remove blockers

Notes and examples

Conflict techniques

Technique	When it may fit	PMP caution
Collaborate/problem-solve	Important issue; long-term solution needed	Usually the strongest answer when time allows
Compromise	Time pressure; both sides can give something	May not solve root cause
Smooth/accommodate	Preserve harmony on low-priority issue	Can hide real problems
Force/direct	Emergency, safety, or urgent decision	Often too authoritarian for normal scenarios
Withdraw/avoid	Cooling-off period or trivial issue	Weak if the conflict affects project performance

Common people-management traps

Escalating to the sponsor before speaking with the team.
Replacing a team member before coaching or understanding the issue.
Ignoring cultural, remote-work, or communication barriers.
Assuming conflict is always bad.
Treating agile teams as unmanaged teams.
Using the project manager’s authority when facilitation would work better.

Scope, schedule, and cost

Scope control

Concept	Meaning	Common confusion
Requirements	Stakeholder needs and conditions	Not the same as final scope baseline
Scope statement	Defines project/product scope and boundaries	Should clarify exclusions
WBS	Decomposes deliverables into manageable work	Not a schedule; not an org chart
Scope baseline	Approved scope statement, WBS, and WBS dictionary	Changes require control in predictive work
Validate scope	Formal acceptance of completed deliverables	Different from quality control
Control scope	Manage changes to scope baseline	Prevent scope creep

Notes and examples

Schedule review

Concept	Quick review	Exam cue
Dependency	Logical relationship between activities	Mandatory, discretionary, external, internal
Lead	Allows successor to start earlier	“Overlap” work
Lag	Delay between activities	Waiting period
Critical path	Longest path controlling project duration	Delays may delay the project
Float/slack	Time an activity can slip without affecting a target	Low or zero float means schedule sensitivity
Crashing	Add resources to shorten schedule	Usually increases cost
Fast tracking	Perform work in parallel	Usually increases risk/rework

Cost and earned value essentials

Term	Plain meaning
PV	Planned value: budgeted value of scheduled work
EV	Earned value: budgeted value of completed work
AC	Actual cost: money spent
BAC	Budget at completion
CV	Cost variance = EV - AC
SV	Schedule variance = EV - PV
CPI	Cost performance index = EV / AC
SPI	Schedule performance index = EV / PV
EAC	Estimate at completion
ETC	Estimate to complete
VAC	Variance at completion = BAC - EAC

Interpretation:

Metric	Favorable	Unfavorable
CV	Positive	Negative
SV	Positive	Negative
CPI	Greater than 1	Less than 1
SPI	Greater than 1	Less than 1

Common EAC logic:

Situation	Formula
Future work expected at original budget rate	EAC = AC + (BAC - EV)
Current cost performance expected to continue	EAC = BAC / CPI
Cost and schedule performance both affect remaining work	EAC = AC + (BAC - EV) / (CPI × SPI)
New bottom-up estimate for remaining work exists	EAC = AC + Bottom-up ETC

PERT expected duration:

\[ \text{Expected Duration} = \frac{O + 4M + P}{6} \]

Where \(O\) is optimistic, \(M\) is most likely, and \(P\) is pessimistic.

Agile and adaptive review

For adaptive scenarios, the exam often tests roles, prioritization, feedback, and servant leadership.

Agile roles and responsibilities

Role	Focus	Common trap
Product owner/customer representative	Product value, backlog ordering, acceptance priorities	Project manager unilaterally prioritizes product features
Scrum master/agile lead	Facilitation, process health, impediment removal	Acts as command-and-control manager
Development team/team members	Build and deliver increments	Waiting for detailed task assignments
Stakeholders	Provide feedback and business context	Bypassing the product owner or team agreements

Notes and examples

Agile artifacts and events

Item	Purpose
Product backlog	Ordered list of product work
Iteration/sprint backlog	Work selected for the iteration
Increment	Usable product output
Definition of done	Shared quality/completion standard
Product roadmap	Direction and sequencing of value
Release plan	Forecast of releasable capability
Daily standup	Coordination, impediments, near-term plan
Review/demo	Feedback on completed increment
Retrospective	Improve team process
Backlog refinement	Clarify, split, estimate, and reorder work

Agile metrics

Metric	Use	Caution
Velocity	Forecasting team capacity	Do not use as a weapon against the team
Burn-down chart	Remaining work trend	Not a complete value measure
Burn-up chart	Completed work and scope changes	Useful when scope changes
Cumulative flow diagram	Flow, bottlenecks, WIP	Look for widening bands
Cycle time	Time from work start to completion	Supports flow improvement
Lead time	Time from request to delivery	Useful for customer responsiveness

Adaptive traps

“Agile welcomes change” does not mean stakeholders can bypass prioritization.
The product owner prioritizes the backlog; the team decides how to do the work.
Retrospectives improve process; reviews gather product feedback.
A daily standup is not a status meeting for the project manager.
A high-performing agile team still needs goals, quality standards, and stakeholder alignment.
Hybrid projects may still require predictive reporting, compliance, or procurement controls.

Business environment, governance, and value

PMP questions increasingly emphasize value delivery and organizational context. Do not focus only on task completion.

Area	Review point	Best-answer pattern
Business value	Projects exist to create benefits	Reassess if expected value changes
Benefits realization	Benefits may occur after project delivery	Align outputs with intended outcomes
Governance	Decision rights, escalation paths, controls	Follow governance instead of improvising
Compliance	Regulatory, safety, security, or policy requirements	Never ignore compliance for convenience
Organizational change	Users must adopt the change for value to occur	Plan communication, training, and readiness
EEFs	External/internal conditions outside project control	Tailor approach to environment
OPAs	Organizational templates, processes, lessons, repositories	Use existing assets before reinventing

Notes and examples

When value is threatened

If the project’s business justification no longer appears valid:

Gather objective information.
Analyze impact on benefits, cost, schedule, risk, and stakeholders.
Communicate with the sponsor or appropriate governance body.
Recommend options.
Do not independently cancel or continue a misaligned project without governance involvement.

Ethics and professional responsibility

Ethics questions may be direct or hidden inside scenario wording.

Value	Practical exam behavior
Responsibility	Own decisions, follow policies, report issues appropriately
Respect	Listen, include stakeholders, manage conflict professionally
Fairness	Avoid favoritism, disclose conflicts of interest
Honesty	Provide truthful status, estimates, and risk information

Common ethical traps:

Hiding schedule or cost problems until they become unavoidable.
Sharing confidential information casually.
Accepting gifts or favors that create a conflict.
Manipulating metrics to make performance look better.
Blaming vendors, team members, or stakeholders without facts.

“First,” “next,” and “best” question strategy

Wording	What it usually tests	Strong answer pattern
What should the project manager do first?	Immediate professional response	Assess, review plan, identify root cause, or engage affected people
What should the project manager do next?	Correct sequence	Follow the defined process after the current step
What should the project manager have done?	Prevention	Plan, identify risks, engage stakeholders, define expectations earlier
What is the best action?	Judgment	Proactive, collaborative, ethical, value-focused solution
What should the agile lead do?	Servant leadership	Facilitate, coach, remove impediments, support team ownership
What should be updated?	Documentation discipline	Update the relevant plan, register, backlog, log, or baseline after the correct decision

High-yield keyword map

If the scenario says…	Think…
“A stakeholder requests an additional feature”	Change control or backlog prioritization
“The team is unsure who is responsible”	RACI/roles, team charter, communication
“A risk has occurred”	Issue management and contingency response
“A deliverable fails testing”	Control quality and root cause analysis
“Customer refuses acceptance”	Validate scope, acceptance criteria, requirements traceability
“Vendor deliverable is late”	Contract review, procurement process, risk/issue response
“Team members disagree on technical approach”	Facilitate collaboration and decision criteria
“Executive asks to skip a required step”	Governance, compliance, ethics
“Velocity is lower than expected”	Inspect causes, remove impediments, avoid blame
“Requirements are changing frequently”	Adaptive or hybrid approach, backlog refinement
“Project no longer supports strategy”	Business case/value review with sponsor/governance
“Many defects are found late”	Prevention, quality management, process improvement

Common candidate mistakes

Memorizing terms without scenario judgment PMP questions often ask what to do, not what a term means.
Escalating too early Escalation is appropriate when authority is exceeded, governance requires it, or prior steps fail. It is rarely the first move.
Ignoring the delivery approach Predictive change control and adaptive backlog management are not interchangeable.
Confusing quality control with scope validation Quality control checks correctness; validation obtains formal acceptance.
Treating all stakeholder problems as communication problems Sometimes the root issue is power, expectation mismatch, benefit concern, resistance, or poor engagement.
Assuming agile has no planning Agile planning is continuous and adaptive, not absent.
Choosing punitive team actions Coaching, facilitation, and impediment removal are usually better than blame.
Reading too fast Words such as “first,” “except,” “best,” “already approved,” and “newly identified” change the answer.
Overusing formulas without interpretation Know what CPI, SPI, CV, and SV mean in plain business language.
Forgetting documentation updates After decisions, update the appropriate register, log, plan, backlog, report, or baseline.

Review missed questions

Match an error to your next review step

Practice step	How to use it
Topic drills	Isolate weak areas such as agile roles, risk, EVM, change control, or stakeholder engagement
Mixed sets	Train yourself to identify the topic without being told
Mock exams	Build timing, stamina, and scenario judgment
Detailed explanations	Review why the right answer is right and why the distractors are wrong
Error log	Track misses by cause: concept gap, misread wording, wrong approach, or poor sequence
Retake strategy	Retake only after you can explain the reasoning, not after memorizing the answer

Put the review into practice

PM Mastery

Start Cheat Sheet practice on Web

Tip: Use the web app to preview question style, then practise the topics you need to revisit.

Use the web app for Cheat Sheet scenario practice, topic drills, timed mock exams, detailed explanations, and saved progress. Original PM Mastery practice only; not official questions, copied live-exam content, or exam dumps.

Current alignment Mapped to the current exam content outline, domains, tasks, learning outcomes, or syllabus areas for this exam.

Practice modes Use topic drills, timed mocks, scenario practice, and focused pages before deeper mixed practice.

Teaching explanations Explanations teach the project, agile, governance, or delivery rule that makes the best option stronger.

Stable bank Questions are prebuilt and reviewed before publication, so practice is stable and inspectable, not improvised during a quiz.

Study Plan

PMP 2026 Cheat Sheet

PMP Scenario Mindset

Delivery Approach Selector

“What Should the Manager Do Next?” Decision Table

Role Reference

Lifecycle and Process Flow

Predictive Artifact Map

Agile and Hybrid Artifact Map

Integrated Change Control

Scope, Requirements, and Acceptance

Schedule and Estimating Reference

Cost, Earned Value, and Forecasting Formulas

Quality Reference

Quality management

Quality tool cues

Risk and Issue Reference

Risk Response Strategies

Risk and issue management

Risk response strategies

Risk traps

Stakeholder and Communications Reference

Stakeholders and communication

Communication methods

Team, Leadership, and Conflict

Procurement and Contract Types

Procurement and contracts

Procurement decision rules

Agile Events, Metrics, and Decision Points

Value, Benefits, and Product Thinking

Tailoring Reference

High-Yield Distinctions

Common PMP Traps

Final Review Checklist

Quick final review checklist

The PMP answer mindset

A fast scenario-reading algorithm

Delivery approaches: predictive, adaptive, and hybrid

Decision rules

Project integration: keep the whole project aligned

Change control in predictive work

Change in adaptive work

People and leadership

Team leadership essentials

Conflict techniques

Common people-management traps

Scope, schedule, and cost

Scope control

Schedule review

Cost and earned value essentials

Agile and adaptive review

Agile roles and responsibilities

Agile artifacts and events

Agile metrics

Adaptive traps

Business environment, governance, and value

When value is threatened

Ethics and professional responsibility

“First,” “next,” and “best” question strategy

High-yield keyword map

Common candidate mistakes

Review missed questions

Put the review into practice

Browse Practice Tests & Interview Prep