PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report

1. Executive Summary

Projects underpin modern value creation. The Project Management Body of Knowledge (PMBOK®) has long served as the reference for how projects should be managed. The Seventh Edition (2021) represented a radical shift away from prescriptive processes to a principles‑ and outcomes‑focused model with eight performance domains. The Eighth Edition (2025) continues the evolution but reintroduces process groups as Focus Areas and integrates a set of 40 non‑prescriptive processes, while consolidating principles and reorganising performance domains. The changes aim to make the guide more value‑driven, actionable and globally accessible.

Main conceptual shift:

• From output centric to value centric. PMBOK 7 defined a project as “a temporary endeavor undertaken to create a unique product, service, or result”. PMBOK 8 reframes a project as a “temporary initiative in a unique context undertaken to create value”. “Project management” moves from meeting project requirements to “the application of knowledge, skills, tools and techniques to project activities to meet or exceed the intended value”. The eighth edition emphasises value delivery and benefits realisation rather than merely completing scope within constraints.
• Principles and mindset. PMBOK 7 introduced 12 project management principles (e.g., be a diligent steward, tailor based on context, navigate complexity). PMBOK 8 simplifies these into six principles organised around a project management mindset with three dimensions (proactive, ownership and value‑driven). The new principles include Adopt a Holistic View, Focus on Value, Embed Quality Into Processes and Deliverables, Be an Accountable Leader, Integrate Sustainability Within All Project Areas, and Build an Empowered Culture. These principles encourage proactive leadership, sustainability and empowerment of teams.
• From knowledge areas to performance domains and focus areas. PMBOK 7 abandoned the 10 knowledge areas of earlier editions and introduced eight performance domains (Stakeholder, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty). PMBOK 8 reorganises these into seven performance domains—Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk—aligned with organisational functions. It also reintroduces the five Project Management Process Groups as Focus Areas (Initiating, Planning, Executing, Monitoring & Controlling, Closing) to provide a lifecycle lens.
• Integration of processes and ITTOs. PMBOK 7 removed detailed process descriptions and ITTOs (inputs, tools & techniques, outputs), instead listing models, methods and artefacts. PMBOK 8 brings back 40 non‑prescriptive processes; each process includes ITTOs and tailoring advice within its associated performance domain. This reintegration gives practitioners actionable guidance while maintaining flexibility.

Key structural changes:

Aspect	PMBOK 7	PMBOK 8	Implications
Purpose/Scope	Principles‑based standard with eight performance domains, focusing on why and what rather than how. Models, methods and artefacts replace ITTOs.	Retains a principles‑based standard but simplifies to six principles and seven performance domains. Reintroduces processes and ITTOs through focus areas.	Practitioners must now balance a value‑driven mindset with practical processes and outputs.
Definitions	Project: temporary endeavour to produce a unique outcome. Project management: application of knowledge, skills, tools and techniques to meet project requirements.	Project: temporary initiative in a unique context undertaken to create value. Project management: application of knowledge, skills, tools and techniques to meet or exceed intended value.	Aligns project work with organisational strategy and benefits realisation.
Principles	12 principles emphasising stewardship, team collaboration, stakeholder engagement, value focus, systems thinking, leadership behaviours, tailoring, quality, complexity, risk responses, adaptability, and change enablement.	Six principles organised around a project management mindset; emphasises holistic view, value focus, quality, accountable leadership, sustainability, and empowered culture.	Principles are streamlined for clarity; sustainability and empowerment gain prominence.
Performance Domains	Eight domains: Stakeholder, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.	Seven domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk. Each includes tailored processes and ITTOs.	Domains shift from behavioural/system‑oriented to functional groupings; measurement and uncertainty are absorbed into governance, scope, schedule and risk.
Process Groups / Focus Areas	Process groups removed; 7th edition emphasises continuous flow rather than sequential groups.	Five Focus Areas (Initiating, Planning, Executing, Monitoring & Controlling, Closing) reintroduce the lifecycle perspective.	Provides familiar structure for practitioners using older editions; facilitates mapping to organisational lifecycles.
Processes & ITTOs	No process or ITTO tables; guidance on models, methods and artefacts.	40 non‑prescriptive processes each with inputs, tools, techniques and outputs; tailored within performance domains.	Offers actionable guidance while emphasising adaptability.
Tailoring Guidance	Dedicated section on tailoring development approaches, processes, and artefacts.	Tailoring considerations integrated into each performance domain and process.	Tailoring is more embedded and context‑specific.

Implications for practitioners and organisations:

1. Adopt a value‑driven mindset. Projects are now defined by the value they create, and project management must meet or exceed the intended value. Project managers must expand planning and stakeholder engagement to ensure benefits realisation.
2. Integrate processes with principles. While PMBOK 7 encouraged flexibility through principles, PMBOK 8 provides actionable processes. Practitioners should select and tailor the 40 processes based on context, using performance domains as a framework.
3. Strengthen governance and sustainability. The addition of a Governance performance domain emphasises transparent decision‑making and alignment with organisational strategy. Sustainability is now a core principle; projects should consider environmental and social impacts.
4. Recalibrate organisational methodologies and training. PMOs and training programs built around PMBOK 6/7 must update templates, plans and curricula to reflect focus areas, performance domains and the new definitions.
5. Embrace hybrid and adaptive approaches. PMBOK 8 retains guidance for predictive, adaptive and hybrid lifecycles; practitioners should tailor process use accordingly and leverage the integrated tailoring advice.

2. High‑Level Structural Comparison

2.1 Overall architecture of PMBOK 7

The Seventh Edition comprises two main parts:

