PMP — PMI Project Management Professional Quick Reference

Last revised: June 29, 2026

Compact reference for PMI Project Management Professional (PMP) candidates: mindset, decision tables, artifacts, agile, risk, change, and formulas.

Quick Use and Exam Mindset

The PMI Project Management Professional (PMP), exam code PMP, tests project management judgment across predictive, agile, and hybrid contexts. Use this independent Quick Reference to review high-yield decisions, artifacts, formulas, and common traps before practice sets or a final review.

PMP questions often ask for the best next action. Prefer answers that assess first, follow governance, engage the right people, protect value, and avoid unilateral overreaction.

Situation in the question	Usually choose	Usually avoid
New problem appears	Analyze facts, identify root cause, consult plans/logs	Escalate immediately, blame, replace people
Stakeholder asks for scope change	Log and analyze change impact; follow change process	Implement informally or reject without analysis
Agile customer wants a new feature	Product owner prioritizes backlog; team discusses impact	PM directly inserts work into sprint
Team conflict	Facilitate collaboration/problem solving	Ignore it, force a decision as first response
Poor performance	Coach, remove impediments, train, clarify expectations	Fire or replace as the first action
Risk identified	Add to risk register, assess probability/impact, plan response	Treat as an issue before it occurs
Risk has occurred	Execute response/contingency; manage as issue if impacting work	Keep it only in the risk register
Quality defect found	Contain, root cause analysis, corrective action	Blame team or inspect quality only at the end
Compliance, safety, ethics concern	Act promptly, document, follow policy, escalate appropriately	Hide, delay, or handle informally
Sponsor asks for impossible date	Analyze options/tradeoffs and communicate impact	Accept without assessment

PMP Domain Lens

Do not study the PMP as a list of definitions only. Most questions combine people, process, and business environment judgment.

Lens	What to recognize	PMP-style response
People	Conflict, motivation, leadership, virtual teams, stakeholders	Use servant leadership, emotional intelligence, collaboration, coaching
Process	Scope, schedule, cost, risk, quality, procurement, change, delivery	Follow the plan, analyze impact, use appropriate artifacts and controls
Business environment	Benefits, compliance, strategy, value, organizational change	Align work to business value and benefits; escalate strategic conflicts
Predictive context	Baselines, formal change control, phase gates, detailed upfront planning	Protect approved baselines; use integrated change control
Agile context	Evolving scope, backlog, increments, customer collaboration	Prioritize value, empower the team, inspect and adapt
Hybrid context	Mixed governance and adaptive delivery	Tailor controls; know which parts are fixed and which are flexible

PMI-Style Principles That Shape Good Answers

Principle cue	What it means on the exam
Stewardship	Act ethically, responsibly, and transparently. Protect organizational and stakeholder interests.
Value	Tie decisions to outcomes and benefits, not just task completion.
Stakeholder engagement	Identify, analyze, and engage stakeholders continuously. Do not surprise key stakeholders.
Team empowerment	Let experts estimate and plan their work; remove impediments instead of micromanaging.
Tailoring	Choose predictive, agile, or hybrid practices based on context, not habit.
Systems thinking	Consider downstream effects across scope, schedule, cost, risk, quality, and benefits.
Quality built in	Prevent defects rather than relying only on inspection.
Adaptability and resilience	Inspect, learn, adjust, and manage uncertainty actively.
Change enablement	Prepare people and the organization for transition, adoption, and benefits realization.

Delivery Approach Selection

Approach	Choose when	Planning style	Change handling	Key artifacts	Common PMP trap
Predictive	Requirements are stable; scope can be defined upfront; compliance or contracts need control	Detailed upfront planning and baselines	Formal change requests and approvals	Charter, project management plan, WBS, baselines, change log	Implementing scope changes without approval
Agile	Requirements are uncertain; fast feedback is valuable; product can be delivered incrementally	Rolling-wave, iterative planning	Backlog reprioritization; inspect and adapt	Product backlog, sprint backlog, increment, definition of done	PM assigns sprint work or overrides product owner
Hybrid	Some elements need control while others evolve	Mix of baseline control and iterative delivery	Formal control for fixed elements; backlog control for adaptive elements	Roadmap, release plan, baselines, backlog	Applying one lifecycle rigidly to all work
Incremental	Deliver complete pieces over time	Plan increments and integration	Prioritize features by value	Release roadmap, acceptance criteria	Confusing incremental delivery with no planning
Iterative	Refine through repeated cycles	Plan near-term detail, refine later	Feedback changes the solution	Prototype, iteration backlog	Treating early prototypes as final deliverables

