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 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 |
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 |
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” |
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 |
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.
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.
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 |
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.
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 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.
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 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 |
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 |
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.
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 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 |
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.