1. The Standard for Project Management. This part defines core concepts and the conditions for effective project management. It is principles‑based rather than prescriptive. It introduces 12 principles (Section 3) and explains how they guide behaviours and decisions. The standard also highlights a system of value delivery, linking projects, programs, portfolios, products and operations. Foundational terms are defined (project, project management, project manager, PMO, value).
2. A Guide to the Project Management Body of Knowledge (PMBOK Guide). The guide is divided into three main sections:
   • Project Performance Domains. Eight interrelated domains—Stakeholder, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement and Uncertainty—provide a systems view of project management. Each domain describes purpose, key activities, interactions and outcomes rather than prescribing processes.
   • Tailoring. A dedicated section explains why and how to tailor development approaches, processes and engagement. It describes selecting lifecycle models, tailoring processes, engaging stakeholders and implementing continuous improvement.
   • Models, Methods and Artefacts. Instead of ITTO tables, the guide lists models (e.g., communication models), methods (e.g., brainstorming, prototyping) and artefacts (e.g., business case, project charter) grouped across performance domains. This encourages practitioners to select appropriate techniques based on context.

2.2 Overall architecture of PMBOK 8

The Eighth Edition retains a dual structure—a standard and a guide—but modifies both:

1. The Standard for Project Management. The standard continues to define the environment for project work. Key updates include:
   • Updated definitions. A project is now a temporary initiative “undertaken to create value”. Project management emphasises meeting or exceeding intended value. The standard clarifies characteristics of projects (temporary, unique context, value creation) and reinforces the link between organisational governance and project governance.
   • Six principles and a project management mindset. Section 3 introduces six principles aligned with three dimensions (proactive, ownership, value‑driven). Each principle includes project impact, principle in action and connected performance domains sub‑sections. Sustainability and empowered culture are explicitly addressed, reflecting societal expectations.
   • System for value delivery. The standard expands on how projects fit into a broader value delivery system, emphasising portfolio alignment and benefits realisation.
2. PMBOK Guide—Eighth Edition. Major structural elements include:
   • Project Management Performance Domains (Section 2). Seven domains—Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk—organise project activities by functional focus. Each domain contains key concepts, processes, tailoring considerations, interactions with other domains, and check results subsections.
   • Project Management Focus Areas (Section 4.5). The five Focus Areas—Initiating, Planning, Executing, Monitoring and Controlling, Closing—reintroduce the lifecycle orientation removed in PMBOK 7. They provide a structure for grouping processes and emphasise that each focus area may occur iteratively in adaptive environments.
   • Processes and ITTOs. The guide enumerates 40 non‑prescriptive processes adapted from the historical 49 processes of earlier editions. These processes are mapped into the seven performance domains and the five focus areas. Each process description includes inputs, tools & techniques, outputs and tailoring guidance.
   • Integration with the Standard. The principles inform the processes and domains; the guide cross‑references principles to show how each performance domain contributes to the project management mindset (e.g., the Be an Accountable Leader principle’s connected performance domains include governance, scope, schedule and finance).

2.3 Integration of principles, performance domains and processes

PMBOK 8 explicitly integrates its components:

• Principles inform processes and domains. Each principle section lists connected performance domains and examples of processes or activities where the principle applies (e.g., accountable leadership strengthens governance, scope, schedule and finance). Practitioners are encouraged to interpret the principles as mindsets underpinning all project work.
• Performance domains host processes. Within each domain, relevant processes (from the set of 40) are described along with ITTOs. For example, the Governance Performance Domain includes processes such as Initiate Project or Phase and Integrate and Align Project Plans (mapped to the Initiating and Planning focus areas).
• Focus areas provide lifecycle context. Processes are also grouped into the five focus areas, emphasising the iterative nature of project work. For instance, Plan Scope Management falls within the Planning focus area but is associated with the Scope Performance Domain.

2.4 Evolution of process groups, knowledge areas and performance domains

Element	PMBOK 7 Treatment	PMBOK 8 Treatment	How it evolved
Process Groups	Removed from PMBOK 7; instead, the eight performance domains interact continuously. Process groups remain in practice via the Process Groups Practice Guide (PGPG) which describes 49 processes within the Initiating, Planning, Executing, Monitoring & Controlling and Closing groups.	Reintroduced as Focus Areas with five lifecycle‑oriented categories—Initiating, Planning, Executing, Monitoring & Controlling, Closing.	Gives practitioners a familiar lifecycle lens and allows mapping of the 40 processes to specific phases.
Knowledge Areas	Eliminated; knowledge areas from earlier editions were replaced by performance domains emphasising outcomes and interactions.	Knowledge areas do not return. Their content is synthesised into the seven performance domains; for example, Scope, Schedule and Finance domains absorb scope, time and cost knowledge areas respectively.	Aligns project management with organisational functions and reduces redundancy.
Performance Domains	Eight domains focusing on behaviours and systems: Stakeholder, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.	Seven domains focusing on functional areas: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk. Domains include key concepts, processes and tailoring considerations.	Consolidates delivery, measurement and uncertainty into governance, scope, schedule and risk; introduces Governance domain to emphasise strategic alignment and transparency.
Models, Methods & Artefacts vs. ITTOs	PMBOK 7 lists models (e.g., communication models), methods (e.g., workshops, prototypes) and artefacts (e.g., business case, backlog) but leaves process selection to practitioners.	PMBOK 8 reinstates ITTOs within process descriptions; models and methods remain available via PMIstandards+ but are not central to the guide.	Provides actionable guidance while maintaining flexibility.

3. Conceptual and Terminology Changes

3.1 Updated or redefined core terms