Roles and Decision Authority

Role	Primary exam meaning	High-yield distinction
Project manager	Integrates work, manages constraints, facilitates communication, leads team	Does not make every technical decision alone
Sponsor	Provides authority, funding support, strategic direction, and escalation path	Charter and major business decisions often involve sponsor
Product owner	Owns product value and backlog ordering in agile contexts	Prioritizes what is built; team determines how
Scrum master / agile coach	Facilitates agile process, removes impediments, supports team effectiveness	Servant leader, not command-and-control manager
Project team	Performs work, estimates, identifies risks, builds quality	Should be engaged in planning and problem solving
Functional manager	Provides people, expertise, and operational authority in matrix settings	Resource conflicts may require negotiation
Change control board or authorized approver	Reviews and decides certain change requests	PM analyzes and recommends; approver authorizes
Customer / end user	Provides requirements, feedback, acceptance, and value perspective	Engage early and continuously
PMO	Standards, governance, templates, coaching, portfolio/program support	May be supportive, controlling, or directive depending on organization

Artifact Map

Artifact	Purpose	Use when the question mentions
Business case	Justifies investment and expected value	Project selection, continued viability, strategic alignment
Benefits management plan	Defines expected benefits, owners, timing, measurement	Benefits realization, transition to operations
Project charter	Formally authorizes the project and PM authority	Project start, sponsor approval, high-level objectives
Project management plan	Integrated plan for executing, monitoring, and controlling	“Refer to the plan,” governance, baselines, subsidiary plans
Scope baseline	Approved scope statement, WBS, WBS dictionary	Scope control, deliverable boundaries
WBS	Decomposes project scope into manageable work packages	Scope definition, estimating, accountability
Requirements documentation	Captures stakeholder and solution requirements	Traceability, validation, acceptance
Requirements traceability matrix	Links requirements to deliverables and tests	Preventing missed requirements
Schedule baseline	Approved schedule model	Schedule performance and change control
Cost baseline	Approved time-phased budget	Cost performance and earned value
Risk register	Individual risks, analysis, owners, responses	New risk, probability/impact, response planning
Risk report	Overall project risk exposure	Executive risk visibility and trends
Issue log	Current problems requiring action	Risk occurred, defect, blocker, dispute
Change log	Tracks change requests and status	Scope, schedule, cost, or baseline changes
Stakeholder register	Identifies stakeholders and attributes	New stakeholder, influence, engagement planning
Stakeholder engagement plan	Strategies for stakeholder involvement	Resistance, support, communication gaps
Communications management plan	Who receives what information, when, how	Miscommunication, reporting, escalation paths
Resource management plan	Roles, responsibilities, acquisition, team development	Staffing, training, resource conflicts
RACI matrix	Responsibility assignment	Role ambiguity
Quality management plan	Standards, methods, acceptance, assurance/control approach	Defects, audits, quality expectations
Lessons learned register	Captures learning during the project	Recurring problems, continuous improvement
Product backlog	Ordered list of product work in agile	New features, changing priorities
Sprint backlog	Work selected for current sprint	Sprint execution and team ownership
Definition of done	Shared completion criteria	Quality, acceptance, incomplete work
Acceptance criteria	Conditions for accepting a specific item	Validation and customer acceptance

Change, Risk, and Issue Control

Predictive Change Control Flow

    flowchart TD
	A[Change request or variance identified] --> B[Log request]
	B --> C[Analyze impact on scope, schedule, cost, quality, risk, resources, benefits]
	C --> D{Within PM authority?}
	D -->|Yes| E[Approve or reject per governance]
	D -->|No| F[Submit to authorized approver or change control board]
	F --> G{Approved?}
	G -->|Yes| H[Update baselines, plans, logs, and communicate]
	G -->|No| I[Communicate decision and keep current baseline]
	H --> J[Implement approved change]

