{"id":1894,"date":"2025-12-06T03:15:03","date_gmt":"2025-12-06T03:15:03","guid":{"rendered":"https:\/\/hksmnow.com\/project-management\/?p=1894"},"modified":"2026-04-19T20:16:13","modified_gmt":"2026-04-19T20:16:13","slug":"pmbok-7-vs-pmbok-8-comprehensive-comparison-report","status":"publish","type":"post","link":"https:\/\/hksmnow.com\/project-management\/pmbok-and-standards\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/","title":{"rendered":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"executive-summary\">1. Executive Summary<\/h2>\n\n\n\n<p>Projects underpin modern value creation. The&nbsp;<strong>Project Management Body of Knowledge (PMBOK\u00ae)<\/strong>&nbsp;has long served as the reference for how projects should be managed. The&nbsp;<strong>Seventh Edition<\/strong>&nbsp;(2021) represented a radical shift away from prescriptive processes to a principles\u2011 and outcomes\u2011focused model with eight performance domains. The&nbsp;<strong>Eighth Edition<\/strong>&nbsp;(2025) continues the evolution but&nbsp;<strong>reintroduces process groups<\/strong>&nbsp;as&nbsp;<em>Focus Areas<\/em>&nbsp;and integrates a set of&nbsp;<strong>40 non\u2011prescriptive processes<\/strong>, while consolidating principles and reorganising performance domains. The changes aim to make the guide more&nbsp;<strong>value\u2011driven<\/strong>,&nbsp;<strong>actionable<\/strong>&nbsp;and&nbsp;<strong>globally accessible<\/strong>.<\/p>\n\n\n\n<p><strong>Main conceptual shift:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>From output centric to value centric.<\/strong>\u00a0PMBOK\u00a07 defined a project as \u201ca temporary endeavor undertaken to create a unique product, service, or result\u201d. PMBOK\u00a08 reframes a project as a \u201ctemporary initiative in a unique context undertaken to\u00a0<strong>create value<\/strong>\u201d. \u201cProject management\u201d moves from meeting project requirements to \u201cthe application of knowledge, skills, tools and techniques to project activities\u00a0<strong>to meet or exceed the intended value<\/strong>\u201d. The eighth edition emphasises\u00a0<em>value delivery<\/em>\u00a0and\u00a0<em>benefits realisation<\/em>\u00a0rather than merely completing scope within constraints.<\/li>\n\n\n\n<li><strong>Principles and mindset.<\/strong>\u00a0PMBOK\u00a07 introduced\u00a0<strong>12 project management principles<\/strong>\u00a0(e.g., be a diligent steward, tailor based on context, navigate complexity). PMBOK\u00a08 simplifies these into\u00a0<strong>six principles<\/strong>\u00a0organised around a\u00a0<strong>project management mindset<\/strong>\u00a0with three dimensions (proactive, ownership and value\u2011driven). The new principles include\u00a0<em>Adopt a Holistic View<\/em>,\u00a0<em>Focus on Value<\/em>,\u00a0<em>Embed Quality Into Processes and Deliverables<\/em>,\u00a0<em>Be an Accountable Leader<\/em>,\u00a0<em>Integrate Sustainability Within All Project Areas<\/em>, and\u00a0<em>Build an Empowered Culture<\/em>. These principles encourage proactive leadership, sustainability and empowerment of teams.<\/li>\n\n\n\n<li><strong>From knowledge areas to performance domains and focus areas.<\/strong>\u00a0PMBOK\u00a07 abandoned the 10 knowledge areas of earlier editions and introduced\u00a0<strong>eight performance domains<\/strong>\u00a0(Stakeholder, Team, Development Approach &amp; Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty). PMBOK\u00a08 reorganises these into\u00a0<strong>seven performance domains<\/strong>\u2014Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk\u2014aligned with organisational functions. It also reintroduces the five\u00a0<strong>Project Management Process Groups<\/strong>\u00a0as\u00a0<strong>Focus Areas<\/strong>\u00a0(Initiating, Planning, Executing, Monitoring &amp; Controlling, Closing) to provide a lifecycle lens.<\/li>\n\n\n\n<li><strong>Integration of processes and ITTOs.<\/strong>\u00a0PMBOK\u00a07 removed detailed process descriptions and ITTOs (inputs, tools &amp; techniques, outputs), instead listing models, methods and artefacts. PMBOK\u00a08 brings back\u00a0<strong>40 non\u2011prescriptive processes<\/strong>; each process includes ITTOs and tailoring advice within its associated performance domain. This reintegration gives practitioners actionable guidance while maintaining flexibility.<\/li>\n<\/ul>\n\n\n\n<p><strong>Key structural changes:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Aspect<\/th><th>PMBOK&nbsp;7<\/th><th>PMBOK&nbsp;8<\/th><th>Implications<\/th><\/tr><\/thead><tbody><tr><td><strong>Purpose\/Scope<\/strong><\/td><td>Principles\u2011based standard with eight performance domains, focusing on&nbsp;<em>why<\/em>&nbsp;and&nbsp;<em>what<\/em>&nbsp;rather than&nbsp;<em>how<\/em>. Models, methods and artefacts replace ITTOs.<\/td><td>Retains a principles\u2011based standard but simplifies to six principles and seven performance domains. Reintroduces processes and ITTOs through focus areas.<\/td><td>Practitioners must now balance a value\u2011driven mindset with practical processes and outputs.<\/td><\/tr><tr><td><strong>Definitions<\/strong><\/td><td>Project: temporary endeavour to produce a unique outcome. Project management: application of knowledge, skills, tools and techniques to meet project requirements.<\/td><td>Project: temporary initiative in a unique context undertaken to create value. Project management: application of knowledge, skills, tools and techniques to meet or&nbsp;<strong>exceed intended value<\/strong>.<\/td><td>Aligns project work with organisational strategy and benefits realisation.<\/td><\/tr><tr><td><strong>Principles<\/strong><\/td><td>12 principles emphasising stewardship, team collaboration, stakeholder engagement, value focus, systems thinking, leadership behaviours, tailoring, quality, complexity, risk responses, adaptability, and change enablement.<\/td><td>Six principles organised around a project management mindset; emphasises holistic view, value focus, quality, accountable leadership, sustainability, and empowered culture.<\/td><td>Principles are streamlined for clarity; sustainability and empowerment gain prominence.<\/td><\/tr><tr><td><strong>Performance Domains<\/strong><\/td><td>Eight domains: Stakeholder, Team, Development Approach &amp; Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.<\/td><td>Seven domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk. Each includes tailored processes and ITTOs.<\/td><td>Domains shift from behavioural\/system\u2011oriented to functional groupings; measurement and uncertainty are absorbed into governance, scope, schedule and risk.<\/td><\/tr><tr><td><strong>Process Groups \/ Focus Areas<\/strong><\/td><td>Process groups removed; 7th edition emphasises continuous flow rather than sequential groups.<\/td><td>Five Focus Areas (Initiating, Planning, Executing, Monitoring &amp; Controlling, Closing) reintroduce the lifecycle perspective.<\/td><td>Provides familiar structure for practitioners using older editions; facilitates mapping to organisational lifecycles.<\/td><\/tr><tr><td><strong>Processes &amp; ITTOs<\/strong><\/td><td>No process or ITTO tables; guidance on models, methods and artefacts.<\/td><td>40 non\u2011prescriptive processes each with inputs, tools, techniques and outputs; tailored within performance domains.<\/td><td>Offers actionable guidance while emphasising adaptability.<\/td><\/tr><tr><td><strong>Tailoring Guidance<\/strong><\/td><td>Dedicated section on tailoring development approaches, processes, and artefacts.<\/td><td>Tailoring considerations integrated into each performance domain and process.<\/td><td>Tailoring is more embedded and context\u2011specific.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Implications for practitioners and organisations:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Adopt a value\u2011driven mindset.<\/strong>\u00a0Projects 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.<\/li>\n\n\n\n<li><strong>Integrate processes with principles.<\/strong>\u00a0While PMBOK\u00a07 encouraged flexibility through principles, PMBOK\u00a08 provides actionable processes. Practitioners should select and tailor the 40 processes based on context, using performance domains as a framework.<\/li>\n\n\n\n<li><strong>Strengthen governance and sustainability.<\/strong>\u00a0The addition of a Governance performance domain emphasises transparent decision\u2011making and alignment with organisational strategy. Sustainability is now a core principle; projects should consider environmental and social impacts.<\/li>\n\n\n\n<li><strong>Recalibrate organisational methodologies and training.<\/strong>\u00a0PMOs and training programs built around PMBOK\u00a06\/7 must update templates, plans and curricula to reflect focus areas, performance domains and the new definitions.<\/li>\n\n\n\n<li><strong>Embrace hybrid and adaptive approaches.<\/strong>\u00a0PMBOK\u00a08 retains guidance for predictive, adaptive and hybrid lifecycles; practitioners should tailor process use accordingly and leverage the integrated tailoring advice.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"highlevel-structural-comparison\">2. High\u2011Level Structural Comparison<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"overall-architecture-of-pmbok-7\">2.1 Overall architecture of PMBOK&nbsp;7<\/h3>\n\n\n\n<p>The&nbsp;<strong>Seventh Edition<\/strong>&nbsp;comprises two main parts:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>The Standard for Project Management.<\/strong>\u00a0This part defines core concepts and the conditions for effective project management. It is principles\u2011based rather than prescriptive. It introduces\u00a0<strong>12 principles<\/strong>\u00a0(Section\u00a03) and explains how they guide behaviours and decisions. The standard also highlights a\u00a0<strong>system of value delivery<\/strong>, linking projects, programs, portfolios, products and operations. Foundational terms are defined (project, project management, project manager, PMO, value).<\/li>\n\n\n\n<li><strong>A Guide to the Project Management Body of Knowledge (PMBOK Guide).<\/strong>\u00a0The guide is divided into three main sections:\n<ul class=\"wp-block-list\">\n<li><strong>Project Performance Domains.<\/strong>\u00a0Eight interrelated domains\u2014Stakeholder, Team, Development Approach &amp; Life Cycle, Planning, Project Work, Delivery, Measurement and Uncertainty\u2014provide a systems view of project management. Each domain describes purpose, key activities, interactions and outcomes rather than prescribing processes.<\/li>\n\n\n\n<li><strong>Tailoring.<\/strong>\u00a0A 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.<\/li>\n\n\n\n<li><strong>Models, Methods and Artefacts.<\/strong>\u00a0Instead 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.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"overall-architecture-of-pmbok-8\">2.2 Overall architecture of PMBOK&nbsp;8<\/h3>\n\n\n\n<p>The&nbsp;<strong>Eighth Edition<\/strong>&nbsp;retains a dual structure\u2014a&nbsp;<strong>standard<\/strong>&nbsp;and a&nbsp;<strong>guide<\/strong>\u2014but modifies both:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>The Standard for Project Management.<\/strong>\u00a0The standard continues to define the environment for project work. Key updates include:\n<ul class=\"wp-block-list\">\n<li><strong>Updated definitions.<\/strong>\u00a0A project is now a temporary initiative \u201cundertaken to create value\u201d. 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.<\/li>\n\n\n\n<li><strong>Six principles and a project management mindset.<\/strong>\u00a0Section\u00a03 introduces six principles aligned with three dimensions (proactive, ownership, value\u2011driven). Each principle includes\u00a0<em>project impact<\/em>,\u00a0<em>principle in action<\/em>\u00a0and\u00a0<em>connected performance domains<\/em>\u00a0sub\u2011sections. Sustainability and empowered culture are explicitly addressed, reflecting societal expectations.<\/li>\n\n\n\n<li><strong>System for value delivery.<\/strong>\u00a0The standard expands on how projects fit into a broader value delivery system, emphasising portfolio alignment and benefits realisation.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>PMBOK Guide\u2014Eighth Edition.<\/strong>\u00a0Major structural elements include:\n<ul class=\"wp-block-list\">\n<li><strong>Project Management Performance Domains (Section\u00a02).<\/strong>\u00a0Seven domains\u2014Governance, Scope, Schedule, Finance, Stakeholders, Resources and Risk\u2014organise project activities by functional focus. Each domain contains\u00a0<strong>key concepts<\/strong>,\u00a0<strong>processes<\/strong>,\u00a0<strong>tailoring considerations<\/strong>,\u00a0<strong>interactions with other domains<\/strong>, and\u00a0<strong>check results<\/strong>\u00a0subsections.<\/li>\n\n\n\n<li><strong>Project Management Focus Areas (Section\u00a04.5).<\/strong>\u00a0The five Focus Areas\u2014Initiating, Planning, Executing, Monitoring and Controlling, Closing\u2014reintroduce the lifecycle orientation removed in PMBOK\u00a07. They provide a structure for grouping processes and emphasise that each focus area may occur iteratively in adaptive environments.<\/li>\n\n\n\n<li><strong>Processes and ITTOs.<\/strong>\u00a0The guide enumerates\u00a0<strong>40 non\u2011prescriptive processes<\/strong>\u00a0adapted 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 &amp; techniques, outputs and tailoring guidance.<\/li>\n\n\n\n<li><strong>Integration with the Standard.<\/strong>\u00a0The principles inform the processes and domains; the guide cross\u2011references principles to show how each performance domain contributes to the project management mindset (e.g., the\u00a0<strong>Be an Accountable Leader<\/strong>\u00a0principle\u2019s connected performance domains include governance, scope, schedule and finance).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"integration-of-principles-performance-domains-and-processes\">2.3 Integration of principles, performance domains and processes<\/h3>\n\n\n\n<p>PMBOK&nbsp;8 explicitly integrates its components:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Principles inform processes and domains.<\/strong>\u00a0Each principle section lists\u00a0<strong>connected performance domains<\/strong>\u00a0and 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.<\/li>\n\n\n\n<li><strong>Performance domains host processes.<\/strong>\u00a0Within each domain, relevant processes (from the set of 40) are described along with ITTOs. For example, the\u00a0<strong>Governance Performance Domain<\/strong>\u00a0includes processes such as\u00a0<em>Initiate Project or Phase<\/em>\u00a0and\u00a0<em>Integrate and Align Project Plans<\/em>\u00a0(mapped to the Initiating and Planning focus areas).<\/li>\n\n\n\n<li><strong>Focus areas provide lifecycle context.<\/strong>\u00a0Processes are also grouped into the five focus areas, emphasising the iterative nature of project work. For instance,\u00a0<em>Plan Scope Management<\/em>\u00a0falls within the Planning focus area but is associated with the\u00a0<strong>Scope Performance Domain<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"evolution-of-process-groups-knowledge-areas-and-performance-domains\">2.4 Evolution of process groups, knowledge areas and performance domains<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Element<\/th><th>PMBOK&nbsp;7 Treatment<\/th><th>PMBOK&nbsp;8 Treatment<\/th><th>How it evolved<\/th><\/tr><\/thead><tbody><tr><td><strong>Process Groups<\/strong><\/td><td>Removed from PMBOK&nbsp;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 &amp; Controlling and Closing groups.<\/td><td><strong>Reintroduced as Focus Areas<\/strong>&nbsp;with five lifecycle\u2011oriented categories\u2014Initiating, Planning, Executing, Monitoring &amp; Controlling, Closing.<\/td><td>Gives practitioners a familiar lifecycle lens and allows mapping of the 40 processes to specific phases.<\/td><\/tr><tr><td><strong>Knowledge Areas<\/strong><\/td><td>Eliminated; knowledge areas from earlier editions were replaced by performance domains emphasising outcomes and interactions.<\/td><td>Knowledge areas do not return. Their content is synthesised into the seven performance domains; for example,&nbsp;<strong>Scope<\/strong>,&nbsp;<strong>Schedule<\/strong>&nbsp;and&nbsp;<strong>Finance<\/strong>&nbsp;domains absorb scope, time and cost knowledge areas respectively.<\/td><td>Aligns project management with organisational functions and reduces redundancy.<\/td><\/tr><tr><td><strong>Performance Domains<\/strong><\/td><td>Eight domains focusing on behaviours and systems: Stakeholder, Team, Development Approach &amp; Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.<\/td><td>Seven domains focusing on functional areas: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk. Domains include key concepts, processes and tailoring considerations.<\/td><td>Consolidates delivery, measurement and uncertainty into governance, scope, schedule and risk; introduces Governance domain to emphasise strategic alignment and transparency.<\/td><\/tr><tr><td><strong>Models, Methods &amp; Artefacts vs.&nbsp;ITTOs<\/strong><\/td><td>PMBOK&nbsp;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.<\/td><td>PMBOK&nbsp;8 reinstates ITTOs within process descriptions; models and methods remain available via PMIstandards+ but are not central to the guide.<\/td><td>Provides actionable guidance while maintaining flexibility.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"conceptual-and-terminology-changes\">3. Conceptual and Terminology Changes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"updated-or-redefined-core-terms\">3.1 Updated or redefined core terms<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Term<\/th><th>PMBOK&nbsp;7 Definition<\/th><th>PMBOK&nbsp;8 Definition<\/th><th>Change &amp; Rationale<\/th><\/tr><\/thead><tbody><tr><td><strong>Project<\/strong><\/td><td>A&nbsp;<strong>temporary endeavor<\/strong>&nbsp;undertaken to create a&nbsp;<strong>unique product, service or result<\/strong>.<\/td><td>A&nbsp;<strong>temporary initiative in a unique context<\/strong>&nbsp;undertaken to&nbsp;<strong>create value<\/strong>. Characteristics include being temporary, having a unique context and driving organizational change.<\/td><td>Adds \u201cunique context\u201d and \u201cvalue\u201d to emphasise that projects exist within complex environments and should produce benefits rather than just deliverables.<\/td><\/tr><tr><td><strong>Project Management<\/strong><\/td><td>Application of knowledge, skills, tools and techniques to project activities to&nbsp;<strong>meet project requirements<\/strong>.<\/td><td>Application of knowledge, skills, tools and techniques to project activities to&nbsp;<strong>meet or exceed the intended value<\/strong>. Project management represents a mindset of proactive, ownership and value\u2011driven behaviours.<\/td><td>Shifts focus from requirements\/scope to value delivery and benefits realisation. Introduces the concept of a project management mindset.<\/td><\/tr><tr><td><strong>Value<\/strong><\/td><td>Net quantifiable benefit derived from a business endeavour; may be tangible or intangible (explained via PGPG).<\/td><td>Excess of financial and non\u2011financial benefits over investment; value is contextual and perceived differently by stakeholders.<\/td><td>Clarifies that value may be qualitative and positions value at the core of project justification.<\/td><\/tr><tr><td><strong>Governance<\/strong><\/td><td>Not an explicit performance domain; governance discussed as part of organisational context and stakeholder engagement.<\/td><td>Defined as a performance domain that provides structures, processes, roles and decision\u2011making models to align project work with organisational strategy.<\/td><td>Elevates governance from background concept to a domain with dedicated processes and metrics, emphasising accountability and transparency.<\/td><\/tr><tr><td><strong>Tailoring<\/strong><\/td><td>A dedicated section emphasises why and how to tailor development approaches, processes and engagement.<\/td><td>Tailoring considerations appear in each performance domain and process. Focus is on context\u2011specific adjustments such as organisational culture, lifecycle selection and stakeholder needs.<\/td><td>Embeds tailoring guidance within each domain to encourage continuous adjustment rather than a one\u2011time activity.<\/td><\/tr><tr><td><strong>Life Cycle<\/strong><\/td><td>Discussion of predictive, adaptive, iterative, incremental and hybrid life cycles within the Development Approach &amp; Life Cycle domain.<\/td><td>Describes project life cycles and development approaches within&nbsp;<strong>Project Life Cycles<\/strong>&nbsp;(Section&nbsp;4) and integrates them with focus areas; emphasises delivering cadence and selection considerations.<\/td><td>Provides more actionable guidance on choosing and tailoring life cycles.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"new-or-emphasised-concepts-in-pmbok-8\">3.2 New or emphasised concepts in PMBOK&nbsp;8<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Value delivery and value\u2011focused outcomes.<\/strong>\u00a0The 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.<\/li>\n\n\n\n<li><strong>Focus Areas vs.\u00a0Performance Domains vs.\u00a0Processes.<\/strong>\u00a0PMBOK\u00a08 introduces the concept of\u00a0<em>Project Management Focus Areas<\/em>\u2014Initiating, Planning, Executing, Monitoring &amp; Controlling and Closing\u2014reimagining the historical process groups as broad areas of work.\u00a0<em>Performance domains<\/em>\u00a0represent functional groupings (e.g., Scope, Schedule), and\u00a0<em>processes<\/em>\u00a0are specific activities with ITTOs. This tri\u2011layer structure integrates lifecycle, functional focus and action.<\/li>\n\n\n\n<li><strong>Expanded governance and metrics.<\/strong>\u00a0The new Governance performance domain covers project value creation, governance models and metrics &amp; mechanisms for effective project governance (e.g., leading\/lagging indicators, measurement frameworks). It emphasises transparent decision\u2011making and accountability. Metrics and mechanisms are integrated into processes and tailoring guidance.<\/li>\n\n\n\n<li><strong>Sustainability and empowered culture.<\/strong>\u00a0One of the six principles\u2014<em>Integrate Sustainability Within All Project Areas<\/em>\u2014highlights environmental and social stewardship. Another principle\u2014<em>Build an Empowered Culture<\/em>\u2014emphasises psychological safety, diversity and empowerment. These were absent or implicit in PMBOK\u00a07.<\/li>\n\n\n\n<li><strong>AI and modern techniques.<\/strong>\u00a0PMBOK\u00a08 includes an appendix (X3) on artificial intelligence, exploring adoption strategies, ethical concerns and use cases (e.g., predictive analytics in risk management). PMBOK\u00a07 made only passing references to emergent technologies.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"concepts-downgraded-merged-or-removed\">3.3 Concepts downgraded, merged or removed<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduction of principles.<\/strong>\u00a0The 12 principles of PMBOK\u00a07 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.<\/li>\n\n\n\n<li><strong>Consolidation of performance domains.<\/strong>\u00a0The Team, Project Work, Delivery, Measurement and Uncertainty domains of PMBOK\u00a07 are merged into the new domains. For example, resource, stakeholder and team aspects now fall under the\u00a0<strong>Resources<\/strong>\u00a0and\u00a0<strong>Stakeholders<\/strong>\u00a0domains; measurement and uncertainty considerations are integrated into\u00a0<strong>Governance<\/strong>,\u00a0<strong>Scope<\/strong>,\u00a0<strong>Schedule<\/strong>\u00a0and\u00a0<strong>Risk<\/strong>\u00a0domains. The\u00a0<strong>Development Approach &amp; Life Cycle<\/strong>\u00a0domain is incorporated into the\u00a0<strong>Schedule<\/strong>\u00a0domain and the life cycle guidance.<\/li>\n\n\n\n<li><strong>Removal of Models, Methods and Artefacts section.<\/strong>\u00a0PMBOK\u00a07\u2019s extensive catalogue of models, methods and artefacts is replaced by integrated ITTOs. Practitioners must consult PMIstandards+ for detailed techniques.<\/li>\n\n\n\n<li><strong>Knowledge areas remain absent.<\/strong>\u00a0There is no return to the 10 knowledge areas of PMBOK\u00a06. Instead, PMBOK\u00a08 maps knowledge\u2011area concepts to performance domains and processes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"performance-domains-focus-areas-and-processes\">4. Performance Domains, Focus Areas and Processes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"pmbok-7-performance-domains-recap\">4.1 PMBOK&nbsp;7 performance domains (recap)<\/h3>\n\n\n\n<p>The eight performance domains in PMBOK&nbsp;7 form a&nbsp;<strong>system of interactive capabilities<\/strong>&nbsp;rather than independent silos. They emphasise behavioural and systems thinking aspects rather than prescriptive tasks:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Stakeholder<\/strong>\u00a0\u2013 identifies stakeholders, analyses their needs and plans engagements to build trust and alignment.<\/li>\n\n\n\n<li><strong>Team<\/strong>\u00a0\u2013 focuses on developing, nurturing and leading high\u2011performing teams.<\/li>\n\n\n\n<li><strong>Development Approach &amp; Life Cycle<\/strong>\u00a0\u2013 discusses selecting predictive, adaptive or hybrid development approaches and aligning life cycle phases and cadence.<\/li>\n\n\n\n<li><strong>Planning<\/strong>\u00a0\u2013 encourages continuous and outcome\u2011focused planning; emphasises iterative refinement rather than static baselines.<\/li>\n\n\n\n<li><strong>Project Work<\/strong>\u00a0\u2013 covers delivery of outputs, managing tasks and establishing systems for execution.<\/li>\n\n\n\n<li><strong>Delivery<\/strong>\u00a0\u2013 ensures that the product or outcome delivers value to stakeholders; emphasises product management and benefits realisation.<\/li>\n\n\n\n<li><strong>Measurement<\/strong>\u00a0\u2013 promotes measurement to guide decisions and improve performance; focuses on outcomes rather than compliance.<\/li>\n\n\n\n<li><strong>Uncertainty<\/strong>\u00a0\u2013 addresses risk, ambiguity and complexity; encourages adaptability and resilience.<\/li>\n<\/ol>\n\n\n\n<p>Each domain describes&nbsp;<strong>purpose<\/strong>,&nbsp;<strong>context<\/strong>,&nbsp;<strong>key activities<\/strong>,&nbsp;<strong>tailoring considerations<\/strong>&nbsp;and&nbsp;<strong>measuring outcomes<\/strong>. There are no prescriptive processes; practitioners are encouraged to select appropriate models, methods and artefacts from the separate section.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"pmbok-8-project-management-focus-areas-and-their-relation-to-performance-domains\">4.2 PMBOK&nbsp;8 Project Management Focus Areas and their relation to performance domains<\/h3>\n\n\n\n<p>PMBOK&nbsp;8 reintroduces the five&nbsp;<strong>Project Management Process Groups<\/strong>&nbsp;as&nbsp;<strong>Focus Areas<\/strong>\u2014Initiating, Planning, Executing, Monitoring &amp; Controlling, and Closing. The&nbsp;<strong>Preface<\/strong>&nbsp;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&nbsp;<strong>lifecycle lens<\/strong>&nbsp;and organise processes within performance domains:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Initiating<\/strong>\u00a0\u2013 establishes the project\u2019s value proposition and secures authorisation; includes processes such as\u00a0<em>Initiate Project or Phase<\/em>\u00a0(development of the project charter).<\/li>\n\n\n\n<li><strong>Planning<\/strong>\u00a0\u2013 defines scope, schedule, finances, resources and risks; aligns the team; includes processes such as\u00a0<em>Plan Scope Management<\/em>\u00a0and\u00a0<em>Plan Schedule Management<\/em>.<\/li>\n\n\n\n<li><strong>Executing<\/strong>\u00a0\u2013 delivers the work and manages resources; includes processes like\u00a0<em>Manage Project Execution<\/em>\u00a0and\u00a0<em>Manage Quality Assurance<\/em>.<\/li>\n\n\n\n<li><strong>Monitoring &amp; Controlling<\/strong>\u00a0\u2013 tracks performance, compares actual versus planned, and implements corrective actions; processes include\u00a0<em>Monitor and Control Project Work<\/em>,\u00a0<em>Control Scope<\/em>,\u00a0<em>Control Schedule<\/em>.<\/li>\n\n\n\n<li><strong>Closing<\/strong>\u00a0\u2013 formalises acceptance and concludes activities; includes\u00a0<em>Close Project or Phase<\/em>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"the-40-processes-in-pmbok-8\">4.3 The 40 processes in PMBOK&nbsp;8<\/h3>\n\n\n\n<p>PMBOK&nbsp;8 introduces&nbsp;<strong>40 non\u2011prescriptive processes<\/strong>&nbsp;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&nbsp;<strong>Inputs<\/strong>,&nbsp;<strong>Tools &amp; Techniques<\/strong>,&nbsp;<strong>Outputs<\/strong>&nbsp;(ITTOs) and&nbsp;<strong>Tailoring Considerations<\/strong>.<\/p>\n\n\n\n<p><strong>Organisation of processes:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Governance domain (Initiating &amp; Planning focus areas)<\/strong>\u00a0\u2013 Processes such as\u00a0<em>Initiate Project or Phase<\/em>,\u00a0<em>Integrate and Align Project Plans<\/em>, and\u00a0<em>Define Governance Framework<\/em>\u00a0ensure the project aligns with organisational strategy, defines decision\u2011making structures and authorises work.<\/li>\n\n\n\n<li><strong>Scope domain<\/strong>\u00a0\u2013 Processes including\u00a0<em>Plan Scope Management<\/em>,\u00a0<em>Collect Requirements<\/em>,\u00a0<em>Define and Validate Scope<\/em>\u00a0and\u00a0<em>Control Scope<\/em>\u00a0provide systematic management of deliverables and boundaries.<\/li>\n\n\n\n<li><strong>Schedule domain<\/strong>\u00a0\u2013 Processes like\u00a0<em>Plan Schedule Management<\/em>,\u00a0<em>Define Activities<\/em>,\u00a0<em>Sequence Activities<\/em>,\u00a0<em>Estimate Duration<\/em>,\u00a0<em>Develop Schedule<\/em>\u00a0and\u00a0<em>Control Schedule<\/em>\u00a0maintain temporal coherence.<\/li>\n\n\n\n<li><strong>Finance domain<\/strong>\u00a0\u2013 Contains processes such as\u00a0<em>Plan Financial Resources<\/em>,\u00a0<em>Estimate Costs<\/em>,\u00a0<em>Determine Budget<\/em>,\u00a0<em>Control Costs<\/em>\u00a0and\u00a0<em>Perform Financial Closure<\/em>.<\/li>\n\n\n\n<li><strong>Stakeholders domain<\/strong>\u00a0\u2013 Processes include\u00a0<em>Plan Stakeholder Engagement<\/em>,\u00a0<em>Identify Stakeholders<\/em>,\u00a0<em>Manage Stakeholder Engagement<\/em>\u00a0and\u00a0<em>Monitor Engagement<\/em>.<\/li>\n\n\n\n<li><strong>Resources domain<\/strong>\u00a0\u2013 Processes such as\u00a0<em>Plan Resource Management<\/em>,\u00a0<em>Acquire Resources<\/em>,\u00a0<em>Develop Team<\/em>,\u00a0<em>Manage Team<\/em>,\u00a0<em>Control Resources<\/em>\u00a0ensure people, materials and equipment are managed effectively.<\/li>\n\n\n\n<li><strong>Risk domain<\/strong>\u00a0\u2013 Processes include\u00a0<em>Plan Risk Management<\/em>,\u00a0<em>Identify Risks<\/em>,\u00a0<em>Analyse Risks<\/em>,\u00a0<em>Plan Risk Responses<\/em>,\u00a0<em>Implement Risk Responses<\/em>\u00a0and\u00a0<em>Monitor Risks<\/em>.<\/li>\n<\/ul>\n\n\n\n<p>These processes reflect modern practice and support both predictive and adaptive life cycles. For example,&nbsp;<em>Plan Scope Management<\/em>&nbsp;includes iterative backlog refinement in agile projects, while&nbsp;<em>Develop Schedule<\/em>&nbsp;may use rolling\u2011wave planning in hybrid contexts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"mapping-major-areas-from-pmbok-7-to-pmbok-8\">4.4 Mapping major areas from PMBOK&nbsp;7 to PMBOK&nbsp;8<\/h3>\n\n\n\n<p>The table below summarizes how key areas from PMBOK&nbsp;7 map into the structure of PMBOK&nbsp;8. It shows where 7th\u2011edition performance domains land within the 8th\u2011edition performance domains and focus areas. Many concepts are redistributed rather than directly renamed.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Major Area<\/th><th>PMBOK&nbsp;7 (Domain\/Section)<\/th><th>PMBOK&nbsp;8 (Domain\/Section)<\/th><th>Change in emphasis<\/th><\/tr><\/thead><tbody><tr><td><strong>Stakeholder<\/strong><\/td><td>Stakeholder Performance Domain emphasised identification, analysis, engagement and outcome\u2011focused measurement.<\/td><td><strong>Stakeholders Performance Domain<\/strong>&nbsp;plus processes (<em>Identify Stakeholders<\/em>,&nbsp;<em>Plan Stakeholder Engagement<\/em>,&nbsp;<em>Manage Stakeholder Engagement<\/em>,&nbsp;<em>Monitor Engagement<\/em>).<\/td><td>Introduces detailed processes and ITTOs; engagement planning is more structured; emphasis on value realisation and alignment.<\/td><\/tr><tr><td><strong>Team \/ Resources<\/strong><\/td><td>Team Performance Domain emphasised culture, leadership styles, high\u2011performing teams and tailoring leadership. Resource management appeared within the Project Work domain.<\/td><td><strong>Resources Performance Domain<\/strong>&nbsp;consolidates people, materials, infrastructure and facilities, with processes for planning, acquiring, developing, managing and controlling resources.<\/td><td>Combines team and physical resource management; leadership and culture are addressed through the&nbsp;<em>Build an Empowered Culture<\/em>&nbsp;principle rather than a domain.<\/td><\/tr><tr><td><strong>Development Approach &amp; Life Cycle<\/strong><\/td><td>Domain covered selection of predictive, adaptive or hybrid development approaches and aligning life cycles and cadences.<\/td><td>Incorporated into the&nbsp;<strong>Schedule Performance Domain<\/strong>&nbsp;and Section&nbsp;4 (Project Life Cycles). Processes like&nbsp;<em>Define Activities<\/em>,&nbsp;<em>Sequence Activities<\/em>&nbsp;and&nbsp;<em>Develop Schedule<\/em>&nbsp;are used regardless of lifecycle.<\/td><td>Life cycle guidance is more detailed; schedule domain includes development approach considerations; focus areas reintroduce initiation and closure.<\/td><\/tr><tr><td><strong>Planning<\/strong><\/td><td>Planning Performance Domain focused on integrated planning, continuous refinement and outcome orientation.<\/td><td>Planning activities are distributed across performance domains (Scope, Schedule, Finance, Stakeholders, Resources, Risk) and processes within the&nbsp;<strong>Planning Focus Area<\/strong>.<\/td><td>Planning is no longer a single domain; instead, each domain has its own planning processes, and integrated planning is part of the Governance domain.<\/td><\/tr><tr><td><strong>Project Work &amp; Delivery<\/strong><\/td><td>Project Work domain ensured tasks were executed effectively; Delivery domain emphasised product delivery and value realisation.<\/td><td>Execution\u2011related processes reside in the&nbsp;<strong>Executing Focus Area<\/strong>&nbsp;within each performance domain; value realisation is integrated into governance and stakeholder domains.<\/td><td>Delivery and measurement are absorbed into functional domains; emphasises value and benefits rather than separate delivery domain.<\/td><\/tr><tr><td><strong>Measurement &amp; Uncertainty<\/strong><\/td><td>Measurement domain promoted outcome\u2011oriented metrics; Uncertainty domain covered risk, complexity and ambiguity.<\/td><td>Measurement activities are embedded within&nbsp;<strong>Governance<\/strong>,&nbsp;<strong>Scope<\/strong>,&nbsp;<strong>Schedule<\/strong>,&nbsp;<strong>Finance<\/strong>&nbsp;and&nbsp;<strong>Risk<\/strong>&nbsp;domains. Uncertainty is addressed primarily by the&nbsp;<strong>Risk Performance Domain<\/strong>; complexity is integrated into the holistic view principle.<\/td><td>Shifts measurement and risk considerations into functional areas; emphasises integrated metrics and risk management across domains.<\/td><\/tr><tr><td><strong>Tailoring<\/strong><\/td><td>Separate section on tailoring development approaches and performance domains.<\/td><td>Tailoring guidance embedded within each performance domain and process.<\/td><td>Encourages context\u2011specific adjustments at every level.<\/td><\/tr><tr><td><strong>Models, Methods &amp; Artefacts<\/strong><\/td><td>Comprehensive catalogue of models, methods and artefacts.<\/td><td>Not included; practitioners refer to PMIstandards+ or other PMI resources for tools and techniques.<\/td><td>Replaces lists with integrated ITTOs; emphasises adaptable process toolkit.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"inputs-tools-techniques-outputs-ittos-and-artefacts\">5. Inputs, Tools &amp; Techniques, Outputs (ITTOs) and Artefacts<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"itto-treatment-in-pmbok-7\">5.1 ITTO treatment in PMBOK&nbsp;7<\/h3>\n\n\n\n<p>Earlier editions of the PMBOK\u00ae Guide (through the Sixth Edition) provided detailed ITTO tables for each process. PMBOK&nbsp;7&nbsp;<strong>eliminated these tables<\/strong>&nbsp;and instead introduced a section on&nbsp;<strong>Models, Methods and Artefacts<\/strong>. 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"itto-integration-in-pmbok-8\">5.2 ITTO integration in PMBOK&nbsp;8<\/h3>\n\n\n\n<p>PMBOK&nbsp;8 brings back ITTOs but with a&nbsp;<strong>non\u2011prescriptive orientation<\/strong>. Each of the&nbsp;<strong>40 processes<\/strong>&nbsp;includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Inputs<\/strong>: documents, agreements or environmental factors required to perform the process.<\/li>\n\n\n\n<li><strong>Tools &amp; Techniques<\/strong>: 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\u2011enabled tools.<\/li>\n\n\n\n<li><strong>Outputs<\/strong>: deliverables, plans, baselines or updates produced by the process. Outputs may feed into other processes or provide value directly.<\/li>\n\n\n\n<li><strong>Tailoring Considerations<\/strong>: guidance on how to adjust the process based on organisational culture, lifecycle approach (predictive, adaptive, hybrid), complexity and stakeholder needs.<\/li>\n<\/ul>\n\n\n\n<p>The ITTOs are integrated within performance domains rather than isolated tables. This integration illustrates&nbsp;<strong>how processes contribute to the domain\u2019s purpose<\/strong>&nbsp;(e.g., the&nbsp;<em>Schedule<\/em>&nbsp;domain\u2019s processes produce a baseline schedule and controlling metrics), and&nbsp;<strong>how outputs feed other processes<\/strong>. Tools and techniques now include modern data analytics, AI and collaboration platforms.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"representative-process-examples\">5.3 Representative process examples<\/h3>\n\n\n\n<p>To illustrate how PMBOK&nbsp;8 processes relate to PMBOK&nbsp;7 content, the following examples compare select processes with their historical context:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Initiate Project or Phase (Governance domain, Initiating focus area)<\/strong>\u00a0\u2013 This process authorises a project or phase by creating the project charter. Inputs include business case, benefits management plan and agreements; tools &amp; techniques include expert judgment, data gathering and facilitation; outputs include a project charter and stakeholder register. In PMBOK\u00a07 the equivalent guidance existed implicitly within the Stakeholder and Planning domains and within models and artefacts (project charter). The PGPG describes\u00a0<em>Develop Project Charter<\/em>\u00a0and\u00a0<em>Identify Stakeholders<\/em>\u00a0as separate processes; PMBOK\u00a08 consolidates the authorisation and stakeholder identification into the Governance domain.<\/li>\n\n\n\n<li><strong>Integrate and Align Project Plans (Governance domain, Planning focus area)<\/strong>\u00a0\u2013 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\u00a07, 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).<\/li>\n\n\n\n<li><strong>Plan Scope Management (Scope domain, Planning focus area)<\/strong>\u00a0\u2013 Defines how scope will be defined, validated and controlled. Inputs include the project charter and organisational process assets; tools &amp; techniques may include workshops, interviews and story\u2011mapping; outputs include a scope management plan and requirements management plan. PMBOK\u00a07 treated scope planning within the Planning domain and referenced artefacts such as product backlog and requirement documents but provided no process detail.<\/li>\n<\/ol>\n\n\n\n<p>These examples illustrate that PMBOK&nbsp;8&nbsp;<strong>reintegrates processes with ITTOs<\/strong>&nbsp;while encouraging adaptation. Practitioners should tailor each process to their context rather than use them as mandatory steps.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"tailoring-governance-and-life-cycle-approaches\">6. Tailoring, Governance and Life Cycle Approaches<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"tailoring-guidance\">6.1 Tailoring guidance<\/h3>\n\n\n\n<p><strong>PMBOK&nbsp;7.<\/strong>&nbsp;A dedicated tailoring section explains why tailoring is essential and how to tailor development approaches, processes and engagement. It provides a step\u2011by\u2011step 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.<\/p>\n\n\n\n<p><strong>PMBOK&nbsp;8.<\/strong>&nbsp;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.&nbsp;adaptive context? Should backlog refinement be continuous? Each process identifies factors influencing tool selection and process adaptation. Tailoring thus becomes a&nbsp;<strong>continuous, context\u2011driven activity<\/strong>, not a separate step. The integration encourages project teams to adjust practices as conditions evolve.<\/p>\n\n\n\n<p><strong>Practical implications.<\/strong>&nbsp;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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"governance\">6.2 Governance<\/h3>\n\n\n\n<p><strong>PMBOK&nbsp;7.<\/strong>&nbsp;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.<\/p>\n\n\n\n<p><strong>PMBOK&nbsp;8.<\/strong>&nbsp;Governance becomes a&nbsp;<strong>full performance domain<\/strong>. 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&nbsp;<strong>project governance<\/strong>&nbsp;is an adaptable framework guiding project management activities to create value, providing structures, systems, roles and decision\u2011making models. The domain emphasises transparency, ethical decision\u2011making, stakeholder alignment and benefits realisation.<\/p>\n\n\n\n<p><strong>Comparison.<\/strong>&nbsp;PMBOK&nbsp;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\u2011gate reviews and benefits monitoring.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"life-cycle-approaches-predictive-adaptive-and-hybrid\">6.3 Life cycle approaches: predictive, adaptive and hybrid<\/h3>\n\n\n\n<p><strong>PMBOK&nbsp;7.<\/strong>&nbsp;The Development Approach &amp; 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.<\/p>\n\n\n\n<p><strong>PMBOK&nbsp;8.<\/strong>&nbsp;Section&nbsp;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.<\/p>\n\n\n\n<p><strong>Comparison.<\/strong>&nbsp;PMBOK&nbsp;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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"domainbydomain-detailed-comparison\">7. Domain\u2011by\u2011Domain Detailed Comparison<\/h2>\n\n\n\n<p>The following sections compare each of PMBOK&nbsp;8\u2019s seven performance domains with related content in PMBOK&nbsp;7. Each subsection summarises how coverage and emphasis have changed and provides a practical example illustrating how project manager behaviour may differ.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"governance-1\">7.1 Governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage (Stakeholder, Team, Planning, Delivery domains).<\/strong>\u00a0Governance 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.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Governance is a dedicated performance domain. It addresses project value creation, governance models (structured vs.\u00a0self\u2011governed), metrics and mechanisms for effective governance, and additional considerations for predictive environments. It prescribes processes such as\u00a0<em>Initiate Project or Phase<\/em>,\u00a0<em>Integrate and Align Project Plans<\/em>\u00a0and\u00a0<em>Define Governance Framework<\/em>, and includes tailoring advice.<\/li>\n\n\n\n<li><strong>New\/expanded\/removed.<\/strong>\u00a0Governance metrics (leading\/lagging indicators), ethical considerations and sustainability are expanded. Governance structures may vary from hierarchical committees to self\u2011organising teams; PMBOK\u00a08 emphasises choosing appropriate models.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0A PMBOK\u00a07 project manager launching an internal IT project might rely on an informal steering committee to approve major decisions. Under PMBOK\u00a08, 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\u2019s strategy and incorporate sustainability goals. Project initiation would involve developing a project charter with explicit value propositions and authorisation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"scope\">7.2 Scope<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0Scope 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.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Scope is a dedicated performance domain with processes like\u00a0<em>Plan Scope Management<\/em>,\u00a0<em>Collect Requirements<\/em>,\u00a0<em>Define Scope<\/em>,\u00a0<em>Create WBS\/Backlog<\/em>,\u00a0<em>Validate Scope<\/em>\u00a0and\u00a0<em>Control Scope<\/em>. 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.<\/li>\n\n\n\n<li><strong>New\/expanded\/removed.<\/strong>\u00a0Detailed process descriptions and ITTOs return; backlog management is incorporated; scope validation and control emphasise stakeholder acceptance and value realisation.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0In PMBOK\u00a07, an agile software project might manage scope through backlog refinement guided by the Delivery domain. In PMBOK\u00a08, the project manager formalises\u00a0<em>Plan Scope Management<\/em>\u00a0to define how backlog items will be prioritised based on value, uses\u00a0<em>Validate Scope<\/em>\u00a0to gain stakeholder acceptance at each increment and employs governance metrics to measure scope creep against value delivered.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"schedule\">7.3 Schedule<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0Schedule considerations appear within the Planning domain; the Development Approach &amp; Life Cycle domain discusses cadence and iterative planning. There are no process descriptions.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0The Schedule domain contains processes such as\u00a0<em>Plan Schedule Management<\/em>,\u00a0<em>Define Activities<\/em>,\u00a0<em>Sequence Activities<\/em>,\u00a0<em>Estimate Durations<\/em>,\u00a0<em>Develop Schedule<\/em>\u00a0and\u00a0<em>Control Schedule<\/em>. It supports both predictive scheduling (network diagrams, critical path) and adaptive approaches (timeboxed iterations, rolling\u2011wave planning). Tailoring guidance addresses schedule approaches for complex or adaptive projects.<\/li>\n\n\n\n<li><strong>Changes.<\/strong>\u00a0Scheduling becomes more granular and integrated with resource and scope management.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0A PMBOK\u00a07 project manager might maintain a high\u2011level milestone chart and adjust it iteratively. Under PMBOK\u00a08, the manager would produce a detailed schedule baseline, apply earned schedule or burndown metrics, and update the schedule via\u00a0<em>Control Schedule<\/em>\u00a0while communicating changes through the governance framework.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"finance\">7.4 Finance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0Cost 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.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Finance is a standalone domain. Processes include\u00a0<em>Plan Financial Resources<\/em>,\u00a0<em>Estimate Costs<\/em>,\u00a0<em>Determine Budget<\/em>,\u00a0<em>Control Costs<\/em>\u00a0and\u00a0<em>Perform Financial Closure<\/em>. 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.<\/li>\n\n\n\n<li><strong>Changes.<\/strong>\u00a0Cost management is elevated and integrated with value delivery; budgeting and forecasting become part of governance.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0In PMBOK\u00a07, budgeting may be handled by organisational finance outside the project manager\u2019s control. PMBOK\u00a08 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.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"stakeholders\">7.5 Stakeholders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0The Stakeholder domain emphasises identifying stakeholders, understanding interests, managing expectations and measuring engagement outcomes. It highlights co\u2011creation and influence patterns.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Stakeholders remain a performance domain but now include specific processes:\u00a0<em>Identify Stakeholders<\/em>,\u00a0<em>Plan Stakeholder Engagement<\/em>,\u00a0<em>Manage Stakeholder Engagement<\/em>\u00a0and\u00a0<em>Monitor Engagement<\/em>. Inputs include stakeholder registers and communication plans; tools include stakeholder analysis, persona development, empathy mapping and AI\u2011based sentiment analysis.<\/li>\n\n\n\n<li><strong>Changes.<\/strong>\u00a0Stakeholder engagement becomes more structured; processes emphasise continuous engagement, value alignment and integration with governance.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0A PMBOK\u00a07 practitioner might facilitate stakeholder workshops and update a stakeholder map occasionally. PMBOK\u00a08 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.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"resources\">7.6 Resources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0Team performance and resource management appear in the Team domain and Project Work domain; they stress building high\u2011performing teams, tailoring leadership styles and ensuring resources are available.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Resources are consolidated into a domain that covers\u00a0<strong>human, material, infrastructure and facilities<\/strong>. Processes include\u00a0<em>Plan Resource Management<\/em>,\u00a0<em>Estimate Resources<\/em>,\u00a0<em>Acquire Resources<\/em>,\u00a0<em>Develop Team<\/em>,\u00a0<em>Manage Team<\/em>, and\u00a0<em>Control Resources<\/em>. The domain emphasises capacity planning, competency development, motivation, diversity and wellbeing.<\/li>\n\n\n\n<li><strong>Changes.<\/strong>\u00a0Distinguishes resource types; integrates team development with resource planning; includes control processes to track resource utilisation and adjust as needed.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0In PMBOK\u00a07, a project manager might rely on HR to assign resources and focus on team cohesion. PMBOK\u00a08 requires the project manager to estimate resource needs, negotiate assignments, ensure training and equipment, manage team performance, and measure resource efficiency.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"risk\">7.7 Risk<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PMBOK\u00a07 coverage.<\/strong>\u00a0Uncertainty 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.<\/li>\n\n\n\n<li><strong>PMBOK\u00a08 coverage.<\/strong>\u00a0Risk is a dedicated domain with processes:\u00a0<em>Plan Risk Management<\/em>,\u00a0<em>Identify Risks<\/em>,\u00a0<em>Perform Risk Analysis<\/em>,\u00a0<em>Plan Risk Responses<\/em>,\u00a0<em>Implement Risk Responses<\/em>\u00a0and\u00a0<em>Monitor Risks<\/em>. 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.<\/li>\n\n\n\n<li><strong>Changes.<\/strong>\u00a0Risk management becomes more systematic; processes and ITTOs provide guidance similar to earlier editions but integrated into the new structure.<\/li>\n\n\n\n<li><strong>Practical example.<\/strong>\u00a0In PMBOK\u00a07, risk identification and response might be informal, with periodic risk reviews. Under PMBOK\u00a08, the project manager sets up a risk register, performs probability\u2011impact assessments, defines responses, implements them as part of execution, and continuously monitors risks, adjusting based on metrics and stakeholder feedback.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"impact-on-practitioners-and-organisations\">8. Impact on Practitioners and Organisations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"adjustments-for-teams-using-pmbok-7-today\">8.1 Adjustments for teams using PMBOK&nbsp;7 today<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Reorient around value.<\/strong>\u00a0Practitioners 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.<\/li>\n\n\n\n<li><strong>Adopt the project management mindset.<\/strong>\u00a0Teams should cultivate a proactive, ownership\u2011driven and value\u2011driven mindset. This involves systems thinking, continuous improvement and empowered leadership. Training should focus on soft skills, ethics and sustainability as much as technical skills.<\/li>\n\n\n\n<li><strong>Implement governance structures.<\/strong>\u00a0Create clear governance frameworks specifying decision rights, accountability and escalation paths. Ensure alignment between organisational governance and project governance and integrate benefits tracking.<\/li>\n\n\n\n<li><strong>Integrate processes and tailoring.<\/strong>\u00a0Adopt the 40 processes as a toolkit; select and adapt them based on project context. Document tailoring decisions and revisit them regularly.<\/li>\n\n\n\n<li><strong>Update templates and PMO methodologies.<\/strong>\u00a0Modify 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.<\/li>\n\n\n\n<li><strong>Engage stakeholders continuously.<\/strong>\u00a0Use structured stakeholder engagement processes; monitor sentiment; ensure stakeholders perceive value.<\/li>\n\n\n\n<li><strong>Upgrade measurement and reporting.<\/strong>\u00a0Implement metrics that link deliverables to benefits. Use dashboards that track value, governance metrics, sustainability indicators and stakeholder satisfaction.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"how-pmbok-8-supports-valuedriven-and-complex-environments\">8.2 How PMBOK&nbsp;8 supports value\u2011driven and complex environments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Holistic and sustainable focus.<\/strong>\u00a0Integrating sustainability within all project areas and building an empowered culture ensure that projects address social and environmental considerations and enable team autonomy.<\/li>\n\n\n\n<li><strong>Flexible yet actionable processes.<\/strong>\u00a0The 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.<\/li>\n\n\n\n<li><strong>Integrated governance and metrics.<\/strong>\u00a0The 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.<\/li>\n\n\n\n<li><strong>Modern tools and AI.<\/strong>\u00a0Appendices discuss artificial intelligence and emerging technologies, encouraging adoption of predictive analytics, machine learning for risk identification and digital dashboards for stakeholder engagement.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"considerations-for-training-methodologies-and-pmo-standards\">8.3 Considerations for training, methodologies and PMO standards<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Training material updates.<\/strong>\u00a0Training 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.<\/li>\n\n\n\n<li><strong>Organisational methodologies.<\/strong>\u00a0PMOs 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.<\/li>\n\n\n\n<li><strong>Templates and standards.<\/strong>\u00a0Update 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.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"summary-tables-and-glossary\">9. Summary Tables and Glossary<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"comparative-overview-table\">9.1 Comparative overview table<\/h3>\n\n\n\n<p>Below is a concise table summarising key concepts and their treatment in PMBOK&nbsp;7 vs.&nbsp;PMBOK&nbsp;8 with practical implications.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Concept<\/th><th>PMBOK&nbsp;7 Treatment<\/th><th>PMBOK&nbsp;8 Treatment<\/th><th>Practical Implication<\/th><\/tr><\/thead><tbody><tr><td><strong>Project definition<\/strong><\/td><td>Temporary endeavour to create a unique product, service or result.<\/td><td>Temporary initiative in a unique context undertaken to&nbsp;<strong>create value<\/strong>.<\/td><td>Requires explicit articulation of value proposition; success measured by benefits.<\/td><\/tr><tr><td><strong>Project management definition<\/strong><\/td><td>Application of knowledge, skills, tools and techniques to meet project requirements.<\/td><td>Application of knowledge, skills, tools and techniques to meet or&nbsp;<strong>exceed intended value<\/strong>.<\/td><td>Encourages value\u2011driven decision making and discourages scope creep or gold plating.<\/td><\/tr><tr><td><strong>Principles<\/strong><\/td><td>Twelve principles emphasising stewardship, team collaboration, stakeholder engagement, tailoring, quality, risk, adaptability, etc..<\/td><td>Six principles focusing on holistic view, value, quality, accountable leadership, sustainability and empowered culture.<\/td><td>Streamlines guidance; emphasises sustainability and culture.<\/td><\/tr><tr><td><strong>Performance domains<\/strong><\/td><td>Eight domains: Stakeholder, Team, Development Approach &amp; Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty.<\/td><td>Seven domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk.<\/td><td>Moves from behavioural\/system focus to functional focus; measurement and uncertainty integrated into other domains.<\/td><\/tr><tr><td><strong>Process groups \/ focus areas<\/strong><\/td><td>Not included in PMBOK&nbsp;7; process groups described separately in PGPG.<\/td><td>Five Focus Areas reintroducing Initiating, Planning, Executing, Monitoring &amp; Controlling, Closing.<\/td><td>Provides lifecycle structure; easier mapping for practitioners familiar with earlier editions.<\/td><\/tr><tr><td><strong>Processes &amp; ITTOs<\/strong><\/td><td>No process tables; models, methods and artefacts section.<\/td><td>40 non\u2011prescriptive processes with integrated ITTOs.<\/td><td>Offers actionable guidance; encourages adaptation to context.<\/td><\/tr><tr><td><strong>Governance<\/strong><\/td><td>Covered implicitly through stakeholder and planning domains; not a domain.<\/td><td>Dedicated Governance domain with processes, metrics and tailoring guidance.<\/td><td>Emphasises strategic alignment, transparency and accountability.<\/td><\/tr><tr><td><strong>Tailoring<\/strong><\/td><td>Separate section covering why and how to tailor.<\/td><td>Tailoring advice embedded into each performance domain and process.<\/td><td>Encourages continuous context\u2011specific adaptation.<\/td><\/tr><tr><td><strong>Life cycle guidance<\/strong><\/td><td>Development Approach &amp; Life Cycle domain discusses predictive, adaptive and hybrid approaches.<\/td><td>Life cycle guidance integrated into Schedule domain and Section&nbsp;4; focus areas emphasise iterative nature.<\/td><td>Provides more actionable selection criteria and integration with processes.<\/td><\/tr><tr><td><strong>Models, methods &amp; artefacts<\/strong><\/td><td>Extensive catalogue provided.<\/td><td>Not included; ITTOs integrated into processes.<\/td><td>Practitioners rely on PMIstandards+ or external resources for tools and techniques.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"glossary-of-selected-new-or-redefined-terms\">9.2 Glossary of selected new or redefined terms<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Term<\/th><th>Definition in PMBOK&nbsp;8<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td><strong>Project<\/strong><\/td><td>A temporary initiative in a unique context undertaken to create value.<\/td><td>Emphasises value and context.<\/td><\/tr><tr><td><strong>Project management<\/strong><\/td><td>Application of knowledge, skills, tools and techniques to meet or exceed the intended value.<\/td><td>Focuses on value rather than requirements.<\/td><\/tr><tr><td><strong>Value<\/strong><\/td><td>The excess of financial and non\u2011financial benefits over investment. Value is perceived differently by stakeholders.<\/td><td>Underpins project justification and success measurement.<\/td><\/tr><tr><td><strong>Governance<\/strong><\/td><td>Framework of structures, systems, roles and decision\u2011making models to align project with organisational strategy.<\/td><td>Includes project value creation, governance models and metrics.<\/td><\/tr><tr><td><strong>Focus Area<\/strong><\/td><td>One of five lifecycle\u2011oriented groupings\u2014Initiating, Planning, Executing, Monitoring &amp; Controlling, Closing\u2014reintroduced to organise processes.<\/td><td>Replaces the term \u201cprocess group\u201d and emphasises that actions may occur iteratively.<\/td><\/tr><tr><td><strong>Performance Domain<\/strong><\/td><td>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).<\/td><td>Replaces the 8th edition\u2019s behavioural domains; integrated with processes and ITTOs.<\/td><\/tr><tr><td><strong>Tailoring<\/strong><\/td><td>Adjusting methods, processes and artefacts to fit the project and organisational context; appears in each domain\/process description.<\/td><td>No longer a separate section; encourages continuous adaptation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"conclusion\">10. Conclusion<\/h2>\n\n\n\n<p>The evolution from&nbsp;<strong>PMBOK&nbsp;7 to PMBOK&nbsp;8<\/strong>&nbsp;reflects a maturation of the project management discipline from prescriptive process adherence to&nbsp;<strong>value\u2011oriented practice<\/strong>. PMBOK&nbsp;7 introduced a principles\u2011based, outcomes\u2011focused framework that emphasised flexibility, systems thinking and tailoring. PMBOK&nbsp;8 builds on this foundation by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reinforcing value and benefits.<\/strong>\u00a0Projects 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.<\/li>\n\n\n\n<li><strong>Simplifying principles and integrating sustainability.<\/strong>\u00a0Six principles encapsulate the project management mindset\u2014holistic view, value focus, quality, accountable leadership, sustainability and empowered culture. Sustainability and empowerment reflect broader social expectations and emphasise ethical, inclusive practices.<\/li>\n\n\n\n<li><strong>Reintroducing process structure through focus areas.<\/strong>\u00a0The five focus areas provide a familiar lifecycle structure while maintaining adaptability. Forty non\u2011prescriptive processes with integrated ITTOs offer actionable guidance tailored to varied approaches.<\/li>\n\n\n\n<li><strong>Aligning performance domains with organisational functions.<\/strong>\u00a0Seven performance domains emphasise governance, scope, schedule, finance, stakeholders, resources and risk, aligning project management with organisational departments and enabling integrated governance and value management.<\/li>\n<\/ul>\n\n\n\n<p><strong>Next steps for practitioners and PMOs:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Reevaluate project methodologies and templates<\/strong>\u00a0to align with the new definitions, principles, domains and processes. Incorporate value statements, governance frameworks and sustainability considerations into project charters and plans.<\/li>\n\n\n\n<li><strong>Train project teams and stakeholders<\/strong>\u00a0on the project management mindset, focusing on proactive behaviours, ownership and value\u2011driven decision making. Encourage continuous learning and adaptation.<\/li>\n\n\n\n<li><strong>Implement integrated governance structures<\/strong>\u00a0that support transparent decision making, benefits tracking and ethical practices. Use metrics and dashboards to monitor value, sustainability and stakeholder satisfaction.<\/li>\n\n\n\n<li><strong>Adopt flexible processes and tailoring<\/strong>, leveraging the 40 processes as a toolkit rather than a checklist. Document tailoring decisions and share lessons learned across the organisation.<\/li>\n\n\n\n<li><strong>Engage with PMIstandards+ and emerging technologies<\/strong>\u00a0to access updated models, methods, artefacts and AI\u2011enabled tools that complement the guide.<\/li>\n<\/ol>\n\n\n\n<p>By embracing these changes, project professionals can deliver projects that not only meet traditional performance constraints but also&nbsp;<strong>maximise value and sustainability<\/strong>&nbsp;for stakeholders and organisations.<\/p>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-28f84493 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe title=\"Mastering Your Career - For Project Managers\" width=\"1170\" height=\"658\" src=\"https:\/\/www.youtube.com\/embed\/VAou_J74dUE?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<p><strong>How To Land the Job and Interview for Project Managers Course:<\/strong><\/p>\n\n\n\n<p>Advance your project management career with HK School of Management\u2019s expert-led course. Gain standout resume strategies, master interviews, and confidently launch your first 90 days. With real-world insights, AI-powered tools, and interactive exercises, you&#8217;ll navigate hiring, salary negotiation, and career growth like a pro. Enroll now and take control of your future!<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.udemy.com\/course\/how-to-land-the-job-and-interview-for-project-managers\/?referralCode=8532FA1ED2CB384A8AE6\" target=\"_blank\" rel=\"noreferrer noopener\">Learn more<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>1. Executive Summary Projects underpin modern value creation. The&nbsp;Project Management Body of Knowledge (PMBOK\u00ae)&nbsp;has long served as the reference for how projects should be managed. The&nbsp;Seventh Edition&nbsp;(2021) represented a radical shift away from prescriptive processes to a principles\u2011 and outcomes\u2011focused model with eight performance domains. The&nbsp;Eighth Edition&nbsp;(2025) continues the evolution [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1895,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[179],"tags":[203,48,33,182],"class_list":["post-1894","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pmbok-and-standards","tag-deep-dive","tag-pmbok","tag-pmi","tag-pmp-candidate"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp\" \/>\n<meta property=\"og:description\" content=\"1. Executive Summary Projects underpin modern value creation. The&nbsp;Project Management Body of Knowledge (PMBOK\u00ae)&nbsp;has long served as the reference for how projects should be managed. The&nbsp;Seventh Edition&nbsp;(2021) represented a radical shift away from prescriptive processes to a principles\u2011 and outcomes\u2011focused model with eight performance domains. The&nbsp;Eighth Edition&nbsp;(2025) continues the evolution [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/\" \/>\n<meta property=\"og:site_name\" content=\"Project Management Bootcamp\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-06T03:15:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-19T20:16:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"1792\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"32 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#\\\/schema\\\/person\\\/57058f1ac2e1f128cf76df71c8c5f8d3\"},\"headline\":\"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report\",\"datePublished\":\"2025-12-06T03:15:03+00:00\",\"dateModified\":\"2026-04-19T20:16:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/\"},\"wordCount\":7285,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1\",\"keywords\":[\"Deep Dive\",\"PMBOK\",\"PMI\",\"PMP Candidate\"],\"articleSection\":[\"PMBOK &amp; Standards\"],\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/\",\"url\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/\",\"name\":\"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1\",\"datePublished\":\"2025-12-06T03:15:03+00:00\",\"dateModified\":\"2026-04-19T20:16:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#primaryimage\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2025\\\/12\\\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1\",\"width\":1792,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/project-management\\\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#website\",\"url\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/\",\"name\":\"Project Management Bootcamp\",\"description\":\"Empowering Professionals\",\"publisher\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#organization\",\"name\":\"Project Management Bootcamp\",\"url\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2023\\\/10\\\/logo-no-text.png\",\"contentUrl\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/wp-content\\\/uploads\\\/2023\\\/10\\\/logo-no-text.png\",\"width\":258,\"height\":262,\"caption\":\"Project Management Bootcamp\"},\"image\":{\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/yury-kozlov\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/#\\\/schema\\\/person\\\/57058f1ac2e1f128cf76df71c8c5f8d3\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"sameAs\":[\"https:\\\/\\\/hksmnow.com\\\/project-management\"],\"url\":\"https:\\\/\\\/hksmnow.com\\\/project-management\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/","og_locale":"en_US","og_type":"article","og_title":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp","og_description":"1. Executive Summary Projects underpin modern value creation. The&nbsp;Project Management Body of Knowledge (PMBOK\u00ae)&nbsp;has long served as the reference for how projects should be managed. The&nbsp;Seventh Edition&nbsp;(2021) represented a radical shift away from prescriptive processes to a principles\u2011 and outcomes\u2011focused model with eight performance domains. The&nbsp;Eighth Edition&nbsp;(2025) continues the evolution [&hellip;]","og_url":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/","og_site_name":"Project Management Bootcamp","article_published_time":"2025-12-06T03:15:03+00:00","article_modified_time":"2026-04-19T20:16:13+00:00","og_image":[{"width":1792,"height":1024,"url":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","type":"image\/webp"}],"author":"admin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"admin","Est. reading time":"32 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#article","isPartOf":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/"},"author":{"name":"admin","@id":"https:\/\/hksmnow.com\/project-management\/#\/schema\/person\/57058f1ac2e1f128cf76df71c8c5f8d3"},"headline":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report","datePublished":"2025-12-06T03:15:03+00:00","dateModified":"2026-04-19T20:16:13+00:00","mainEntityOfPage":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/"},"wordCount":7285,"commentCount":0,"publisher":{"@id":"https:\/\/hksmnow.com\/project-management\/#organization"},"image":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","keywords":["Deep Dive","PMBOK","PMI","PMP Candidate"],"articleSection":["PMBOK &amp; Standards"],"inLanguage":"en","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/","url":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/","name":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report - Project Management Bootcamp","isPartOf":{"@id":"https:\/\/hksmnow.com\/project-management\/#website"},"primaryImageOfPage":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#primaryimage"},"image":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","datePublished":"2025-12-06T03:15:03+00:00","dateModified":"2026-04-19T20:16:13+00:00","breadcrumb":{"@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/"]}]},{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#primaryimage","url":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","contentUrl":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","width":1792,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/hksmnow.com\/project-management\/project-management\/pmbok-7-vs-pmbok-8-comprehensive-comparison-report\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hksmnow.com\/project-management\/"},{"@type":"ListItem","position":2,"name":"PMBOK 7 vs PMBOK 8 Comprehensive Comparison Report"}]},{"@type":"WebSite","@id":"https:\/\/hksmnow.com\/project-management\/#website","url":"https:\/\/hksmnow.com\/project-management\/","name":"Project Management Bootcamp","description":"Empowering Professionals","publisher":{"@id":"https:\/\/hksmnow.com\/project-management\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hksmnow.com\/project-management\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Organization","@id":"https:\/\/hksmnow.com\/project-management\/#organization","name":"Project Management Bootcamp","url":"https:\/\/hksmnow.com\/project-management\/","logo":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/hksmnow.com\/project-management\/#\/schema\/logo\/image\/","url":"https:\/\/hksmnow.com\/project-management\/wp-content\/uploads\/2023\/10\/logo-no-text.png","contentUrl":"https:\/\/hksmnow.com\/project-management\/wp-content\/uploads\/2023\/10\/logo-no-text.png","width":258,"height":262,"caption":"Project Management Bootcamp"},"image":{"@id":"https:\/\/hksmnow.com\/project-management\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/in\/yury-kozlov\/"]},{"@type":"Person","@id":"https:\/\/hksmnow.com\/project-management\/#\/schema\/person\/57058f1ac2e1f128cf76df71c8c5f8d3","name":"admin","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/secure.gravatar.com\/avatar\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/b8f79fd7ffa17d42a2a6ec3bd77b731eaf7e922301bd55472a360b1bd905f928?s=96&d=mm&r=g","caption":"admin"},"sameAs":["https:\/\/hksmnow.com\/project-management"],"url":"https:\/\/hksmnow.com\/project-management\/author\/admin\/"}]}},"jetpack_featured_media_url":"https:\/\/i0.wp.com\/hksmnow.com\/project-management\/wp-content\/uploads\/2025\/12\/PMBOK7-vs-Blog-Cover.webp?fit=1792%2C1024&ssl=1","_links":{"self":[{"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/posts\/1894","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/comments?post=1894"}],"version-history":[{"count":1,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/posts\/1894\/revisions"}],"predecessor-version":[{"id":1896,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/posts\/1894\/revisions\/1896"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/media\/1895"}],"wp:attachment":[{"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/media?parent=1894"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/categories?post=1894"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hksmnow.com\/project-management\/wp-json\/wp\/v2\/tags?post=1894"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}