Term	PMBOK 7 Definition	PMBOK 8 Definition	Change & Rationale
Project	A temporary endeavor undertaken to create a unique product, service or result.	A temporary initiative in a unique context undertaken to create value. Characteristics include being temporary, having a unique context and driving organizational change.	Adds “unique context” and “value” to emphasise that projects exist within complex environments and should produce benefits rather than just deliverables.
Project Management	Application of knowledge, skills, tools and techniques to project activities to meet project requirements.	Application of knowledge, skills, tools and techniques to project activities to meet or exceed the intended value. Project management represents a mindset of proactive, ownership and value‑driven behaviours.	Shifts focus from requirements/scope to value delivery and benefits realisation. Introduces the concept of a project management mindset.
Value	Net quantifiable benefit derived from a business endeavour; may be tangible or intangible (explained via PGPG).	Excess of financial and non‑financial benefits over investment; value is contextual and perceived differently by stakeholders.	Clarifies that value may be qualitative and positions value at the core of project justification.
Governance	Not an explicit performance domain; governance discussed as part of organisational context and stakeholder engagement.	Defined as a performance domain that provides structures, processes, roles and decision‑making models to align project work with organisational strategy.	Elevates governance from background concept to a domain with dedicated processes and metrics, emphasising accountability and transparency.
Tailoring	A dedicated section emphasises why and how to tailor development approaches, processes and engagement.	Tailoring considerations appear in each performance domain and process. Focus is on context‑specific adjustments such as organisational culture, lifecycle selection and stakeholder needs.	Embeds tailoring guidance within each domain to encourage continuous adjustment rather than a one‑time activity.
Life Cycle	Discussion of predictive, adaptive, iterative, incremental and hybrid life cycles within the Development Approach & Life Cycle domain.	Describes project life cycles and development approaches within Project Life Cycles (Section 4) and integrates them with focus areas; emphasises delivering cadence and selection considerations.	Provides more actionable guidance on choosing and tailoring life cycles.

3.2 New or emphasised concepts in PMBOK 8

1. Value delivery and value‑focused outcomes. The eighth edition consistently links projects to organisational systems for value delivery. It emphasises that projects drive change from a current state to a future state to achieve value. Processes and governance structures support this objective.
2. Focus Areas vs. Performance Domains vs. Processes. PMBOK 8 introduces the concept of Project Management Focus Areas—Initiating, Planning, Executing, Monitoring & Controlling and Closing—reimagining the historical process groups as broad areas of work. Performance domains represent functional groupings (e.g., Scope, Schedule), and processes are specific activities with ITTOs. This tri‑layer structure integrates lifecycle, functional focus and action.
3. Expanded governance and metrics. The new Governance performance domain covers project value creation, governance models and metrics & mechanisms for effective project governance (e.g., leading/lagging indicators, measurement frameworks). It emphasises transparent decision‑making and accountability. Metrics and mechanisms are integrated into processes and tailoring guidance.
4. Sustainability and empowered culture. One of the six principles—Integrate Sustainability Within All Project Areas—highlights environmental and social stewardship. Another principle—Build an Empowered Culture—emphasises psychological safety, diversity and empowerment. These were absent or implicit in PMBOK 7.
5. AI and modern techniques. PMBOK 8 includes an appendix (X3) on artificial intelligence, exploring adoption strategies, ethical concerns and use cases (e.g., predictive analytics in risk management). PMBOK 7 made only passing references to emergent technologies.

3.3 Concepts downgraded, merged or removed

• Reduction of principles. The 12 principles of PMBOK 7 are condensed to six to reduce overlap and make them more actionable. Principles related to tailoring, complexity and risk are absorbed into the project management mindset and performance domains.
• Consolidation of performance domains. The Team, Project Work, Delivery, Measurement and Uncertainty domains of PMBOK 7 are merged into the new domains. For example, resource, stakeholder and team aspects now fall under the Resources and Stakeholders domains; measurement and uncertainty considerations are integrated into Governance, Scope, Schedule and Risk domains. The Development Approach & Life Cycle domain is incorporated into the Schedule domain and the life cycle guidance.
• Removal of Models, Methods and Artefacts section. PMBOK 7’s extensive catalogue of models, methods and artefacts is replaced by integrated ITTOs. Practitioners must consult PMIstandards+ for detailed techniques.
• Knowledge areas remain absent. There is no return to the 10 knowledge areas of PMBOK 6. Instead, PMBOK 8 maps knowledge‑area concepts to performance domains and processes.

4. Performance Domains, Focus Areas and Processes

4.1 PMBOK 7 performance domains (recap)

The eight performance domains in PMBOK 7 form a system of interactive capabilities rather than independent silos. They emphasise behavioural and systems thinking aspects rather than prescriptive tasks:

1. Stakeholder – identifies stakeholders, analyses their needs and plans engagements to build trust and alignment.
2. Team – focuses on developing, nurturing and leading high‑performing teams.
3. Development Approach & Life Cycle – discusses selecting predictive, adaptive or hybrid development approaches and aligning life cycle phases and cadence.
4. Planning – encourages continuous and outcome‑focused planning; emphasises iterative refinement rather than static baselines.
5. Project Work – covers delivery of outputs, managing tasks and establishing systems for execution.
6. Delivery – ensures that the product or outcome delivers value to stakeholders; emphasises product management and benefits realisation.
7. Measurement – promotes measurement to guide decisions and improve performance; focuses on outcomes rather than compliance.
8. Uncertainty – addresses risk, ambiguity and complexity; encourages adaptability and resilience.

Each domain describes purpose, context, key activities, tailoring considerations and measuring outcomes. There are no prescriptive processes; practitioners are encouraged to select appropriate models, methods and artefacts from the separate section.

