PMP Master Revision Guide

Plain-language coverage of the full exam scope, with real-world examples

How to use this. This is a revision companion, not a replacement for drilling
questions. Read a section, then test yourself on that topic in the mock simulators.
The exam rewards judgment, not recall — so every section ends with the instinct
the exam wants. Where something is a formula or a hard rule, it's marked. Aligned
to the current exam (People 42% / Process 50% / Business Environment 8%), valid
through the 8 July 2026 cutoff.

PART 0 — The one thing that passes this exam: the PMI mindset
Most PMP questions are situational: "What should the project manager do NEXT / FIRST /
BEST?" Two or three options are usually "correct" in real life. The exam wants the one that
matches how PMI thinks a great project manager behaves. Burn these in:

-​ Be proactive. Prevent problems; don't wait to react. (Like running condition-based

maintenance instead of waiting for the bearing to fail.)
-​ Find the root cause before acting. Don't treat the symptom. (You wouldn't replace a
pump that keeps tripping without finding why it trips.)
-​ Talk to the people involved first. Go to the source. Don't escalate to the sponsor or go
formal as your first move.
-​ Serve the team (servant leadership). Remove obstacles, coach, protect them. Never
blame or remove people hastily.
-​ Empower the team. Let them self-organize and make the technical decisions. You
facilitate; they decide how.
-​ Check what already exists. Lessons learned, risk register, the plan — look there before
inventing something new.
-​ Lean collaborative / agile / hybrid. Favor transparency, iteration, and working
solutions.
-​ Deliver value, not just outputs. A project on time and on budget that delivers no
benefit has failed.

Test: when two answers both look right, pick the one that is more proactive, more people-first,
more team-empowering, and more value-focused. That single habit is worth more than any
formula.
PART 1 — PEOPLE domain (≈42%)
This domain is about leading and building the team and managing relationships. Roughly half
the exam is agile/hybrid, so these ideas show up in agile clothing too.

Leadership vs management
-​ Managing = dealing with systems and processes to get work done (schedules, budgets,
controls).
-​ Leading = vision, motivation, influencing people.
-​ A great PM does both, but on the exam lead with leadership: inspire and enable rather
than command.

Servant leadership (huge on the exam)

The leader exists to serve the team: remove impediments, shield them from distractions, coach,
and help them grow. Example: your team is constantly pulled into unplanned side requests. A
servant leader negotiates with those requesters and protects the team's focus — rather than
telling the team to "just work faster."

Building and developing the team

-​ Tuckman's stages: Forming → Storming → Norming → Performing → Adjourning.
Storming (conflict, friction) is normal; coach the team through it, don't panic.
-​ Develop the team through training, mentoring, and pairing. Prefer growing a capable
person over replacing them for one closable skill gap.
-​ Team charter / ground rules: the team's agreed values and ways of working. Set these
with the team, not for them.
-​ Recognition works best when it's timely and doesn't pit people against each other
(avoid win/lose rewards).

Motivation (recognize the names)

-​ Maslow: hierarchy of needs (basic → safety → social → esteem → self-actualization).
-​ Herzberg: hygiene factors (salary, conditions) prevent dissatisfaction but don't motivate;
motivators (achievement, recognition, growth) drive satisfaction.
-​ McGregor Theory X/Y: X = people need control; Y = people are self-motivated. PMI
leans Y.
-​ McClelland: needs for achievement, power, affiliation.

Conflict management (know the best approach)

Five approaches: Collaborate/Problem-solve (win-win, best & most lasting), Compromise
(lose-lose / partial), Smooth/Accommodate (emphasize agreement), Force (win-lose),
Withdraw/Avoid (retreat — only OK for trivial issues or to cool down). Default exam answer:
Collaborate. Face the issue, use facts, find a solution both sides accept.

Emotional intelligence
Self-awareness, self-regulation (stay calm under bad news), social awareness, relationship
management. Example: a vendor drops a bombshell in front of the team. EI means pausing,
staying composed, and gathering facts — not venting or blaming.

Influencing & power

Types of power: Expert (competence), Referent (respect/relationship), Reward, Legitimate
(position), Coercive (punishment). Most effective for PMs: Expert and Referent — especially
in a matrix where you have little formal authority. Influence comes from credibility and
relationships.

Stakeholders & communication