Item	Definition	Correct response
Risk	Uncertain event or condition that may affect objectives	Analyze, assign owner, plan response
Issue	Current condition affecting the project	Log, assign action owner, resolve, communicate
Assumption	Something treated as true for planning	Validate; convert to risk if uncertain and impactful
Constraint	Limitation such as budget, date, regulation, contract	Plan within it; escalate if objectives conflict
Defect	Deliverable does not meet requirements or quality criteria	Correct, verify, update lessons learned
Change request	Formal proposal to modify scope, schedule, cost, quality, or plan	Analyze impact before approval or implementation
Workaround	Unplanned response to an occurred risk or issue	Document and update plans/registers afterward
Contingency plan	Planned response if a risk trigger occurs	Execute when trigger/condition is met
Fallback plan	Backup response if primary response fails	Use after contingency is insufficient

Change Control Traps

Trap answer	Why it is weak
“Make the change because the customer asked”	Bypasses impact analysis and authorization
“Reject the change because scope is frozen”	Ignores evaluation and business value
“Escalate to sponsor immediately”	PM should usually assess first
“Update the baseline after implementation”	Baselines are updated after approval, before controlled execution
“Tell the team to absorb it”	Hides impact and creates unmanaged scope creep

What Should the Project Manager Do Next?

Exam cue	Best next action
Unknown cause of delay	Analyze root cause with the team before choosing corrective action
Critical path activity slipping	Evaluate schedule impact, consider compression options, update forecast
Stakeholder is resistant	Meet to understand concerns; update engagement strategy
Executive stakeholder complains about lack of updates	Review communications plan, adjust if needed, communicate appropriately
Team member lacks skill	Coach, train, pair with mentor, or adjust assignments
Team member is disruptive	Address privately, clarify expectations, use conflict resolution
Functional manager will not release resource	Negotiate using resource plan; escalate only if unresolved
Vendor deliverable late	Review contract and procurement plan; document, meet vendor, apply remedies
Customer rejects deliverable	Compare against acceptance criteria; resolve gaps or clarify requirements
Requirements are changing frequently	In predictive, use change control; in agile, refine and prioritize backlog
Sprint goal threatened by new request	Product owner and team evaluate; protect sprint unless urgent tradeoff is agreed
Project no longer supports strategy	Review business case/benefits; escalate to sponsor/governance
Benefits are not being realized	Reassess benefits plan, transition/adoption, and business ownership
Safety or ethical violation	Act immediately, document, follow policy, escalate appropriately
Lessons from prior project are relevant	Review lessons learned before planning or corrective action

Stakeholder and Communication Reference

Stakeholder Engagement

Current state	Desired response
Unaware	Identify interest and impact; provide targeted information
Resistant	Understand concerns; address impact, benefits, and involvement
Neutral	Build relevance and participation
Supportive	Keep informed and engaged
Leading	Use as champion or change advocate

Stakeholder problem	Better PMP action
Hidden stakeholder emerges late	Update stakeholder register and engagement plan
Conflicting requirements	Facilitate prioritization and tradeoff discussion
Low adoption of deliverable	Engage users, training, change management, benefits focus
Sponsor unavailable	Use agreed escalation/communication path; document decisions
Stakeholders disagree publicly	Facilitate structured discussion; focus on objectives and data

Communication Rules

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

Communication need	Best method
Sensitive conflict	Face-to-face or rich interactive communication when possible
Routine status	Push communication such as reports or dashboards
Large audience reference information	Pull communication such as repository or knowledge base
Complex requirements	Workshops, facilitated sessions, prototypes
Urgent risk or issue	Direct communication plus documentation
Virtual team alignment	Frequent check-ins, working agreements, visible information radiators

Team Leadership and Conflict

Concept	Exam meaning
Servant leadership	Remove impediments, support team growth, enable ownership
Emotional intelligence	Recognize and manage emotions, build trust
Self-organizing team	Team decides how to do work within goals and constraints
Psychological safety	Team can raise risks, issues, and mistakes without fear
Team charter	Working agreements, values, communication norms
Tuckman model	Forming, storming, norming, performing, adjourning
Ground rules	Expected behaviors; useful for conflict prevention
Training	Build needed competencies before replacing people