4.2 PMBOK 8 Project Management Focus Areas and their relation to performance domains

PMBOK 8 reintroduces the five Project Management Process Groups as Focus Areas—Initiating, Planning, Executing, Monitoring & Controlling, and Closing. The Preface explains that historical process groups have been reimagined as Focus Areas because modern projects fulfil these concepts through multiple approaches and not solely through formal processes. Focus Areas provide a lifecycle lens and organise processes within performance domains:

• Initiating – establishes the project’s value proposition and secures authorisation; includes processes such as Initiate Project or Phase (development of the project charter).
• Planning – defines scope, schedule, finances, resources and risks; aligns the team; includes processes such as Plan Scope Management and Plan Schedule Management.
• Executing – delivers the work and manages resources; includes processes like Manage Project Execution and Manage Quality Assurance.
• Monitoring & Controlling – tracks performance, compares actual versus planned, and implements corrective actions; processes include Monitor and Control Project Work, Control Scope, Control Schedule.
• Closing – formalises acceptance and concludes activities; includes Close Project or Phase.

4.3 The 40 processes in PMBOK 8

PMBOK 8 introduces 40 non‑prescriptive processes across the seven performance domains. Unlike the 49 processes of earlier editions, these processes are adaptable and can be tailored to different development approaches. Each process includes Inputs, Tools & Techniques, Outputs (ITTOs) and Tailoring Considerations.

Organisation of processes:

• Governance domain (Initiating & Planning focus areas) – Processes such as Initiate Project or Phase, Integrate and Align Project Plans, and Define Governance Framework ensure the project aligns with organisational strategy, defines decision‑making structures and authorises work.
• Scope domain – Processes including Plan Scope Management, Collect Requirements, Define and Validate Scope and Control Scope provide systematic management of deliverables and boundaries.
• Schedule domain – Processes like Plan Schedule Management, Define Activities, Sequence Activities, Estimate Duration, Develop Schedule and Control Schedule maintain temporal coherence.
• Finance domain – Contains processes such as Plan Financial Resources, Estimate Costs, Determine Budget, Control Costs and Perform Financial Closure.
• Stakeholders domain – Processes include Plan Stakeholder Engagement, Identify Stakeholders, Manage Stakeholder Engagement and Monitor Engagement.
• Resources domain – Processes such as Plan Resource Management, Acquire Resources, Develop Team, Manage Team, Control Resources ensure people, materials and equipment are managed effectively.
• Risk domain – Processes include Plan Risk Management, Identify Risks, Analyse Risks, Plan Risk Responses, Implement Risk Responses and Monitor Risks.

These processes reflect modern practice and support both predictive and adaptive life cycles. For example, Plan Scope Management includes iterative backlog refinement in agile projects, while Develop Schedule may use rolling‑wave planning in hybrid contexts.

4.4 Mapping major areas from PMBOK 7 to PMBOK 8

The table below summarizes how key areas from PMBOK 7 map into the structure of PMBOK 8. It shows where 7th‑edition performance domains land within the 8th‑edition performance domains and focus areas. Many concepts are redistributed rather than directly renamed.

Major Area	PMBOK 7 (Domain/Section)	PMBOK 8 (Domain/Section)	Change in emphasis
Stakeholder	Stakeholder Performance Domain emphasised identification, analysis, engagement and outcome‑focused measurement.	Stakeholders Performance Domain plus processes (Identify Stakeholders, Plan Stakeholder Engagement, Manage Stakeholder Engagement, Monitor Engagement).	Introduces detailed processes and ITTOs; engagement planning is more structured; emphasis on value realisation and alignment.
Team / Resources	Team Performance Domain emphasised culture, leadership styles, high‑performing teams and tailoring leadership. Resource management appeared within the Project Work domain.	Resources Performance Domain consolidates people, materials, infrastructure and facilities, with processes for planning, acquiring, developing, managing and controlling resources.	Combines team and physical resource management; leadership and culture are addressed through the Build an Empowered Culture principle rather than a domain.
Development Approach & Life Cycle	Domain covered selection of predictive, adaptive or hybrid development approaches and aligning life cycles and cadences.	Incorporated into the Schedule Performance Domain and Section 4 (Project Life Cycles). Processes like Define Activities, Sequence Activities and Develop Schedule are used regardless of lifecycle.	Life cycle guidance is more detailed; schedule domain includes development approach considerations; focus areas reintroduce initiation and closure.
Planning	Planning Performance Domain focused on integrated planning, continuous refinement and outcome orientation.	Planning activities are distributed across performance domains (Scope, Schedule, Finance, Stakeholders, Resources, Risk) and processes within the Planning Focus Area.	Planning is no longer a single domain; instead, each domain has its own planning processes, and integrated planning is part of the Governance domain.
Project Work & Delivery	Project Work domain ensured tasks were executed effectively; Delivery domain emphasised product delivery and value realisation.	Execution‑related processes reside in the Executing Focus Area within each performance domain; value realisation is integrated into governance and stakeholder domains.	Delivery and measurement are absorbed into functional domains; emphasises value and benefits rather than separate delivery domain.
Measurement & Uncertainty	Measurement domain promoted outcome‑oriented metrics; Uncertainty domain covered risk, complexity and ambiguity.	Measurement activities are embedded within Governance, Scope, Schedule, Finance and Risk domains. Uncertainty is addressed primarily by the Risk Performance Domain; complexity is integrated into the holistic view principle.	Shifts measurement and risk considerations into functional areas; emphasises integrated metrics and risk management across domains.
Tailoring	Separate section on tailoring development approaches and performance domains.	Tailoring guidance embedded within each performance domain and process.	Encourages context‑specific adjustments at every level.
Models, Methods & Artefacts	Comprehensive catalogue of models, methods and artefacts.	Not included; practitioners refer to PMIstandards+ or other PMI resources for tools and techniques.	Replaces lists with integrated ITTOs; emphasises adaptable process toolkit.