-​ Active listening: paraphrase back and confirm understanding.
-​ Power/Interest grid: High power + high interest = manage closely; high power/low
interest = keep satisfied; low/high = keep informed; low/low = monitor.
-​ Move resistant stakeholders toward supportive by engaging to understand their
concerns, not by avoiding or forcing them.

Virtual & diverse teams

Set shared communication norms collaboratively; build cultural awareness and respect; use the
right tools. Don't force one culture's norms or isolate subgroups.

People-domain instinct: talk to people directly, coach don't command, empower the team,
address conflict head-on with collaboration, and protect a sustainable pace.

PART 2 — PROCESS domain (≈50%)

This is the "how the work gets done" domain. It blends predictive (plan-driven) mechanics with
agile/hybrid delivery. We'll cover the predictive knowledge areas, then agile/hybrid.

2.1 Integration (tying it all together)

-​ Project charter: issued by the sponsor/initiator; it authorizes the project and
empowers the PM. Without it, you have no mandate.
-​ Project management plan: the integrated set of all subsidiary plans and baselines.
 -​ Integrated Change Control: every change after baselining is assessed for impact
(scope, time, cost, risk, quality), then the Change Control Board (CCB)
approves/rejects. Never just "do" a change because it seems small.
-​ Lessons learned: captured continuously, not only at the end.

2.2 Scope
-​ Collect requirements → Define scope → Create WBS (decompose deliverables into
work packages) → WBS dictionary.
-​ Scope baseline = scope statement + WBS + WBS dictionary.
-​ Requirements traceability matrix: links each requirement to its origin and to the
deliverable that satisfies it (ensures nothing is lost).
-​ Validate Scope = the customer formally accepts deliverables. Control Quality = the
team checks deliverables are correct internally. Quality first, then acceptance.
-​ Scope creep (uncontrolled change) and gold plating (adding unrequested extras) are
both bad. Control scope to the agreed requirements.

2.3 Schedule
-​ Define activities → sequence → estimate durations → develop schedule.
-​ Critical path: the longest path through the network; it has zero float and sets the
minimum project duration. (Formula world: see Part 5.)
-​ Float/slack: how long an activity can slip without delaying the project (LS−ES or
LF−EF).
-​ Leads and lags: a lead lets a successor start early; a lag is an imposed delay.
-​ Schedule compression: Crashing = add resources → costs more. Fast tracking = do
things in parallel → more risk/rework.
-​ Critical chain: schedule with buffers to protect against resource constraints.
-​ Rolling wave planning: detail the near-term work now, elaborate distant work later
(progressive elaboration).

2.4 Cost & Earned Value (high-yield)

EVM tells you, in money terms, whether you're ahead/behind and over/under budget. Memorize
the core formulas (Part 5). The fast intuition:

-​ CV / CPI answer "budget?" — positive CV or CPI > 1 = good (under budget).

-​ SV / SPI answer "schedule?" — positive SV or SPI > 1 = good (ahead).
-​ EAC = forecast total cost. ETC = cost of the remaining work. VAC = forecast
surplus/deficit.
-​ Reserves: Contingency = for known risks, inside the cost baseline (PM controls it).
Management = for unknown work, outside the baseline (needs management approval).
2.5 Quality
-​ Prevention over inspection — design quality in; don't rely on catching defects.
-​ Cost of quality: Conformance (prevention + appraisal) vs Nonconformance (internal +
external failure). Spending on prevention is cheaper than failure.
-​ Tools: Pareto (the vital few causes — 80/20), Ishikawa/fishbone (cause-and-effect,
find root causes), Control charts (is the process stable? rule of seven = 7 points one
side of the mean = investigate), Histograms, Scatter diagrams.
-​ Validate Scope vs Control Quality (see 2.2).

2.6 Resources
-​ Acquire, develop, manage the team; for physical resources, plan and control them.
-​ Resource leveling (smooth over-allocation, may extend dates) vs resource smoothing
(within float).
-​ RACI chart (Responsible, Accountable, Consulted, Informed) clarifies roles.

2.7 Communications
-​ ~90% of a PM's time is communicating.
-​ Methods: Interactive (meetings/calls — best for complex/sensitive), Push (email,
reports — sent out), Pull (knowledge base — people retrieve).
-​ Channels = n(n−1)/2. Adding people increases complexity fast.

