The PMBOK® Guide — Eighth Edition does not revise the previous editions so much as re-cut them. The Seventh Edition’s 12 principles become 6. Its 8 performance domains become 7, carrying almost none of the same names. The Sixth Edition’s 49 processes become 40, and they return to the centre of the guide after an edition away from it.
This page maps the old to the new: every one of the 49 processes traced to what it became, all 12 principles traced to where they went, and each of the 8 performance domains traced to what absorbed it. It is a reference, not a summary — if you learned project management from the Sixth or Seventh Edition, this is the translation layer.
The change at a glance
| Element | Sixth / Seventh Edition | Eighth Edition |
|---|---|---|
| Principles | 12 (7th Ed) | 6 |
| Performance domains | 8 (7th Ed) | 7 |
| Processes | 49 (6th Ed) | 40 |
| Process groups / focus areas | 5 process groups (6th Ed) | 5 focus areas |
| Knowledge areas | 10 (6th Ed) | — |
Two of those rows deserve a closer look before the detail. The process groups return — renamed Focus Areas, and no longer presented as containers of processes but as areas of activity that a project moves through. And the knowledge areas formally disappear, which is the single most misleading row in the table, because in substance they did not.
Where the 7 performance domains actually came from
The Eighth Edition presents seven performance domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk. Read that list next to the Seventh Edition’s — Stakeholder, Team, Development Approach and Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty — and only one name survives.
Read it instead next to the Sixth Edition’s ten knowledge areas and the resemblance is obvious. The Eighth Edition’s performance domains are structurally the Sixth Edition’s knowledge areas. They inherit the Seventh Edition’s name and the Sixth Edition’s organizing principle.
That is a testable claim rather than an impression, so we tested it. Taking each of the 49 processes, noting the knowledge area it belonged to, and following it to the domain it now sits in: 40 of 46 traceable processes (87%) land in the domain corresponding to their old knowledge area, and four domains are a perfect match.
| Eighth Edition domain | Sixth Edition knowledge area it corresponds to | Match |
|---|---|---|
| Schedule | Schedule Management | 100% |
| Finance | Cost Management (widened to finance) | 100% |
| Resources | Resource Management | 100% |
| Risk | Risk Management | 100% |
| Scope | Scope Management | 86% |
| Governance | Integration Management (renamed) | 78% |
| Stakeholders | Stakeholder + Communications Management (merged) | merge |
So the real arithmetic is 10 knowledge areas into 7 domains: five survive one-to-one, Integration is renamed Governance, Stakeholder and Communications merge, and Quality and Procurement are dissolved — neither has a domain, and between them they account for most of the processes that disappear.
The guide itself supports the reading in its definition: an Eighth Edition performance domain is defined as a group of related processes, where the Seventh Edition defined one as a group of related activities. Processes are the unit of organization again.
The 8 performance domains: where each one went
Because the two editions organize on different axes, this map is genuinely many-to-many. Only one Seventh Edition domain survives recognizably, and two Eighth Edition domains inherit nothing from any of them.
| Seventh Edition domain | Became | What happened |
|---|---|---|
| Stakeholder | Stakeholders | The only domain to survive largely intact. It also absorbs the whole Communications knowledge area, and all seven of its processes keep their names. |
| Team | Resources | Ceases to be a domain. Its substance concentrates in the Lead the Team process, and its behavioural framing moves up into two principles. People are now treated as a category of resource. |
| Development Approach and Life Cycle | The Standard, Section 4 | Leaves the domain set entirely and moves into The Standard, where its subsections reappear almost one for one as Project Phases, Development Approaches, and Delivery Cadence. |
| Planning | Planning focus area | Stops being a place and becomes an axis. Planning is now a focus area holding 19 of the 40 processes, spread across all seven domains. |
| Project Work | Governance | Absorbed mainly by Governance — execution, change and project knowledge. Its procurement material goes to the procurement appendix. |
| Delivery | Scope | Splits. Requirements, scope definition and scope creep go to Scope; quality divides between Scope and Governance; the value material becomes the Focus on Value principle. |
| Measurement | Governance | Absorbed by Governance, whose key concepts are now measurement theory — leading indicators, lagging indicators, SMART criteria. |
| Uncertainty | Risk | Narrowed and renamed Risk. Ambiguity and uncertainty survive inside it, complexity leaves for a principle, and volatility loses its dedicated treatment. |
The 12 principles became 6
This is the one part of the crosswalk that PMI publishes itself, in Appendix X5 of the Eighth Edition. The mapping below follows PMI’s own table; the wording is ours.
| Eighth Edition | Came from (7th Ed) | Change |
|---|---|---|
| Adopt a Holistic View | Navigate Complexity Recognize, Evaluate, and Respond to System Interactions |
Merged (2 → 1) |
| Focus on Value | Effectively Engage With Stakeholders Focus on Value Embrace Adaptability and Resiliency Enable Change to Achieve the Envisioned Future State |
Merged (4 → 1) |
| Embed Quality Into Processes and Deliverables | Build Quality Into Processes and Deliverables | Refined (1 → 1) |
| Build an Empowered Culture | Create a Collaborative Project Team Environment | Refined (1 → 1) |
| Be an Accountable Leader | Demonstrate Leadership Behaviors Be a Diligent, Respectful, and Caring Steward |
Merged (2 → 1) |
| Tailoring section | Tailor Based on Context | Moved out of the principles (1 → 1) |
| Risk performance domain | Optimize Risk Responses | Moved out of the principles (1 → 1) |
Note what is missing from that table. Five of the six Eighth Edition principles have a Seventh Edition ancestor. “Integrate Sustainability Within All Project Areas” has none — it is the only genuinely new principle in the edition, and the clearest signal of where the profession is being pointed.
Note also the two principles that stopped being principles. Tailoring moved into its own section, and optimizing risk responses moved into the Risk domain — in both cases because practitioners asked for concrete mechanics rather than a statement of value.
The 49 processes became 40
Of the 40 processes in the Eighth Edition, 20 keep their names exactly, 16 are renamed, and 4 are merges of two or more predecessors. A further 3 of the old 49 have no successor process at all.
The table below is the complete map. Every one of the 49 appears exactly once. The same map as a printable sheet.
| Eighth Edition process | Domain | Focus area | Was (6th Ed) | Change |
|---|---|---|---|---|
| Initiate Project or Phase | Governance | Initiating | Develop Project Charter | Renamed |
| Integrate and Align Project Plans | Governance | Planning | Develop Project Management Plan | Renamed |
| Plan Sourcing Strategy | Governance | Planning | Plan Procurement Management | Renamed |
| Manage Project Execution | Governance | Executing | Direct and Manage Project Work | Renamed |
| Manage Quality Assurance | Governance | Executing | Manage Quality | Renamed |
| Manage Project Knowledge | Governance | Executing | Manage Project Knowledge | Unchanged |
| Monitor and Control Project Performance | Governance | Monitoring and Controlling | Monitor and Control Project Work | Renamed |
| Assess and Implement Changes | Governance | Monitoring and Controlling | Perform Integrated Change Control | Renamed |
| Close Project or Phase | Governance | Closing | Close Project or Phase | Unchanged |
| Plan Scope Management | Scope | Planning | Plan Scope Management | Unchanged |
| Elicit and Analyze Requirements | Scope | Planning | Collect Requirements | Renamed |
| Define Scope | Scope | Planning | Define Scope | Unchanged |
| Develop Scope Structure | Scope | Planning | Create WBS | Renamed |
| Monitor and Control Scope | Scope | Monitoring and Controlling | Control Scope | Renamed |
| Validate Scope | Scope | Monitoring and Controlling | Validate Scope Control Quality |
Merged (2 → 1) |
| Plan Schedule Management | Schedule | Planning | Plan Schedule Management | Unchanged |
| Develop Schedule | Schedule | Planning | Define Activities Sequence Activities Estimate Activity Durations Develop Schedule |
Merged (4 → 1) |
| Monitor and Control Schedule | Schedule | Monitoring and Controlling | Control Schedule | Renamed |
| Plan Financial Management | Finance | Planning | Plan Cost Management | Renamed |
| Estimate Costs | Finance | Planning | Estimate Costs | Unchanged |
| Develop Budget | Finance | Planning | Determine Budget | Renamed |
| Monitor and Control Finances | Finance | Monitoring and Controlling | Control Costs | Renamed |
| Identify Stakeholders | Stakeholders | Initiating | Identify Stakeholders | Unchanged |
| Plan Stakeholder Engagement | Stakeholders | Planning | Plan Stakeholder Engagement | Unchanged |
| Plan Communications Management | Stakeholders | Planning | Plan Communications Management | Unchanged |
| Manage Stakeholder Engagement | Stakeholders | Executing | Manage Stakeholder Engagement | Unchanged |
| Manage Communications | Stakeholders | Executing | Manage Communications | Unchanged |
| Monitor Stakeholder Engagement | Stakeholders | Monitoring and Controlling | Monitor Stakeholder Engagement | Unchanged |
| Monitor Communications | Stakeholders | Monitoring and Controlling | Monitor Communications | Unchanged |
| Plan Resource Management | Resources | Planning | Plan Resource Management | Unchanged |
| Estimate Resources | Resources | Planning | Estimate Activity Resources | Renamed |
| Acquire Resources | Resources | Executing | Acquire Resources | Unchanged |
| Lead the Team | Resources | Executing | Develop Team Manage Team |
Merged (2 → 1) |
| Monitor and Control Resourcing | Resources | Monitoring and Controlling | Control Resources | Renamed |
| Plan Risk Management | Risk | Planning | Plan Risk Management | Unchanged |
| Identify Risks | Risk | Planning | Identify Risks | Unchanged |
| Perform Risk Analysis | Risk | Planning | Perform Qualitative Risk Analysis Perform Quantitative Risk Analysis |
Merged (2 → 1) |
| Plan Risk Responses | Risk | Planning | Plan Risk Responses | Unchanged |
| Implement Risk Responses | Risk | Executing | Implement Risk Responses | Unchanged |
| Monitor Risks | Risk | Monitoring and Controlling | Monitor Risks | Unchanged |
The 3 processes with no successor
These are the ones that simply stop existing as processes.
| Sixth Edition process | What happened to it |
|---|---|
| Plan Quality Management | No quality-planning process remains. The quality management plan survives as a document and is an input to several processes, but nothing produces it. |
| Conduct Procurements | Procurement is demoted out of the process set to an appendix. |
| Control Procurements | Procurement is demoted out of the process set to an appendix. |
The four consolidations worth knowing
- Scheduling took the deepest cut. Define Activities, Sequence Activities, Estimate Activity Durations and Develop Schedule become a single Develop Schedule. The whole domain drops from six processes to three.
- Quality loses both of its processes. Manage Quality becomes Manage Quality Assurance under Governance, and Control Quality is folded into Validate Scope, which now has two jobs: checking against quality standards and obtaining formal acceptance.
- Procurement leaves the process set. Only its planning half survives, as Plan Sourcing Strategy under Governance. Conducting and controlling procurements move to an appendix.
- Develop Team and Manage Team become Lead the Team, and qualitative and quantitative risk analysis collapse into a single Perform Risk Analysis — the qualitative/quantitative distinction is now a choice of technique, not a process boundary.
Where the 40 processes sit
The distribution across the five focus areas is heavily weighted towards the front of the project — 19 of the 40 are planning processes, and exactly 1 is a closing process.
| Focus area | Processes |
|---|---|
| Initiating | 2 |
| Planning | 19 |
| Executing | 8 |
| Monitoring and Controlling | 10 |
| Closing | 1 |
Three things the summaries get wrong
The inputs and outputs are not a list to memorize any more. Every process in the Eighth Edition carries inputs, tools and techniques, and outputs (ITTOs) — and every single one of those lists is explicitly open-ended. All 120 of them end by noting the list continues. The Sixth Edition’s ITTOs were widely treated as closed sets to be learned; the Eighth Edition’s formally are not. What that changes, counted across all 120 columns.
Artificial intelligence is not woven through the processes. The Eighth Edition gives AI its own appendix, which has been widely reported, so the natural inference is that it now runs through the framework. It does not. Artificial intelligence appears in the inputs, tools and outputs of two of the forty processes, and the wider technology vocabulary — predictive analytics, augmented and virtual reality — is concentrated almost entirely in a single process, Estimate Resources.
The knowledge areas did not disappear. They were renamed performance domains. Anyone who learned the Sixth Edition’s ten knowledge areas already knows most of the Eighth Edition’s structure, which is the opposite of what the change in vocabulary suggests.
How this crosswalk was built
The structural facts — the names, counts and section numbering — are taken from the PMBOK® Guide — Eighth Edition itself, and verified twice: once from the guide’s own table of processes by focus area, and once independently from its section headings. Both give the same 40 processes and the same distribution across the seven domains.
The principle mapping is PMI’s, published in Appendix X5 of the Eighth Edition, and is credited as such above. The process and domain mappings are our own analysis — PMI publishes no item-level crosswalk of either — and each was checked so that all 49 processes and all 12 principles are accounted for exactly once, with no item counted twice and none left out.
Nothing on this page reproduces text from the guide. The names of processes, domains and principles are used to refer to the things they name.
PMBOK, PMI and PMP are registered marks of the Project Management Institute, Inc. This site is not affiliated with or endorsed by PMI. See the disclaimer.