5. Inputs, Tools & Techniques, Outputs (ITTOs) and Artefacts

5.1 ITTO treatment in PMBOK 7

Earlier editions of the PMBOK® Guide (through the Sixth Edition) provided detailed ITTO tables for each process. PMBOK 7 eliminated these tables and instead introduced a section on Models, Methods and Artefacts. This change emphasised that project success depends on selecting appropriate tools and techniques for the context rather than blindly following process inputs and outputs. Practitioners were encouraged to consult PMIstandards+ for detailed guidance.

5.2 ITTO integration in PMBOK 8

PMBOK 8 brings back ITTOs but with a non‑prescriptive orientation. Each of the 40 processes includes:

• Inputs: documents, agreements or environmental factors required to perform the process.
• Tools & Techniques: methods or approaches to transform inputs into outputs; may include data gathering, analysis, facilitation, decision making, interpersonal skills, project management information systems (PMIS) and AI‑enabled tools.
• Outputs: deliverables, plans, baselines or updates produced by the process. Outputs may feed into other processes or provide value directly.
• Tailoring Considerations: guidance on how to adjust the process based on organisational culture, lifecycle approach (predictive, adaptive, hybrid), complexity and stakeholder needs.

The ITTOs are integrated within performance domains rather than isolated tables. This integration illustrates how processes contribute to the domain’s purpose (e.g., the Schedule domain’s processes produce a baseline schedule and controlling metrics), and how outputs feed other processes. Tools and techniques now include modern data analytics, AI and collaboration platforms.

5.3 Representative process examples

To illustrate how PMBOK 8 processes relate to PMBOK 7 content, the following examples compare select processes with their historical context:

1. Initiate Project or Phase (Governance domain, Initiating focus area) – This process authorises a project or phase by creating the project charter. Inputs include business case, benefits management plan and agreements; tools & techniques include expert judgment, data gathering and facilitation; outputs include a project charter and stakeholder register. In PMBOK 7 the equivalent guidance existed implicitly within the Stakeholder and Planning domains and within models and artefacts (project charter). The PGPG describes Develop Project Charter and Identify Stakeholders as separate processes; PMBOK 8 consolidates the authorisation and stakeholder identification into the Governance domain.
2. Integrate and Align Project Plans (Governance domain, Planning focus area) – Aligns individual domain plans (scope, schedule, cost, quality, resources, procurement, stakeholder, risk) into a cohesive project management plan and ensures consistency with organisational governance. Tools include integrated change control and collaboration tools. In PMBOK 7, the Planning domain encouraged integrated and iterative planning but did not prescribe such a process; integration was addressed through the principle of tailoring and models (e.g., integrated planning models).
3. Plan Scope Management (Scope domain, Planning focus area) – Defines how scope will be defined, validated and controlled. Inputs include the project charter and organisational process assets; tools & techniques may include workshops, interviews and story‑mapping; outputs include a scope management plan and requirements management plan. PMBOK 7 treated scope planning within the Planning domain and referenced artefacts such as product backlog and requirement documents but provided no process detail.

These examples illustrate that PMBOK 8 reintegrates processes with ITTOs while encouraging adaptation. Practitioners should tailor each process to their context rather than use them as mandatory steps.

6. Tailoring, Governance and Life Cycle Approaches

6.1 Tailoring guidance

PMBOK 7. A dedicated tailoring section explains why tailoring is essential and how to tailor development approaches, processes and engagement. It provides a step‑by‑step tailoring process covering selection of life cycle, tailoring for organisation and project, and implementing ongoing improvement. The section encourages considering stakeholder needs, environment, organisational culture and governance structures.

PMBOK 8. Tailoring guidance is embedded within each performance domain and process description. For example, the Scope domain outlines tailoring questions such as: What level of detail is needed in a predictive vs. adaptive context? Should backlog refinement be continuous? Each process identifies factors influencing tool selection and process adaptation. Tailoring thus becomes a continuous, context‑driven activity, not a separate step. The integration encourages project teams to adjust practices as conditions evolve.

Practical implications. Practitioners must evaluate organisational culture, stakeholder expectations, risk tolerance and complexity at the onset and throughout the project. Tailoring decisions should be revisited at phase gates or retrospectives. PMOs should document tailoring rationale and create repositories of lessons learned to inform future projects.

6.2 Governance

PMBOK 7. Governance is discussed as part of organisational context and stakeholder engagement. It emphasises aligning projects with organisational strategy and defines project success criteria. However, governance is not a dedicated performance domain.

PMBOK 8. Governance becomes a full performance domain. It covers project value creation, governance models, metrics and mechanisms for effective project governance, and additional considerations for predictive environments. It emphasises that organisational governance provides direction and control through policies and decisions, whereas project governance is an adaptable framework guiding project management activities to create value, providing structures, systems, roles and decision‑making models. The domain emphasises transparency, ethical decision‑making, stakeholder alignment and benefits realisation.

Comparison. PMBOK 8 elevates governance from background concept to central focus. Practitioners must establish governance frameworks tailored to project size, complexity and organisational culture, and integrate them with portfolio and program governance. Governance should include clear accountability (e.g., RACI matrices), escalation paths, stage‑gate reviews and benefits monitoring.

6.3 Life cycle approaches: predictive, adaptive and hybrid

