PMBOK® Guide 6 had six scope processes in chapter 5. PMBOK® Guide – Eighth Edition also has six, but three of them carry new names, and one has moved. If you still look for “Collect Requirements”, “Create WBS” or “Control Scope” in the new guide, you will not find them as process names.
Old and new names side by side
| PMBOK 6 (Project Scope Management, chapter 5) | PMBOK 8 (Scope performance domain, section 2.2.2) |
|---|---|
| 5.1 Plan Scope Management | 2.2.2.1 Plan Scope Management |
| 5.2 Collect Requirements | 2.2.2.2 Elicit and Analyze Requirements |
| 5.3 Define Scope | 2.2.2.3 Define Scope |
| 5.4 Create WBS | 2.2.2.4 Develop Scope Structure |
| 5.5 Validate Scope | 2.2.2.6 Validate Scope |
| 5.6 Control Scope | 2.2.2.5 Monitor and Control Scope |
We searched the full text of PMBOK 8 for the old names; the PMBOK 6 names come from its chapter 5. “Collect Requirements” and “Create WBS” have zero hits in PMBOK 8. “Control Scope” appears only as part of “Monitor and Control Scope”, never on its own as a process name.
What changed beyond the names
Plan Scope Management keeps its name. PMBOK 6 defines it as creating a scope management plan that documents how scope will be defined, validated and controlled. PMBOK 8 keeps that idea and adds that the approach differs between predictive and adaptive projects, the latter being more iterative and collaborative. Our page on the scope management plan covers the document itself.
Elicit and Analyze Requirements replaces Collect Requirements. The new verb pair puts analysis next to gathering. PMBOK 8 describes the aim as defining and documenting the stakeholders’ needs for features and functions so that quality and value are assured. The requirements traceability matrix remains the tool most readers associate with this step.
Define Scope keeps its name, but its description is wider. PMBOK 8 says it produces a detailed or high-level description of the project, product and expected value, at the start for predictive approaches or at the start of each iteration for adaptive and hybrid ones. It also identifies quality requirements and standards for the deliverables and how the project will show that they are met. PMBOK 6 describes only the detailed description of project and product.
Develop Scope Structure replaces Create WBS. The definition is the same as before: subdividing project deliverables and project work into smaller, more manageable components. What is new is the explicit agile reading. In agile projects, PMBOK 8 says, this corresponds to breaking down the product backlog into epics, features and user stories. For predictive projects the work breakdown structure stays the central result, and PMBOK 8 mentions a WBS dictionary for complex or interdependent deliverables.
Monitor and Control Scope replaces Control Scope. The PMBOK 6 definition is monitoring the status of project and product scope and managing changes to the scope baseline. PMBOK 8 keeps both parts and adds measuring the quality of the deliverables and checking that required standards are met.
Validate Scope keeps its name and moves from position five to position six, behind Monitor and Control Scope. PMBOK 6 defines it as formalizing acceptance of the completed deliverables. PMBOK 8 names two objectives: checking the processes used to reach the quality standards, and formalizing acceptance.
Why this matters for searching and studying
Most material online, including older pages on this site, still uses the PMBOK 6 vocabulary. If a course or template says “Create WBS”, it means what PMBOK 8 now calls Develop Scope Structure. The same pattern appeared in the cost processes and in the schedule area, where six processes became three. For the larger picture, read our overview of PMBOK 8.
What we did not check
We compared process names, definitions and the descriptions in section 2.2.2. We did not compare every input, tool and output line by line between the two editions, so this is not a complete mapping. PMI’s free table of contents may not list the process names, so the primary source for the details is the guide itself.
Sources: PMBOK® Guide – Eighth Edition, section 2.2.2 (Scope performance domain, processes, from page 39); PMBOK® Guide – Sixth Edition, chapter 5; PMI PMBOK Guide page; PMBOK Guide Eighth Edition table of contents (PDF).
By Tom, PMP-certified since 2004. Last updated: October 2026
Bild: KI-generiert