Conflict approach	Use when	PMP preference
Collaborate / problem solve	Important issue; need durable solution	Usually best long-term
Compromise	Need acceptable middle ground quickly	Useful but may not optimize
Smooth / accommodate	Preserve relationship; issue is minor	Temporary
Withdraw / avoid	Cooling-off period or low-value conflict	Rarely best if issue matters
Force / direct	Emergency or authority-based decision needed	Use cautiously

Formula Sheet

Estimating

\[ \text{PERT expected duration} = \frac{O + 4M + P}{6} \]\[ \sigma = \frac{P - O}{6} \]

Formula	Meaning	Exam note
Triangular estimate = (O + M + P) / 3	Simple average of optimistic, most likely, pessimistic	Less weighted than PERT
PERT estimate = (O + 4M + P) / 6	Weighted average emphasizing most likely	Common for uncertain activity duration
Standard deviation = (P - O) / 6	Spread for beta/PERT estimate	Larger spread means more uncertainty
Range estimate	Estimate expressed as low-high	Useful when uncertainty is high

Schedule

Term	Meaning
Critical path	Longest path through the network; determines shortest project duration
Total float	Time an activity can slip without delaying project finish
Free float	Time an activity can slip without delaying its successor
Lead	Acceleration; successor starts before predecessor fully finishes
Lag	Waiting time inserted between activities
Fast tracking	Perform activities in parallel; increases risk/rework
Crashing	Add resources to shorten duration; increases cost
Resource leveling	Adjust schedule for resource limits; may change critical path
Resource smoothing	Adjust within float; does not change critical path

Formula	Use
Total float = LS - ES	Late start minus early start
Total float = LF - EF	Late finish minus early finish
Forward pass	Calculates early start and early finish
Backward pass	Calculates late start and late finish

Earned Value Management

\[ CV = EV - AC,\quad SV = EV - PV \]\[ CPI = \frac{EV}{AC},\quad SPI = \frac{EV}{PV} \]

Variable	Meaning
BAC	Budget at completion
PV	Planned value
EV	Earned value
AC	Actual cost
CV	Cost variance
SV	Schedule variance
CPI	Cost performance index
SPI	Schedule performance index
EAC	Estimate at completion
ETC	Estimate to complete
VAC	Variance at completion
TCPI	To-complete performance index

Metric	Formula	Interpretation
Cost variance	CV = EV - AC	Positive is under budget; negative is over budget
Schedule variance	SV = EV - PV	Positive is ahead; negative is behind
Cost performance index	CPI = EV / AC	Greater than 1 is favorable
Schedule performance index	SPI = EV / PV	Greater than 1 is favorable
Estimate to complete	ETC = EAC - AC	Expected remaining cost
Variance at completion	VAC = BAC - EAC	Positive is favorable
EAC if current cost efficiency continues	EAC = BAC / CPI	Use when CPI trend is expected to continue
EAC if future work follows original plan	EAC = AC + (BAC - EV)	Past variance considered atypical
EAC with new bottom-up remaining estimate	EAC = AC + bottom-up ETC	Use when original assumptions are no longer valid
EAC if cost and schedule both affect remaining work	EAC = AC + (BAC - EV) / (CPI * SPI)	Use when both performance factors matter
TCPI based on BAC	TCPI = (BAC - EV) / (BAC - AC)	Required efficiency to meet original budget
TCPI based on EAC	TCPI = (BAC - EV) / (EAC - AC)	Required efficiency to meet revised estimate

Risk and Decision Analysis

\[ \text{Expected monetary value} = \text{probability} \times \text{impact} \]

Tool	Use	Exam note
Probability-impact matrix	Prioritize qualitative risks	High probability and high impact need attention
EMV	Quantitative expected value	Add EMVs across decision paths
Decision tree	Compare alternatives under uncertainty	Choose best expected value, considering risk appetite
Sensitivity analysis	Shows which variable has greatest effect	Tornado diagram is common representation
Monte Carlo analysis	Simulates many outcomes	Produces probability distribution of cost/schedule outcomes