PMBOK 7. The Development Approach & Life Cycle domain discusses different life cycles (predictive, iterative, incremental, adaptive and hybrid) and stresses aligning the development approach with project objectives. It emphasises that no single approach is universally best and that tailoring is essential.

PMBOK 8. Section 4 (Project Life Cycles) and the Schedule performance domain provide detailed guidance on selecting development approaches and cadence. The guide explains predictive, adaptive and hybrid approaches, highlights considerations for selecting and tailoring them (e.g., requirements stability, stakeholder engagement, complexity and risk), and incorporates them into process descriptions. Focus areas emphasise that initiating and closing occur in all life cycles but may be iterative. The Governance domain includes additional considerations for predictive environments, recognising that heavily regulated projects may require more formal governance.

Comparison. PMBOK 8 offers more actionable guidance on choosing and tailoring life cycles and integrates these decisions into process planning and scheduling. Hybrid approaches are explicitly described with examples of predictive frameworks supplemented by adaptive increments.

7. Domain‑by‑Domain Detailed Comparison

The following sections compare each of PMBOK 8’s seven performance domains with related content in PMBOK 7. Each subsection summarises how coverage and emphasis have changed and provides a practical example illustrating how project manager behaviour may differ.

7.1 Governance

• PMBOK 7 coverage (Stakeholder, Team, Planning, Delivery domains). Governance concepts appear implicitly: project sponsors and boards are responsible for authorising projects, aligning work with organisational strategy and ensuring benefits realisation. Stakeholder and Planning domains discuss engaging sponsors and defining success criteria. However, governance structures and models are not elaborated.
• PMBOK 8 coverage. Governance is a dedicated performance domain. It addresses project value creation, governance models (structured vs. self‑governed), metrics and mechanisms for effective governance, and additional considerations for predictive environments. It prescribes processes such as Initiate Project or Phase, Integrate and Align Project Plans and Define Governance Framework, and includes tailoring advice.
• New/expanded/removed. Governance metrics (leading/lagging indicators), ethical considerations and sustainability are expanded. Governance structures may vary from hierarchical committees to self‑organising teams; PMBOK 8 emphasises choosing appropriate models.
• Practical example. A PMBOK 7 project manager launching an internal IT project might rely on an informal steering committee to approve major decisions. Under PMBOK 8, the manager would create a governance framework that specifies decision rights, escalation paths, metrics for value creation and benefits tracking; they would align the project with the organisation’s strategy and incorporate sustainability goals. Project initiation would involve developing a project charter with explicit value propositions and authorisation.

7.2 Scope

• PMBOK 7 coverage. Scope management is addressed implicitly in the Planning and Delivery domains; scope definition, validation and change control are part of planning activities. Specific processes are absent; instead, models and artefacts such as product backlog, scope statement and requirements documentation are referenced.
• PMBOK 8 coverage. Scope is a dedicated performance domain with processes like Plan Scope Management, Collect Requirements, Define Scope, Create WBS/Backlog, Validate Scope and Control Scope. It emphasises ensuring that deliverables contribute to the intended value and that scope changes are evaluated through governance structures. Tailoring guidance suggests using backlogs and MVPs in adaptive projects.
• New/expanded/removed. Detailed process descriptions and ITTOs return; backlog management is incorporated; scope validation and control emphasise stakeholder acceptance and value realisation.
• Practical example. In PMBOK 7, an agile software project might manage scope through backlog refinement guided by the Delivery domain. In PMBOK 8, the project manager formalises Plan Scope Management to define how backlog items will be prioritised based on value, uses Validate Scope to gain stakeholder acceptance at each increment and employs governance metrics to measure scope creep against value delivered.

7.3 Schedule

• PMBOK 7 coverage. Schedule considerations appear within the Planning domain; the Development Approach & Life Cycle domain discusses cadence and iterative planning. There are no process descriptions.
• PMBOK 8 coverage. The Schedule domain contains processes such as Plan Schedule Management, Define Activities, Sequence Activities, Estimate Durations, Develop Schedule and Control Schedule. It supports both predictive scheduling (network diagrams, critical path) and adaptive approaches (timeboxed iterations, rolling‑wave planning). Tailoring guidance addresses schedule approaches for complex or adaptive projects.
• Changes. Scheduling becomes more granular and integrated with resource and scope management.
• Practical example. A PMBOK 7 project manager might maintain a high‑level milestone chart and adjust it iteratively. Under PMBOK 8, the manager would produce a detailed schedule baseline, apply earned schedule or burndown metrics, and update the schedule via Control Schedule while communicating changes through the governance framework.

7.4 Finance

• PMBOK 7 coverage. Cost management is discussed within the Planning and Delivery domains but without prescriptive processes. Financial considerations appear in the Measurement domain as one of many outcomes metrics.
• PMBOK 8 coverage. Finance is a standalone domain. Processes include Plan Financial Resources, Estimate Costs, Determine Budget, Control Costs and Perform Financial Closure. The domain emphasises aligning budgets with strategic priorities and managing reserves. Tailoring guidance addresses funding models for adaptive projects and integrating finance with value realisation metrics.
• Changes. Cost management is elevated and integrated with value delivery; budgeting and forecasting become part of governance.
• Practical example. In PMBOK 7, budgeting may be handled by organisational finance outside the project manager’s control. PMBOK 8 requires the project manager to proactively plan financial resources, track cost performance and communicate variances to the governance body; agile projects may use continuous funding models with rolling budgets.

7.5 Stakeholders

