PMP — PMI Project Management Professional - 2026 Exam Refresh Quick Review

Quick review for PMI Project Management Professional (PMP) - 2026 Exam Refresh candidates using topic drills, mock exams, and detailed explanations.

Quick Review focus

This Quick Review supports preparation for the PMI Project Management Professional (PMP) - 2026 Exam Refresh from PMI, exam code PMP. It is PM Mastery review support and is not affiliated with PMI.

Use this page to refresh high-yield concepts before moving into topic drills, mock exams, and detailed explanations in a question bank. The PMP exam is scenario-heavy: success depends less on recalling isolated definitions and more on choosing the best project management action for the situation.

The PMP answer mindset

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

Scenario signalPreferAvoid
Unclear factsAssess, review documents, ask clarifying questionsActing immediately without diagnosis
ConflictFacilitate collaboration and root-cause problem solvingEscalating first or ignoring the issue
Change request in predictive workLog, analyze impact, follow change controlImplementing because a stakeholder asked
New priority in adaptive workReprioritize through the product backlog and product owner/customerTreating all change as formal baseline change
RiskIdentify, analyze, assign owner, plan responseWaiting until the risk becomes an issue
Stakeholder resistanceAnalyze interest/influence, engage, communicate valueReplacing communication with authority
Team performance issueCoach, remove impediments, build capabilityPunish, blame, or micromanage
Vendor issueReview contract, document facts, use procurement processInformal side deals or ignoring contract terms
Compliance concernFollow required governance and escalate appropriatelyPrioritizing schedule over compliance
Ethical issueBe honest, fair, responsible, and transparentConcealing facts to protect the project

A fast scenario-reading algorithm

  1. Identify the delivery approach: predictive, adaptive, or hybrid.
  2. Find the real problem: risk, issue, change, conflict, quality, stakeholder, procurement, compliance, or value alignment.
  3. Notice the question wording: “first,” “next,” “best,” “should have done,” or “most likely.”
  4. Use the right level of authority: team, project manager, product owner, sponsor, change control board, governance body, or procurement function.
  5. Choose the proactive, ethical, value-focused answer.
  6. 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.

ApproachBest fitKey practicesCommon exam trap
PredictiveRequirements are stable; scope can be defined early; compliance or contract constraints are strongCharter, detailed planning, WBS, baselines, integrated change control, formal acceptanceImplementing changes without impact analysis and approval
AdaptiveRequirements evolve; frequent feedback is valuable; product discovery mattersProduct backlog, iterations, increments, reviews, retrospectives, servant leadershipAssuming “agile” means no planning, no documentation, or no control
HybridSome elements are fixed while others need iterative discoveryPredictive governance for fixed constraints plus adaptive delivery for evolving workApplying one method blindly to the whole project

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.

ConceptQuick reviewExam decision point
Project charterFormally authorizes the project and gives the project manager authorityIf no authority exists, secure authorization rather than acting informally
Business caseExplains why the project is worth doingIf the project no longer supports value, raise it with sponsor/governance
Project management planIntegrated plan plus subsidiary plans and baselinesReview the plan before taking process-driven action
Work performance data/information/reportsRaw observations become analyzed information and then reportsDo not confuse raw data with actionable reporting
Lessons learnedCaptured throughout, not only at closingUse prior lessons when planning or solving repeated issues
Change controlEvaluates impact before approving changesDo not implement unapproved scope, schedule, or cost changes
ClosureConfirms acceptance, transitions deliverables, archives records, releases resourcesClosure is more than “the work is finished”

Change control in predictive work

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

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

Change in adaptive work

Adaptive work expects change, but not chaos.

SituationBetter answer
Stakeholder wants a new featureAdd/refine/prioritize it in the product backlog
Stakeholder wants to disrupt current iterationProduct owner and team evaluate impact; protect iteration goals unless change is justified
Customer feedback changes prioritiesReorder backlog based on value, risk, and learning
Team discovers technical debtMake it visible, prioritize appropriately, and include it in planning
Scope is unclearUse 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

AreaHigh-yield reviewBest-answer pattern
Servant leadershipRemove impediments, support self-management, coach the teamAsk what the team needs; facilitate, do not dictate
Emotional intelligenceUnderstand emotions, motivations, conflict, and stakeholder concernsListen first, then respond deliberately
Psychological safetyTeam members can raise problems without fearEncourage transparency and learning
Conflict managementConflict can be productive if handled wellCollaborate/problem-solve for durable resolution
MotivationPeople need purpose, autonomy, mastery, recognition, and fair treatmentAddress root causes, not just symptoms
Virtual teamsNeed communication norms, trust building, and clear working agreementsImprove collaboration structure, not just meeting frequency
Team developmentSkills, cohesion, and performance improve over timeCoach, train, mentor, and remove blockers

Conflict techniques

TechniqueWhen it may fitPMP caution
Collaborate/problem-solveImportant issue; long-term solution neededUsually the strongest answer when time allows
CompromiseTime pressure; both sides can give somethingMay not solve root cause
Smooth/accommodatePreserve harmony on low-priority issueCan hide real problems
Force/directEmergency, safety, or urgent decisionOften too authoritarian for normal scenarios
Withdraw/avoidCooling-off period or trivial issueWeak 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.