Risk Response Strategies

Risk type	Strategy	Meaning
Threat	Avoid	Change plan to eliminate threat
Threat	Mitigate	Reduce probability or impact
Threat	Transfer	Shift ownership/impact to third party, often contract/insurance
Threat	Accept	Take no proactive action beyond monitoring or reserves
Opportunity	Exploit	Ensure opportunity happens
Opportunity	Enhance	Increase probability or impact
Opportunity	Share	Partner with another party to capture opportunity
Opportunity	Accept	Take advantage if it occurs
Threat or opportunity	Escalate	Move outside project authority to appropriate level

Reserve type	Purpose
Contingency reserve	Known identified risks; included for planned risk responses
Management reserve	Unknown-unknowns; controlled outside the project baseline depending on governance

Agile and Hybrid Quick Reference

Agile Roles, Events, and Artifacts

Item	Purpose	PMP trap
Product owner	Maximizes product value and orders backlog	PM should not override backlog priority
Scrum master / agile coach	Facilitates process and removes impediments	Not the team’s boss
Development team	Builds increment and estimates work	Self-organizing; not assigned task-by-task by PM
Sprint planning	Selects sprint goal and work	Needs team involvement
Daily scrum	Synchronizes team and identifies impediments	Not a status meeting for the PM
Sprint review	Demonstrates increment and collects feedback	Not the same as retrospective
Retrospective	Improves process and teamwork	Should produce actionable improvements
Backlog refinement	Clarifies and prepares future backlog items	Ongoing, not a substitute for sprint planning
Product backlog	Ordered product work	Continuously refined
Sprint backlog	Work for current sprint	Owned by team
Increment	Potentially usable product result	Must meet definition of done
Definition of done	Shared quality/completion standard	Prevents partially complete work being counted

Agile Metrics and Tools

Metric/tool	Meaning	Watch for
Velocity	Amount of work completed per iteration	Use for forecasting, not comparing teams
Burndown chart	Remaining work over time	Shows whether sprint/release is on track
Burnup chart	Completed work and total scope	Makes scope changes visible
Cumulative flow diagram	Work by status over time	Bottlenecks and WIP buildup
Lead time	Time from request to delivery	Customer-focused flow metric
Cycle time	Time from start of work to completion	Team flow efficiency
WIP limit	Caps work in progress	Improves focus and exposes bottlenecks
Information radiator	Visible project/team information	Encourages transparency

Agile Decision Cues

Cue	Best answer direction
Requirements unclear	Use iterative discovery, prototypes, backlog refinement
Customer feedback changes priority	Product owner reorders backlog
Team repeatedly misses sprint goals	Retrospective, root cause, adjust planning/velocity assumptions
Work is blocked	Scrum master/agile lead helps remove impediment
Stakeholder wants mid-sprint change	Discuss with product owner/team; usually place in backlog unless urgent
Quality problems in increments	Strengthen definition of done, test automation, pairing, root cause
Too much work started	Apply WIP limits and improve flow
Distributed agile team struggles	Working agreements, collaboration tools, overlap hours, transparency

Scope, Quality, Procurement, and Governance

Scope and Requirements

Concept	Exam distinction
Product scope	Features and functions of the product/service/result
Project scope	Work required to deliver the product/service/result
Validate scope	Formal acceptance by customer or sponsor
Control scope	Manage changes to scope baseline
Gold plating	Adding extra features not requested; avoid
Scope creep	Uncontrolled expansion without approval
Acceptance criteria	Conditions deliverable must satisfy
WBS dictionary	Details about WBS components and work packages

Quality

Concept	Meaning
Quality management	Plan and build quality into processes and deliverables
Quality assurance	Process-focused confidence that quality processes are followed
Quality control	Deliverable-focused inspection/testing of results
Prevention cost	Cost to avoid defects
Appraisal cost	Cost to evaluate quality
Internal failure cost	Defects found before customer delivery
External failure cost	Defects found after customer delivery
Continuous improvement	Incremental process improvement using data and feedback
Root cause analysis	Identify underlying cause, not just symptom