• PMBOK 7 coverage. The Stakeholder domain emphasises identifying stakeholders, understanding interests, managing expectations and measuring engagement outcomes. It highlights co‑creation and influence patterns.
• PMBOK 8 coverage. Stakeholders remain a performance domain but now include specific processes: Identify Stakeholders, Plan Stakeholder Engagement, Manage Stakeholder Engagement and Monitor Engagement. Inputs include stakeholder registers and communication plans; tools include stakeholder analysis, persona development, empathy mapping and AI‑based sentiment analysis.
• Changes. Stakeholder engagement becomes more structured; processes emphasise continuous engagement, value alignment and integration with governance.
• Practical example. A PMBOK 7 practitioner might facilitate stakeholder workshops and update a stakeholder map occasionally. PMBOK 8 expects the project manager to maintain a stakeholder register, plan engagement strategies, execute them with appropriate tools (e.g., collaboration platforms) and monitor engagement metrics (sentiment, participation) to ensure stakeholders perceive value.

7.6 Resources

• PMBOK 7 coverage. Team performance and resource management appear in the Team domain and Project Work domain; they stress building high‑performing teams, tailoring leadership styles and ensuring resources are available.
• PMBOK 8 coverage. Resources are consolidated into a domain that covers human, material, infrastructure and facilities. Processes include Plan Resource Management, Estimate Resources, Acquire Resources, Develop Team, Manage Team, and Control Resources. The domain emphasises capacity planning, competency development, motivation, diversity and wellbeing.
• Changes. Distinguishes resource types; integrates team development with resource planning; includes control processes to track resource utilisation and adjust as needed.
• Practical example. In PMBOK 7, a project manager might rely on HR to assign resources and focus on team cohesion. PMBOK 8 requires the project manager to estimate resource needs, negotiate assignments, ensure training and equipment, manage team performance, and measure resource efficiency.

7.7 Risk

• PMBOK 7 coverage. Uncertainty domain addresses risk, ambiguity and complexity and promotes adapting to change. Risk management models (e.g., qualitative and quantitative analysis, risk response strategies) are suggested but not prescribed.
• PMBOK 8 coverage. Risk is a dedicated domain with processes: Plan Risk Management, Identify Risks, Perform Risk Analysis, Plan Risk Responses, Implement Risk Responses and Monitor Risks. The domain emphasises aligning risk responses with value objectives and integrating risk management into all focus areas. Tailoring guidance suggests scaling risk management based on project size and complexity and using AI tools for predictive analytics.
• Changes. Risk management becomes more systematic; processes and ITTOs provide guidance similar to earlier editions but integrated into the new structure.
• Practical example. In PMBOK 7, risk identification and response might be informal, with periodic risk reviews. Under PMBOK 8, the project manager sets up a risk register, performs probability‑impact assessments, defines responses, implements them as part of execution, and continuously monitors risks, adjusting based on metrics and stakeholder feedback.

8. Impact on Practitioners and Organisations

8.1 Adjustments for teams using PMBOK 7 today

1. Reorient around value. Practitioners must shift from completing deliverables to creating value. The project charter should articulate the value proposition; success criteria should include benefits realisation. Governance frameworks must track value metrics (e.g., ROI, customer satisfaction) beyond scope, schedule and cost.
2. Adopt the project management mindset. Teams should cultivate a proactive, ownership‑driven and value‑driven mindset. This involves systems thinking, continuous improvement and empowered leadership. Training should focus on soft skills, ethics and sustainability as much as technical skills.
3. Implement governance structures. Create clear governance frameworks specifying decision rights, accountability and escalation paths. Ensure alignment between organisational governance and project governance and integrate benefits tracking.
4. Integrate processes and tailoring. Adopt the 40 processes as a toolkit; select and adapt them based on project context. Document tailoring decisions and revisit them regularly.
5. Update templates and PMO methodologies. Modify project management plans, charters, schedules and reports to incorporate focus areas, performance domains, ITTOs and value metrics. Provide training on the new definitions and processes.
6. Engage stakeholders continuously. Use structured stakeholder engagement processes; monitor sentiment; ensure stakeholders perceive value.
7. Upgrade measurement and reporting. Implement metrics that link deliverables to benefits. Use dashboards that track value, governance metrics, sustainability indicators and stakeholder satisfaction.

8.2 How PMBOK 8 supports value‑driven and complex environments

• Holistic and sustainable focus. Integrating sustainability within all project areas and building an empowered culture ensure that projects address social and environmental considerations and enable team autonomy.
• Flexible yet actionable processes. The 40 processes provide structure without rigidity; they can be tailored for predictive, adaptive or hybrid projects. This supports complex environments where requirements evolve or stakeholders are diverse.
• Integrated governance and metrics. The Governance domain and the Finance domain incorporate performance measures that link to organisational strategy and benefits realisation. Projects can adapt metrics based on stakeholder needs and risk appetite.
• Modern tools and AI. Appendices discuss artificial intelligence and emerging technologies, encouraging adoption of predictive analytics, machine learning for risk identification and digital dashboards for stakeholder engagement.

8.3 Considerations for training, methodologies and PMO standards

1. Training material updates. Training providers should reframe curricula to emphasise value delivery, sustainability and the project management mindset. They should teach the 40 processes but stress tailoring and adaptability. Case studies should illustrate governance frameworks, value metrics and hybrid life cycles.
2. Organisational methodologies. PMOs should revise methodologies to incorporate performance domains, focus areas and processes. They should create governance templates, value management plans, integrated schedules and risk registers aligned with the new definitions.
3. Templates and standards. Update templates for project charters, management plans, backlogs, stakeholder registers and governance frameworks. Provide guidance on selecting lifecycle approaches and tailoring processes. Establish a repository of artefacts mapped to the 40 processes and ensure knowledge sharing through PMIstandards+ or internal libraries.