Stakeholders and communication

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

TopicQuick reviewTrap to avoid
Identify stakeholdersFind people/groups affected by or able to affect the projectIdentifying only executives or only end users
Analyze stakeholdersConsider power, interest, influence, impact, and desired engagementTreating all stakeholders the same
Engagement planPlan how to move stakeholders toward productive engagementCommunicating randomly or reactively
Manage expectationsAddress concerns early and honestlyHiding bad news
Monitor engagementReassess as the project changesAssuming early stakeholder analysis stays valid
Communication planDefines who needs what information, when, how, and why“More communication” is not always better

Communication methods

MethodUse whenExample
InteractiveImmediate feedback is neededMeeting, workshop, call
PushInformation must be sent to recipientsEmail, report, notification
PullLarge audience accesses information as neededDashboard, 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.

Scope, schedule, and cost

Scope control

ConceptMeaningCommon confusion
RequirementsStakeholder needs and conditionsNot the same as final scope baseline
Scope statementDefines project/product scope and boundariesShould clarify exclusions
WBSDecomposes deliverables into manageable workNot a schedule; not an org chart
Scope baselineApproved scope statement, WBS, and WBS dictionaryChanges require control in predictive work
Validate scopeFormal acceptance of completed deliverablesDifferent from quality control
Control scopeManage changes to scope baselinePrevent scope creep

Schedule review

ConceptQuick reviewExam cue
DependencyLogical relationship between activitiesMandatory, discretionary, external, internal
LeadAllows successor to start earlier“Overlap” work
LagDelay between activitiesWaiting period
Critical pathLongest path controlling project durationDelays may delay the project
Float/slackTime an activity can slip without affecting a targetLow or zero float means schedule sensitivity
CrashingAdd resources to shorten scheduleUsually increases cost
Fast trackingPerform work in parallelUsually increases risk/rework

Cost and earned value essentials

TermPlain meaning
PVPlanned value: budgeted value of scheduled work
EVEarned value: budgeted value of completed work
ACActual cost: money spent
BACBudget at completion
CVCost variance = EV - AC
SVSchedule variance = EV - PV
CPICost performance index = EV / AC
SPISchedule performance index = EV / PV
EACEstimate at completion
ETCEstimate to complete
VACVariance at completion = BAC - EAC

Interpretation:

MetricFavorableUnfavorable
CVPositiveNegative
SVPositiveNegative
CPIGreater than 1Less than 1
SPIGreater than 1Less than 1

Common EAC logic:

SituationFormula
Future work expected at original budget rateEAC = AC + (BAC - EV)
Current cost performance expected to continueEAC = BAC / CPI
Cost and schedule performance both affect remaining workEAC = AC + (BAC - EV) / (CPI × SPI)
New bottom-up estimate for remaining work existsEAC = 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.

Quality management

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

ConceptReview pointTrap
Quality planningDefine standards and how to meet themWaiting until testing to think about quality
Manage qualityAudit and improve processesConfusing it with inspecting deliverables only
Control qualityInspect/test deliverables and record resultsConfusing it with formal customer acceptance
Validate scopeCustomer/sponsor acceptance of deliverablesNot the same as control quality
Cost of qualityPrevention/appraisal plus failure costsIgnoring prevention because it costs time
Continuous improvementImprove process capability and reduce defectsTreating defects as isolated events only

Quality tool cues

ToolUseful for
Cause-and-effect diagramRoot cause analysis
Pareto chartPrioritizing major contributors
Control chartProcess stability over time
HistogramFrequency distribution
Scatter diagramRelationship between variables
Check sheetTallying occurrences
FlowchartUnderstanding process steps
AuditChecking process compliance and improvement opportunities

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

Risk and issue management

A risk is uncertain. An issue has occurred.

TopicQuick review
Risk registerDocuments risks, causes, probability/impact, owners, and responses
Risk ownerPerson responsible for monitoring and response execution
TriggerWarning sign that a risk may occur
Contingency planPlanned response if a risk event occurs
Fallback planBackup if the primary response fails
Residual riskRisk remaining after response
Secondary riskNew risk created by a response
WatchlistLower-priority risks monitored over time

Risk response strategies

Risk typeStrategyMeaning
ThreatAvoidRemove the threat or its cause
ThreatMitigateReduce probability or impact
ThreatTransferShift ownership/impact to another party, often contractually
ThreatAcceptTake no proactive action beyond monitoring or reserves
ThreatEscalateMove outside project authority to appropriate level
OpportunityExploitEnsure the opportunity happens
OpportunityEnhanceIncrease probability or benefit
OpportunitySharePartner to capture benefit
OpportunityAcceptTake advantage if it occurs
OpportunityEscalateMove 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.

Procurement and contracts

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

Contract typeBasic ideaRisk tendency
Firm fixed priceSet price for defined workMore risk to seller if costs rise
Fixed price incentive feeFixed price with incentive termsShared performance motivation
Cost plus fixed feeReimburses allowable costs plus fixed feeMore cost risk to buyer
Cost plus incentive feeCost reimbursement with incentive formulaShared cost/performance focus
Time and materialsPay for time and materials usedNeeds 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 and adaptive review

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