2.8 Risk
-​ Identify → Qualitative analysis (rate probability × impact, prioritize) → Quantitative
analysis (numbers/modeling like Monte Carlo, only on selected risks) → Plan
responses → Implement → Monitor.
-​ Threat responses: Avoid (eliminate it), Mitigate (reduce probability/impact), Transfer
(insurance/contract — shift to a third party), Accept (do nothing proactive / set
contingency), Escalate (outside your authority).
-​ Opportunity responses: Exploit (make sure it happens), Enhance (increase
odds/impact), Share (partner), Accept, Escalate.
-​ Secondary risk: a new risk created by your response. Residual risk: what's left over
after the response.
-​ Log new risks in the risk register and analyze before responding — don't fund or
escalate blindly.

2.9 Procurement
-​ Contract types & who carries cost risk:
-​ Fixed Price (FFP/FPIF/FP-EPA): seller carries most cost risk; needs
well-defined scope. Lowest risk to buyer.
 -​ Cost-Reimbursable (CPFF/CPIF/CPAF): buyer carries more cost risk; good
when scope is uncertain.
-​ Time & Materials (T&M): hybrid, flexible, good for staff augmentation/undefined
scope.
-​ Bidder conference: all sellers get the same information — supports fairness.
-​ Make-or-buy analysis: decide build internally vs purchase.
-​ Claims: disputed changes; resolve ideally by negotiation (then ADR, then litigation).

2.10 Stakeholder engagement

-​ Identify → plan engagement → manage → monitor.
-​ Engagement assessment matrix: compares current vs desired engagement (e.g.,
Resistant → Supportive) so you can plan to close the gap.
-​ Update the stakeholder register throughout the project.

PART 3 — AGILE & HYBRID essentials (woven through ~50% of

the exam)

The mindset
Agile Manifesto values: individuals & interactions > processes & tools; working software >
documentation; customer collaboration > contract negotiation; responding to change > following
a plan. (The right items have value; the left are valued more.) Welcome change — even late —
and reprioritize the backlog. (Contrast: predictive controls change formally through the CCB.)

Scrum roles
-​ Product Owner (PO): owns and orders the backlog, maximizes value, accepts work
against acceptance criteria. Represents the customer.
-​ Scrum Master: servant leader/coach; facilitates events; removes impediments;
protects the process. Does not assign work.
-​ Developers (the team): self-manage, decide how to build, and own the day-to-day
work.

Scrum events
-​ Sprint: short timebox (e.g., 1–4 weeks) producing a usable increment.
-​ Sprint Planning: decide the sprint goal and what to build (PO + team).
-​ Daily Standup: ≤15 min team coordination — plan the next 24h, surface impediments.
Not a status report to the PM.
-​ Sprint Review: inspect the product increment with stakeholders; get feedback.
 -​ Retrospective: inspect the team's process; agree improvements.
-​ Backlog refinement (grooming): keep upcoming items clear, sized, and ready
(ongoing).

Artifacts & concepts