9. Summary Tables and Glossary

9.1 Comparative overview table

Below is a concise table summarising key concepts and their treatment in PMBOK 7 vs. PMBOK 8 with practical implications.

Concept	PMBOK 7 Treatment	PMBOK 8 Treatment	Practical Implication
Project definition	Temporary endeavour to create a unique product, service or result.	Temporary initiative in a unique context undertaken to create value.	Requires explicit articulation of value proposition; success measured by benefits.
Project management definition	Application of knowledge, skills, tools and techniques to meet project requirements.	Application of knowledge, skills, tools and techniques to meet or exceed intended value.	Encourages value‑driven decision making and discourages scope creep or gold plating.
Principles	Twelve principles emphasising stewardship, team collaboration, stakeholder engagement, tailoring, quality, risk, adaptability, etc..	Six principles focusing on holistic view, value, quality, accountable leadership, sustainability and empowered culture.	Streamlines guidance; emphasises sustainability and culture.
Performance domains	Eight domains: Stakeholder, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.	Seven domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk.	Moves from behavioural/system focus to functional focus; measurement and uncertainty integrated into other domains.
Process groups / focus areas	Not included in PMBOK 7; process groups described separately in PGPG.	Five Focus Areas reintroducing Initiating, Planning, Executing, Monitoring & Controlling, Closing.	Provides lifecycle structure; easier mapping for practitioners familiar with earlier editions.
Processes & ITTOs	No process tables; models, methods and artefacts section.	40 non‑prescriptive processes with integrated ITTOs.	Offers actionable guidance; encourages adaptation to context.
Governance	Covered implicitly through stakeholder and planning domains; not a domain.	Dedicated Governance domain with processes, metrics and tailoring guidance.	Emphasises strategic alignment, transparency and accountability.
Tailoring	Separate section covering why and how to tailor.	Tailoring advice embedded into each performance domain and process.	Encourages continuous context‑specific adaptation.
Life cycle guidance	Development Approach & Life Cycle domain discusses predictive, adaptive and hybrid approaches.	Life cycle guidance integrated into Schedule domain and Section 4; focus areas emphasise iterative nature.	Provides more actionable selection criteria and integration with processes.
Models, methods & artefacts	Extensive catalogue provided.	Not included; ITTOs integrated into processes.	Practitioners rely on PMIstandards+ or external resources for tools and techniques.

9.2 Glossary of selected new or redefined terms

Term	Definition in PMBOK 8	Notes
Project	A temporary initiative in a unique context undertaken to create value.	Emphasises value and context.
Project management	Application of knowledge, skills, tools and techniques to meet or exceed the intended value.	Focuses on value rather than requirements.
Value	The excess of financial and non‑financial benefits over investment. Value is perceived differently by stakeholders.	Underpins project justification and success measurement.
Governance	Framework of structures, systems, roles and decision‑making models to align project with organisational strategy.	Includes project value creation, governance models and metrics.
Focus Area	One of five lifecycle‑oriented groupings—Initiating, Planning, Executing, Monitoring & Controlling, Closing—reintroduced to organise processes.	Replaces the term “process group” and emphasises that actions may occur iteratively.
Performance Domain	A group of related activities within which the project team focuses to achieve an aspect of project performance (Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk).	Replaces the 8th edition’s behavioural domains; integrated with processes and ITTOs.
Tailoring	Adjusting methods, processes and artefacts to fit the project and organisational context; appears in each domain/process description.	No longer a separate section; encourages continuous adaptation.

10. Conclusion

The evolution from PMBOK 7 to PMBOK 8 reflects a maturation of the project management discipline from prescriptive process adherence to value‑oriented practice. PMBOK 7 introduced a principles‑based, outcomes‑focused framework that emphasised flexibility, systems thinking and tailoring. PMBOK 8 builds on this foundation by:

• Reinforcing value and benefits. Projects are now defined by the value they create, and project management must meet or exceed intended value. This shift requires project managers to engage stakeholders early, articulate value propositions and measure outcomes beyond traditional constraints.
• Simplifying principles and integrating sustainability. Six principles encapsulate the project management mindset—holistic view, value focus, quality, accountable leadership, sustainability and empowered culture. Sustainability and empowerment reflect broader social expectations and emphasise ethical, inclusive practices.
• Reintroducing process structure through focus areas. The five focus areas provide a familiar lifecycle structure while maintaining adaptability. Forty non‑prescriptive processes with integrated ITTOs offer actionable guidance tailored to varied approaches.
• Aligning performance domains with organisational functions. Seven performance domains emphasise governance, scope, schedule, finance, stakeholders, resources and risk, aligning project management with organisational departments and enabling integrated governance and value management.

Next steps for practitioners and PMOs:

1. Reevaluate project methodologies and templates to align with the new definitions, principles, domains and processes. Incorporate value statements, governance frameworks and sustainability considerations into project charters and plans.
2. Train project teams and stakeholders on the project management mindset, focusing on proactive behaviours, ownership and value‑driven decision making. Encourage continuous learning and adaptation.
3. Implement integrated governance structures that support transparent decision making, benefits tracking and ethical practices. Use metrics and dashboards to monitor value, sustainability and stakeholder satisfaction.
4. Adopt flexible processes and tailoring, leveraging the 40 processes as a toolkit rather than a checklist. Document tailoring decisions and share lessons learned across the organisation.
5. Engage with PMIstandards+ and emerging technologies to access updated models, methods, artefacts and AI‑enabled tools that complement the guide.

By embracing these changes, project professionals can deliver projects that not only meet traditional performance constraints but also maximise value and sustainability for stakeholders and organisations.