Agile roles and responsibilities

RoleFocusCommon trap
Product owner/customer representativeProduct value, backlog ordering, acceptance prioritiesProject manager unilaterally prioritizes product features
Scrum master/agile leadFacilitation, process health, impediment removalActs as command-and-control manager
Development team/team membersBuild and deliver incrementsWaiting for detailed task assignments
StakeholdersProvide feedback and business contextBypassing the product owner or team agreements

Agile artifacts and events

ItemPurpose
Product backlogOrdered list of product work
Iteration/sprint backlogWork selected for the iteration
IncrementUsable product output
Definition of doneShared quality/completion standard
Product roadmapDirection and sequencing of value
Release planForecast of releasable capability
Daily standupCoordination, impediments, near-term plan
Review/demoFeedback on completed increment
RetrospectiveImprove team process
Backlog refinementClarify, split, estimate, and reorder work

Agile metrics

MetricUseCaution
VelocityForecasting team capacityDo not use as a weapon against the team
Burn-down chartRemaining work trendNot a complete value measure
Burn-up chartCompleted work and scope changesUseful when scope changes
Cumulative flow diagramFlow, bottlenecks, WIPLook for widening bands
Cycle timeTime from work start to completionSupports flow improvement
Lead timeTime from request to deliveryUseful 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.

AreaReview pointBest-answer pattern
Business valueProjects exist to create benefitsReassess if expected value changes
Benefits realizationBenefits may occur after project deliveryAlign outputs with intended outcomes
GovernanceDecision rights, escalation paths, controlsFollow governance instead of improvising
ComplianceRegulatory, safety, security, or policy requirementsNever ignore compliance for convenience
Organizational changeUsers must adopt the change for value to occurPlan communication, training, and readiness
EEFsExternal/internal conditions outside project controlTailor approach to environment
OPAsOrganizational templates, processes, lessons, repositoriesUse existing assets before reinventing

When value is threatened

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

  1. Gather objective information.
  2. Analyze impact on benefits, cost, schedule, risk, and stakeholders.
  3. Communicate with the sponsor or appropriate governance body.
  4. Recommend options.
  5. 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.

ValuePractical exam behavior
ResponsibilityOwn decisions, follow policies, report issues appropriately
RespectListen, include stakeholders, manage conflict professionally
FairnessAvoid favoritism, disclose conflicts of interest
HonestyProvide 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

WordingWhat it usually testsStrong answer pattern
What should the project manager do first?Immediate professional responseAssess, review plan, identify root cause, or engage affected people
What should the project manager do next?Correct sequenceFollow the defined process after the current step
What should the project manager have done?PreventionPlan, identify risks, engage stakeholders, define expectations earlier
What is the best action?JudgmentProactive, collaborative, ethical, value-focused solution
What should the agile lead do?Servant leadershipFacilitate, coach, remove impediments, support team ownership
What should be updated?Documentation disciplineUpdate 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

  1. Memorizing terms without scenario judgment PMP questions often ask what to do, not what a term means.

  2. Escalating too early Escalation is appropriate when authority is exceeded, governance requires it, or prior steps fail. It is rarely the first move.

  3. Ignoring the delivery approach Predictive change control and adaptive backlog management are not interchangeable.

  4. Confusing quality control with scope validation Quality control checks correctness; validation obtains formal acceptance.

  5. Treating all stakeholder problems as communication problems Sometimes the root issue is power, expectation mismatch, benefit concern, resistance, or poor engagement.

  6. Assuming agile has no planning Agile planning is continuous and adaptive, not absent.

  7. Choosing punitive team actions Coaching, facilitation, and impediment removal are usually better than blame.

  8. Reading too fast Words such as “first,” “except,” “best,” “already approved,” and “newly identified” change the answer.

  9. Overusing formulas without interpretation Know what CPI, SPI, CV, and SV mean in plain business language.

  10. Forgetting documentation updates After decisions, update the appropriate register, log, plan, backlog, report, or baseline.

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?

Using question-bank practice effectively

After this Quick Review, move into PM Mastery practice with original practice questions. Use the question bank deliberately:

Practice stepHow to use it
Topic drillsIsolate weak areas such as agile roles, risk, EVM, change control, or stakeholder engagement
Mixed setsTrain yourself to identify the topic without being told
Mock examsBuild timing, stamina, and scenario judgment
Detailed explanationsReview why the right answer is right and why the distractors are wrong
Error logTrack misses by cause: concept gap, misread wording, wrong approach, or poor sequence
Retake strategyRetake only after you can explain the reasoning, not after memorizing the answer

A practical next step: choose your weakest area from this review, complete a focused topic drill of original practice questions, read every detailed explanation, then do a mixed question-bank set to confirm you can apply the concept in realistic PMP scenarios.

Continue in PM Mastery

Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official PMI questions, copied live-exam content, or exam dumps.

Browse Certification Practice Tests by Exam Family