-​ Product backlog (ordered list of everything) → sprint backlog (this sprint's work) →
increment (done work). Release = when increment(s) are actually delivered to users.
-​ Definition of Done (DoD): shared completeness standard. Acceptance criteria:
conditions for a specific story.
-​ User story: "As a [user], I want [goal], so that [value]." INVEST (Independent,
Negotiable, Valuable, Estimable, Small, Testable).
-​ MVP: smallest releasable version to get early value and feedback.
-​ Spike: time-boxed experiment to reduce uncertainty.

Estimation & metrics

-​ Relative estimation / story points (often via planning poker); when estimates differ,
the outliers explain, then re-vote — don't average or impose.
-​ Velocity: a single team's forecasting tool — never compare teams or use it as a
performance score.
-​ Burndown (remaining work falling) vs Burnup (completed work rising toward total
scope — makes scope changes visible).
-​ Kanban: visualize the workflow; WIP limits improve flow by exposing bottlenecks; pull
work as capacity frees up.
-​ Information radiators: make progress visible to all (task boards, charts) —
transparency, not surveillance.

Hybrid
Mix predictive and agile to fit the work: e.g., a stable infrastructure stream run predictively while
the software is built in sprints. Tailor to context.

Agile-domain instinct: protect the sprint, push new requests to the backlog for the PO to
prioritize, keep events for the team's benefit, foster psychological safety and self-organization,
and deliver value incrementally.

PART 4 — BUSINESS ENVIRONMENT (≈8%)

Small slice, easy points if you know these:
 -​ Project vs operations: a project is temporary with a unique result; operations are
ongoing/repetitive.
-​ Business case & benefits: the project must keep making business sense. Revisit the
business case at decision points / phase gates. A benefits realization management
plan defines how/when benefits are delivered and measured. On time + on budget but
no benefit = failure.
-​ Compliance: non-negotiable. A new regulation/standard mid-project? Assess the
impact and comply, managing the change properly. Don't defer it.
-​ OPA vs EEF: OPAs = your organization's internal assets (templates, processes,
historical lessons learned). EEFs = conditions that influence you (regulations, market,
culture) but you don't create.
-​ Organizational structures: Functional (PM low authority) → Matrix
(weak/balanced/strong) → Projectized (PM high authority). Know that resource
negotiation gets harder the weaker your authority.
-​ PMO types: Supportive (templates/guidance, low control), Controlling (requires
compliance, moderate control), Directive (actually manages the projects, high control).
-​ Tailoring: adapt approach, life cycle, and processes to the project's size, risk, industry,
and culture. No single method fits all.

PART 5 — Formula quick sheet (know EVM cold; recognize the

rest)
Metric Formula Read it as

Earned Value (EV) % complete × BAC value of work actually done

Cost Variance (CV) EV − AC + = under budget

Schedule Variance (SV) EV − PV + = ahead of schedule

Cost Perf. Index (CPI) EV / AC > 1 = under budget

Schedule Perf. Index (SPI) EV / PV > 1 = ahead

EAC (typical) BAC / CPI forecast total cost if trend

holds

EAC (atypical) AC + (BAC − EV) forecast if rest is on-budget

ETC EAC − AC cost of remaining work

VAC BAC − EAC forecast surplus(+)/deficit(−)

 Metric Formula Read it as

TCPI (to BAC) (BAC − EV) / (BAC − AC) > 1 = must be more efficient

Comm. channels n(n − 1) / 2 number of communication

paths

PERT estimate (O + 4M + P) / 6 weighted activity estimate

PERT std deviation (P − O) / 6 estimate uncertainty

Float / slack LS − ES (or LF − EF) delay possible without

slipping project

Reading trick: anything starting with EV ÷ something → index. EV/AC = cost (CPI), EV/PV =
schedule (SPI). Variances subtract; indices divide.

PART 6 — Professional & ethical responsibility (PMI Code)

Four values: Responsibility, Respect, Fairness, Honesty.

-​ Conflict of interest: disclose it to affected stakeholders and step back from the
decision. Never conceal it.
-​ Be honest in estimates and reporting; don't inflate or hide bad news.
-​ Respect laws, customs, and confidentiality; protect proprietary information.
-​ Fairness: no favoritism, no discrimination, transparent decisions.

Exam instinct: when an answer involves honesty, transparency, or disclosure, it's usually right.
Cover-ups and "quietly proceed" are always wrong.

PART 7 — Exam-day strategy

-​ Read the last line first. The question often asks NEXT / FIRST / BEST / EXCEPT —
that word changes the answer.
-​ Eliminate the two clearly wrong options, then choose between the remaining two
using the mindset test (proactive, people-first, team-empowered, value-focused).
-​ Watch for distractors that are real PM activities but not the first/best step (e.g.,
"escalate to the sponsor" early, "go straight to a change request," "remove the team
member").
 -​ Agile context cues ("sprint," "backlog," "product owner") → answer in agile terms;
predictive cues ("baseline," "CCB," "WBS") → answer in predictive terms.
-​ Manage your time (~1.3 min/question). Flag and move on; don't sink on one item. Use
your simulator the same way.
-​ Don't change answers without a clear reason — first instinct grounded in the mindset is
usually right.

Final note
This guide covers the full scope at revision depth. If any single section feels thin for you after a
mock — say, risk responses or EVM forecasting — tell me and I'll expand that section into a
deeper, example-heavy mini-lesson rather than bloating everything. The smart move with your
remaining days: read a part, take the matching mock, log misses, then revisit. Good luck —
you're well-resourced and the plan is sound.