Quality cue	Better PMP action
Repeated defects	Root cause analysis and process improvement
Customer rejects deliverable	Compare to acceptance criteria and validate requirements
Team says inspection will catch issues later	Build quality in earlier
Process noncompliance	Audit/review process, correct, update lessons learned

Procurement

Contract type	Best fit	Buyer risk	Seller risk
Fixed-price	Well-defined scope	Lower	Higher
Cost-reimbursable	Uncertain or evolving scope	Higher	Lower
Time and materials	Staff augmentation or unclear exact duration	Medium; manage with caps/controls	Medium

Procurement cue	Best response
Vendor late	Review contract, document issue, meet vendor, seek corrective action
Seller requests extra payment	Review contract and change provisions
Contract dispute	Follow claims/dispute process; document communications
Need specialized capability	Consider make-or-buy and procurement strategy
Vendor proposes unauthorized change	Use contract/change control process

Business Environment, Benefits, and Change Adoption

Concept	PMP meaning
Strategic alignment	Project should support organizational objectives
Business value	Tangible or intangible benefit delivered by the project
Benefits realization	Ensuring outcomes are achieved after deliverables are produced
Compliance	Requirements from law, regulation, policy, contract, or standards
Organizational change management	Preparing users and operations to adopt the result
Transition plan	Moving deliverable to operations, customer, or support team
Governance	Decision rights, approvals, oversight, and accountability

Business environment cue	Best answer
Project value no longer clear	Revisit business case and benefits with sponsor/governance
Users resist new system	Engage stakeholders, training, communication, change champions
Deliverable complete but benefits not achieved	Assess adoption, operational readiness, and benefits ownership
Compliance requirement discovered	Analyze impact and follow required governance
Competing strategic priorities	Escalate through portfolio/sponsor governance with analysis

Ethics and Professional Conduct Cues

Cue	Correct direction
Conflict of interest	Disclose promptly and follow policy
Confidential information	Protect it; share only with authorized parties
Inaccurate status report pressure	Report truthfully with evidence and corrective plan
Favoritism or unfair vendor treatment	Use fair, transparent procurement practices
Safety concern	Act immediately and escalate appropriately
Cultural misunderstanding	Use respect, active listening, and inclusive communication

Common PMP Traps

Trap	Better thinking
Escalate first	Assess and attempt resolution within authority first, except urgent ethics/safety/compliance issues
Fire or replace first	Coach, train, clarify, and remove impediments first
Implement customer request immediately	Analyze and follow change/backlog process
Ignore stakeholder resistance	Engage early; resistance is a risk to value
Treat agile as no planning	Agile plans continuously at appropriate detail
Treat predictive as no adaptation	Predictive projects still monitor, control, and change formally
Choose technical fix without root cause	Diagnose before solving
Add extra features to please customer	Avoid gold plating
Hide bad news until solved	Communicate transparently per plan
Use only email for sensitive conflict	Prefer richer communication
Count incomplete agile work as done	Must meet definition of done
Confuse sprint review and retrospective	Review inspects product; retrospective improves process
Confuse risk and issue	Risk is uncertain; issue is happening now
Update baseline without approval	Baselines change only through authorized process

Final Review Checklist

Use this list after each practice set:

Did you identify the lifecycle: predictive, agile, or hybrid?
Did you choose an answer that assesses before acting?
Did you follow the correct artifact: plan, log, register, baseline, backlog, or contract?
Did you distinguish risk from issue and change request from defect?
Did you protect approved baselines in predictive scenarios?
Did you let the product owner prioritize value in agile scenarios?
Did you empower the team rather than micromanage?
Did you engage stakeholders instead of avoiding conflict?
Did you consider business value, benefits, and compliance?
Did you avoid escalation unless the issue exceeded PM authority or involved ethics, safety, or compliance?
Did you interpret EVM correctly: positive variances and indexes above 1 are favorable?
Did you select prevention/root cause analysis over late inspection and blame?

Practical Next Step

Take a timed PMP practice set, mark every missed question by category, then return to this Quick Reference to review the exact decision pattern: lifecycle, artifact, stakeholder, risk/change control, agile role, or formula.

Scenario Guide

People