PMP Certification — Fundamentals
The 6 project management principles
PMBOK 8 consolidates the 7th Edition's 12 principles into 6 broader ones — the same underlying values, regrouped rather than discarded:
Two PMBOK 7 principles didn't merge into another principle at all: tailoring moved out of the principles list entirely into its own section of the Guide (still central to PMP reasoning, just structurally relocated — see below), and risk moved into the Risk performance domain rather than remaining a standalone principle. (needs verification — recheck against current source: exact principle wording and the principle-to-principle mapping above reflect secondary analysis of PMI's published 8th Edition; confirm directly against the PMBOK Guide 8th Edition text.)
The Project Management Mindset — new in PMBOK 8
PMBOK 8 introduces a three-dimensional mindset framework with no equivalent in the 7th Edition, grouping the 6 principles into three lenses: Proactive (Adopt a Holistic View + Embed Quality), Ownership (Be an Accountable Leader + Build an Empowered Culture), and Value-Driven (Focus on Value + Integrate Sustainability). This framing is worth learning explicitly — it's new conceptual scaffolding PMI added specifically to connect the principles to day-to-day practice, and exam scenarios can draw on it directly.
The 7 performance domains
PMBOK 8 reduces PMBOK 7's 8 outcome-focused performance domains to 7, and — the more significant change — makes them function-oriented: each domain now embeds its own processes (40 total across all 7), rather than describing outcomes with no prescribed process guidance the way PMBOK 7's domains did.
| Performance domain | Embedded processes | What it covers |
|---|
|---|---|---|
| **Governance** | 9 | Integration-style work: project initiation, plan alignment, execution management, change control, knowledge management, quality assurance, sourcing strategy, project/phase closeout |
|---|---|---|
| Scope | 6 | Requirements elicitation, scope definition, scope structure (the PMBOK 8 term replacing "WBS"), scope validation and control |
| Schedule | 3 | Schedule management planning and schedule development, monitoring, and control |
| Finance | 4 | Financial management planning, cost estimating, budget development, and finance monitoring/control (broadened from "cost" to "finance" to include funding and value analysis) |
| Stakeholders | 7 | Stakeholder identification and engagement, plus communications management — PMBOK 7 treated communications as a separate concern; PMBOK 8 folds it into this domain |
| Resources | 5 | Resource planning, acquisition, and control, plus team leadership (PMBOK 7's separate "develop team" and "manage team" processes are merged into a single "Lead the Team" process here) |
| Risk | 6 | Risk planning, identification, analysis (PMBOK 7's separate qualitative and quantitative risk analysis processes are merged here), response planning, and implementation |
Three of PMBOK 7's 8 domains don't map to a PMBOK 8 domain directly: Development Approach and Life Cycle moved into a life-cycle discussion in the Standard's main body rather than remaining a performance domain; Planning is no longer a standalone domain — planning processes are distributed across all 7 domains above instead; and Measurement likewise isn't a standalone domain — measurement concepts (including earned value management) now sit inside each domain's monitoring-and-controlling processes, most concentrated in Finance. (needs verification — recheck against current source: process counts per domain and the domain-mapping details above reflect secondary analysis; confirm directly against the PMBOK Guide 8th Edition text before treating any specific count as final.)
Tailoring — now a section, not a principle
Tailoring — adapting planning depth, documentation formality, and process rigor to a specific project's size, complexity, and risk profile rather than applying one methodology uniformly — remains just as central to PMP reasoning as it was in PMBOK 7. What changed is structural, not conceptual: PMBOK 8 moved tailoring out of the principles list into its own dedicated section of the Guide. Most PMP exam scenarios still ultimately test tailoring judgment in some form, whether or not the question labels it that way.
Focus Areas — PMBOK 8's name for Process Groups
PMBOK 7 kept Process Groups (Initiating, Planning, Executing, Monitoring & Controlling, Closing) as an optional model. PMBOK 8 renames these five to Focus Areas and reframes them as explicitly approach-agnostic — applicable to predictive, agile, and hybrid delivery alike, rather than implicitly describing a predictive sequence. Conceptually they still describe the same lifecycle progression; the rename signals PMI's intent that they not be read as waterfall-specific.