PMP Study Guide (2026 ECO)

Foundation — PMBOK principles & performance domains

PMBOK 7 (and the upcoming 8th edition) is principles-based, not a list of 49 processes. Internalize these — they generate exam answers.

12 Principles (how to behave)

Be a diligent, respectful, caring steward; build a collaborative team environment; effectively engage stakeholders; focus on value; recognize and respond to systems interactions; demonstrate leadership; tailor based on context; build quality into processes and deliverables; navigate complexity; optimize risk responses; embrace adaptability and resiliency; enable change to achieve the envisioned future state.

8 Performance Domains (what to manage)

Stakeholders · Team · Development Approach & Life Cycle · Planning · Project Work · Delivery · Measurement · Uncertainty. Each describes outcomes to achieve, not steps to follow.

Delivery approaches

• Predictive (waterfall): requirements known up front; plan-driven; change-controlled. ~40% of items.
• Adaptive (agile): iterative/incremental; backlog, sprints, ceremonies; embrace change. Roles: product owner, scrum master, dev team. Artifacts: product/sprint backlog, increment, burndown.
• Hybrid: mix predictive and adaptive to fit the work. ~60% of items are agile or hybrid — know servant leadership cold.

Numbers & formulas worth knowing

• EVM: CV = EV−AC; SV = EV−PV; CPI = EV/AC; SPI = EV/PV (≥1 is good). EAC = BAC/CPI.
• Communication channels: n(n−1)/2.
• Three-point (PERT) estimate: (O + 4M + P) / 6.

Domain I — People 33%

Leading and supporting the team and stakeholders. The dominant mode is servant leadership: remove impediments, empower, facilitate.

Tasks (2026 ECO)

• Develop a common vision — build and keep a shared vision with key stakeholders; trace misunderstandings to root cause.
• Manage conflict — identify the source, analyze context, apply an agreed resolution. Know the modes: collaborate/problem-solve (best, win-win), compromise, smooth/accommodate, force/direct, withdraw/avoid.
• Lead the project team — set expectations, empower, solve problems, represent the team's voice, choose a fitting leadership style, set clear roles & responsibilities (RACI).
• Engage stakeholders — identify, analyze, tailor communication, execute the engagement plan, build trust and influence.
• Align & manage stakeholder expectations — categorize stakeholders (power/interest grid), facilitate alignment, monitor satisfaction, mentor.
• Ensure knowledge transfer — identify critical knowledge, gather it, foster an environment for sharing (lessons learned, communities of practice).
• Plan and manage communication — define strategy, promote transparency, establish feedback loops, meet reporting/governance needs.

Exam instincts for People

• A team member is underperforming → understand why first (1:1), don't punish or escalate.
• Conflict between members → bring them together to resolve it (facilitate); collaborating beats avoiding.
• Build motivation via empowerment and recognition (think Maslow, Herzberg, Theory Y, McClelland).
• Self-organizing teams: the PM facilitates and protects, doesn't command.

Domain II — Process 41% — the largest domain

Executing the technical work of managing the project across the full life cycle.

Tasks (2026 ECO)

• Develop an integrated plan & plan delivery — assess complexity, recommend the development approach (predictive/agile/hybrid), estimate effort/resources, integrate plans, collect & analyze data for decisions.
• Develop and manage scope — define scope, get stakeholder agreement, decompose (WBS / product backlog). Beware scope creep and gold-plating.
• Ensure value-based delivery — identify value with stakeholders, prioritize by value, deliver incrementally, track benefits.
• Plan and manage resources — define, acquire, optimize availability.
• Plan and manage procurement — plan, select contract types (fixed-price vs cost-reimbursable vs T&M — know the risk balance), negotiate, manage suppliers/contracts.
• Plan and manage finance / budget — analyze needs, fund contingency/reserves, track spend, manage variances with governance.
• Plan and optimize quality — gather requirements, plan processes/tools, ensure compliance, manage cost of quality, drive continuous improvement (prevention over inspection).
• Plan and manage schedule — choose the approach, estimate (story points / milestones / dependencies), build & baseline, manage variance. Know critical path.
• Evaluate project status — develop metrics, tailor & maintain artifacts, measure progress, communicate status (EVM, dashboards, burndown).
• Manage project closure — get approval, define close criteria, validate transition, capture final lessons learned, release resources.

Exam instincts for Process

• Always tailor: there's no one-size approach — choose what fits the project.
• Behind schedule? Analyze before crashing/fast-tracking; understand impact and cost/risk.
• Quality is built in, not inspected in. Prevention > appraisal > failure cost.
• Procurement risk shifts with contract type (FFP = seller's risk; CPFF = buyer's risk).

Domain III — Business Environment 26% — tripled for 2026

Connecting the project to the wider organization, compliance, and strategy. Study this hard — it's the biggest 2026 change and many older materials underweight it.

Tasks (2026 ECO)

• Define and establish governance — structure, rules, reporting, ethics, and policies via organizational process assets (OPAs); define success metrics; set escalation paths and thresholds.
• Plan and manage compliance — confirm requirements (security, health & safety, sustainability, regulatory), classify categories, identify threats to compliance, address gaps, measure compliance.
• Manage and control changes — run the integrated change control process: evaluate, get CCB approval, communicate, implement, update documents/baselines. Never implement an undocumented change.
• Remove impediments and manage issues — assess impact, prioritize, apply intervention strategies, and recognize when a risk has become an issue.
• Plan and manage risk — identify, qualitative + quantitative analysis, maintain a risk register, plan responses (avoid / transfer / mitigate / accept for threats; exploit / share / enhance / accept for opportunities / escalate), monitor.
• Continuous improvement — use lessons learned, update processes and OPAs.
• Support organizational change — assess culture, evaluate the project's impact on the org and act (think Kotter / ADKAR style change management).
• Evaluate external business environment changes — survey regulatory, technology, geopolitical, and market shifts; reprioritize scope/backlog accordingly.

Exam instincts for Business Environment

• Compliance and safety usually override schedule and cost — pick the compliant option.
• Tie work to the business case and benefits; if a project no longer delivers value, recommend stopping it.
• External change (new regulation, market shift) → assess impact on backlog/scope, then adapt — don't ignore it.
• Expect AI and sustainability as new 2026 context in scenarios.