Latest Post
Ask ten project managers what they thought of the PMBOK Guide's seventh edition and you will hear a familiar complaint: the ideas were good, but it was hard to know what to actually do on Monday morning. The eighth edition is PMI's answer. It keeps the principle-based thinking of the seventh edition, simplifies it, and brings back a practical, process-based layer that many practitioners missed.
This guide breaks down the new structure in plain language, shows how the pieces fit together, and explains what it means for your work and for the PMP exam.
Quick answer:
The PMBOK Guide – Eighth Edition, published by PMI in November 2025, is built on three layers. Six principles shape how project managers think: adopt a holistic view, focus on value, embed quality, lead accountably, integrate sustainability, and build empowered teams. Seven performance domains define what must be managed: governance, scope, schedule, finance, stakeholders, resources and risk. Five focus areas (initiating, planning, executing, monitoring and controlling, and closing) organise around 40 non-prescriptive processes that describe how the work gets done.
What Is the PMBOK Guide 8th Edition?
The PMBOK Guide (A Guide to the Project Management Body of Knowledge) is the Project Management Institute's foundational reference for the profession. The eighth edition was released to PMI members in digital form in November 2025, with the print edition following in early 2026. It is published together with The Standard for Project Management in a single volume.
According to PMI, the edition draws on input from thousands of practitioners and more than 48,000 data points. Its stated aim is to connect the why, what and how of project management in one coherent structure.
Why PMI Needed a New Edition
The sixth edition (2017) was detailed and process-heavy, with 49 processes arranged across 10 knowledge areas. It suited predictive projects but felt rigid for agile teams. The seventh edition (2021) swung the other way, replacing processes with 12 principles and 8 performance domains. It was flexible but abstract, and many readers struggled to translate it into daily practice.
The eighth edition aims for the middle ground: principles for judgement, domains for focus, and processes for practical guidance, applied in whatever way suits the project.
How the Three Layers Fit Together
A helpful way to picture the new structure is as three questions every project manager asks:
LayerQuestion it answersWhat it containsPrinciplesHow should I think and behave?6 guiding principlesPerformance domainsWhat must I pay attention to?7 areas of project performanceFocus areasWhat work happens, and when?5 focus areas with about 40 processes
Tailoring runs through all three. The guide repeatedly reminds readers to adapt the practices to the project's size, risk, industry and delivery approach, whether predictive, agile or hybrid.
The 6 Principles of PMBOK 8
The seventh edition's 12 principles overlapped in places and were hard to remember. The eighth edition consolidates them into six that are easier to apply.
1. Adopt a Holistic View
A project is part of a larger system that includes the organisation, its strategy, other projects, customers and society. Decisions in one area ripple into others. A project manager who cuts testing time to meet a deadline, for example, may create support costs that land on another team months later.
2. Focus on Value
Success is measured by the value a project creates, not just by whether it delivered its outputs on time and within budget. A new HR system that is delivered on schedule but that employees refuse to use has not delivered value.
3. Embed Quality
Quality is built into processes and deliverables from the start, rather than inspected at the end. This principle absorbs much of what used to sit in the separate Quality Management knowledge area.
4. Lead Accountably
Project leaders take ownership of decisions and outcomes, act ethically, and make their reasoning transparent to stakeholders. Accountability applies to the whole team, not only to the person with the project manager title.
5. Integrate Sustainability
Projects should consider their environmental, social and economic impact over the full life of what they deliver. This is one of the most visible additions, reflecting growing pressure on organisations to report and manage sustainability.
6. Build Empowered Teams
High-performing teams have clarity, trust and the authority to make decisions within agreed limits. The project manager's role shifts from directing tasks to creating the conditions for the team to succeed.
The 7 Performance Domains
Performance domains are groups of related activities that are critical to delivering project outcomes. They interact constantly, so treat them as lenses on the same project rather than separate departments.
1. Governance
Governance covers how decisions are made, who approves what, how issues are escalated, and how the project aligns with organisational policies and strategy. It also includes integrating the various project plans into a coherent whole. In the new structure, governance plays much of the role that integration management played in earlier editions.
2. Scope
Scope defines what the project will and will not deliver, and how requirements are gathered, prioritised and controlled. In agile settings, this means managing a product backlog. In predictive settings, it means a work breakdown structure and formal change control.
3. Schedule
Schedule covers planning the sequence and timing of work, managing dependencies, and responding when progress shifts. The approach should match the life cycle: a construction project's critical path schedule looks very different from a software team's sprint plan.
4. Finance
Finance covers budgeting, cost tracking, funding and financial decisions, with an eye on the project's expected value. Procurement, which receives expanded coverage in this edition, is closely tied to this domain.
5. Stakeholders
This domain covers identifying the people and groups affected by the project, understanding their interests and influence, and engaging them throughout. Communication planning sits naturally here.
6. Resources
Resources include people, equipment, materials, facilities and technology. The domain covers acquiring, developing and managing them, including building the team and resolving conflicts.
7. Risk
Risk covers identifying threats and opportunities, analysing them, and planning responses. The emphasis is on navigating uncertainty rather than simply listing risks in a register that nobody reads.
What Happened to Quality and Communications?
Readers familiar with the sixth edition often notice that quality and communications are no longer standalone areas. They have not disappeared. Quality is now a principle (embed quality) that applies across every domain, and communication is woven into stakeholder engagement and governance.
The 5 Focus Areas and 40 Processes
The focus areas will look familiar to anyone who studied the sixth edition. They mirror the classic process groups, now presented as focus areas that apply to any approach.
1. Initiating
Starting a project or phase: confirming the business need, defining high-level objectives, identifying key stakeholders and securing authorisation.
2. Planning
Developing the approach to scope, schedule, finance, resources, risk and stakeholder engagement, at the level of detail the project needs. On an agile project, much of this happens progressively, sprint by sprint.
3. Executing
Doing the work: building deliverables, leading the team, engaging stakeholders and managing procurement.
4. Monitoring and Controlling
Tracking performance against plans, managing changes and taking corrective action. In adaptive projects, this includes reviews, retrospectives and backlog reprioritisation.
5. Closing
Formally completing the project or phase, handing over deliverables, releasing resources and capturing lessons learned. The guide also recognises early closure when a project no longer makes sense.
Why the Processes Are "Non-Prescriptive"
The roughly 40 processes are fewer than the sixth edition's 49 and are deliberately flexible. They describe what typically needs to happen, not a fixed sequence of inputs, tools and outputs. A five-person internal project and a multi-year infrastructure programme can both use them, at very different levels of formality.
New and Expanded Topics
Artificial Intelligence
The guide addresses how AI can support project work, such as forecasting, risk analysis, reporting and drafting documents, and the governance needed to use it responsibly, including data privacy, bias and human oversight.
Project Management Offices (PMOs)
Expanded guidance covers how PMOs can add value through governance, standards, capability building and portfolio support, rather than acting only as reporting centres.
Procurement
With more projects relying on vendors, contractors and partners, procurement receives fuller treatment, from choosing contract types to managing supplier relationships.
PMBOK 6 vs 7 vs 8: Side-by-Side Comparison
Feature6th Edition (2017)7th Edition (2021)8th Edition (2025)Core structureProcess-basedPrinciple-basedPrinciples + domains + processesPrinciplesNone126Areas of practice10 knowledge areas8 performance domains7 performance domainsProcesses49 in 5 process groupsNoneAbout 40 in 5 focus areasDelivery approachesMainly predictivePredictive, agile, hybridPredictive, agile, hybridEmerging topicsLimitedModels and methodsAI, PMOs, procurement, sustainability
Putting It Together: A Practical Example
An illustrative example to show how the layers work together.
Imagine a mid-sized logistics company in Gurugram rolling out a warehouse management system across six sites.
- Principles in action: The project manager focuses on value by defining success as faster order dispatch, not just "system live." Integrating sustainability leads the team to plan reuse of existing scanners instead of buying all-new hardware.
- Domains in action: Governance sets a steering committee and clear approval limits. Scope is split into a fixed core (inventory and dispatch) and an evolving backlog (reports and dashboards). Finance tracks vendor milestone payments. Stakeholders include warehouse supervisors, whose buy-in decides adoption. Risk planning flags the festive-season peak as a no-go period for go-live.
- Focus areas in action: Initiating confirms the business case. Planning uses a hybrid approach, with a predictive rollout schedule and agile sprints for configuration. Executing and monitoring run site by site, and closing captures lessons before each new site goes live.
No single layer would be enough on its own. Together, they give the project manager both direction and a practical checklist.
What PMBOK 8 Means for the PMP and CAPM Exams
The PMP exam is built on PMI's Examination Content Outline (ECO), not directly on any single edition of the PMBOK Guide. However, the new PMP exam launched on 9 July 2026 closely reflects the eighth edition's themes: business value, hybrid delivery, AI and sustainability. Business Environment now carries 26% of the exam, up from 8%.
For candidates, the eighth edition is a useful reference for understanding the thinking behind the exam, but it should be paired with the ECO and practice questions. Read our full guide to the new PMP exam in 2026 for domain weights and a study plan.
How to Start Using PMBOK 8 at Work
- Start with the principles. Use them as a checklist in project reviews: are we focused on value, and is quality built in?
- Map your current templates to the seven domains. Most organisations find gaps in finance tracking or stakeholder engagement.
- Tailor the processes. Keep only what adds value for your project size and risk level.
- Set rules for AI use. Decide which tools are approved and what data can be shared.
- Add a sustainability question to your business case template. It is a small change that signals the new mindset.
Frequently Asked Questions
When was the PMBOK Guide 8th Edition released?
PMI released the eighth edition to members in digital form in November 2025. The print edition followed in early 2026.
What are the 6 principles of PMBOK 8?
Adopt a holistic view, focus on value, embed quality, lead accountably, integrate sustainability, and build empowered teams.
What are the 7 performance domains in PMBOK 8?
Governance, scope, schedule, cost, stakeholders, resources, and risk.
What are the 5 focus areas in PMBOK 8?
Initiating, planning, executing, monitoring and controlling, and closing. Together, they organise about 40 non-prescriptive processes.
Is PMBOK 8 required for the PMP exam?
The PMP exam is based on PMI's Examination Content Outline, not on one book. PMBOK 8 is closely aligned with the 2026 exam and is a valuable reference, but it should be studied alongside the ECO and practice questions.
Should I still read PMBOK 7?
The eighth edition carries forward and simplifies the seventh edition's core ideas, so most readers can go straight to PMBOK 8. The sixth edition remains useful for detailed predictive techniques.
Final Thoughts
The PMBOK Guide 8th Edition is the most practical in years. It respects the flexibility that agile and hybrid teams need, while giving project managers a clear structure to fall back on. Learn the six principles well, use the seven domains to check that nothing important is being missed, and tailor the processes to your context. That combination is what the profession, and the new PMP exam, now expects.
If you want structured guidance on applying these ideas, explore our PMP certification training or the entry-level CAPM course. You can learn more about the guide on PMI's official PMBOK Guide page.