PMBOK 8th Edition: Key Principles, Domains, and Formulas

Table of Contents

• What the PMBOK is (and what it is not)
• Evolution: from 49 processes to principles and back to processes
• The structure of the 8th edition

  • The 6 principles
  • The 7 performance domains and their 40 processes
  • The 5 focus areas
  • Tailoring: adapt, don't copy
• Technical tools you have to master

  • 1. Critical path method (CPM)
  • 2. Earned value management (EVM)
  • 3. Quantitative risk analysis: expected monetary value (EMV)
• PMBOK vs. other frameworks
• How to apply the PMBOK without bureaucratizing your project
• What if you are starting a business?
• Frequently Asked Questions

What the PMBOK is (and what it is not)

The PMBOK® Guide (A Guide to the Project Management Body of Knowledge) is published by the Project Management Institute (PMI). Alongside it, The Standard for Project Management is published, recognized as a national standard in the United States by ANSI.

Three clarifications that avoid half the arguments:

1. It is not a methodology. It is a body of knowledge: it describes what is usually done in project management; it does not impose how to do it in your organization. A methodology (PRINCE2, Scrum, your company's internal methodology) does define roles, sequences, and mandatory templates.
2. It is not only for predictive (waterfall) projects. Since the 7th edition, it explicitly covers predictive, adaptive (agile), and hybrid approaches.
3. It is not the complete PMP syllabus. The PMP exam is based on the PMI's Examination Content Outline (ECO). The PMBOK is a central reference, but not the only one.

Evolution: from 49 processes to principles and back to processes

	6th edition (2017)	7th edition (2021)	8th edition (Nov. 2025)
Approach	Process-based	Principle-based	Principles + processes
Core	5 process groups, 10 knowledge areas	12 principles, 8 performance domains	6 principles, 7 performance domains
Processes	49, with inputs, tools, and outputs (ITTO)	Removed from the main body (published separately in the Process Groups: A Practice Guide)	40 processes, integrated into the domains
Agile / hybrid	Agile practice annex	Integrated throughout the text	Integrated, with an emphasis on tailoring

The 7th edition was a radical change: it set processes aside and talked about principles and outcomes instead. It was more flexible, but many teams struggled to put it into practice. The 8th edition seeks a middle ground: it keeps the principles-based perspective and brings back concrete processes as a bridge to execution, in a single publication.

The structure of the 8th edition

The 6 principles

The 12 principles of the 7th edition were consolidated into six:

1. Adopt a holistic view. The project is a system: changing one part affects the others.
2. Focus on value. Success is measured by the outcomes and benefits it delivers, not only by meeting scope, schedule, and cost.
3. Build quality into processes and deliverables. Quality is designed from the start, not inspected at the end.
4. Be a responsible leader. Accountability, ethics, and leadership exercised by the whole team, not only by the manager.
5. Embed sustainability in every area of the project. This is the most visible novelty: environmental, social, and economic impact as a decision criterion.
6. Build an empowered culture. Teams with autonomy, psychological safety, and the capacity to decide.

The 7 performance domains and their 40 processes

Domain	What it covers	Processes
Governance	Decision structure, integration, change control, closure	9
Scope	Requirements, WBS, scope validation and control	6
Schedule	Planning, sequencing, and time control	3
Finance	Cost estimation, budgeting, financial control	4
Stakeholders	Identification, engagement, and communication with stakeholders	7
Resources	Team, physical resources, acquisition, and development	5
Risk	Identification, analysis, response, and monitoring	6
Total		40

If you come from the 6th edition, the approximate mapping is: integration → governance; cost → finance; resources, communications, and stakeholders are reorganized between Resources and Stakeholders. Procurement is no longer a central area and moved to an appendix, and quality was elevated to a principle.

The 5 focus areas

The old process groups are now called focus areas (focus areas): Initiating, Planning, Executing, Monitoring and Control, and Closing. Each process within a domain sits in one of them. In practice, this gives you a domain × focus area matrix that works as a map of the project: for example, "Risk × Planning" groups what you do to identify and analyze risks before executing.

Tailoring: adapt, don't copy

In the 7th edition, tailoring was a principle; in the 8th, it has its own section. The technical idea is simple: you select which processes, artifacts, and levels of formality to apply depending on context: size, criticality, regulation, requirements uncertainty, and team maturity. A chatbot implementation project for an SME does not need the same risk management plan as building a hospital.

Technical tools you have to master

Principles guide; calculations decide. These are the three quantitative techniques that appear in practically any serious project.

1. Critical path method (CPM)

The critical path is the longest sequence of dependent activities: it determines the minimum duration of the project. Any delay in it delays the whole project.

Example:

Activity	Duration (days)	Predecessor
A. Requirements gathering	3	—
B. Development	4	A
C. Infrastructure setup	2	A
D. Testing and integration	5	B, C

Possible paths:

• A → B → D = 3 + 4 + 5 = 12 days ← critical path
• A → C → D = 3 + 2 + 5 = 10 days

Activity C has 2 days of float: it can be delayed by up to two days without affecting the final date. B has no float. If you want to shorten the project, you have to act on A, B, or D, either with crashing (adding resources) or fast tracking (overlapping activities, which increases risk).

2. Earned value management (EVM)

Earned value management integrates scope, schedule, and cost into a single system of indicators. These are the base variables:

• BAC (Budget at Completion): total budget.
• PV (Planned Value): value of the work that should be done by the date.
• EV (Earned Value): value of the work that is actually done.
• AC (Actual Cost): what has actually been spent.

And these are the key formulas:

Indicator	Formula	Interpretation
Cost variance	CV = EV − AC	Negative = cost overrun
Schedule variance	SV = EV − PV	Negative = delay
Cost performance index	CPI = EV / AC	< 1 = you spend more than you produce
Schedule performance index	SPI = EV / PV	< 1 = you move slower than planned
Estimate at completion	EAC = BAC / CPI	Projected final cost if the trend continues
Estimate to complete	ETC = EAC − AC	What remains to be spent
Variance at completion	VAC = BAC − EAC	Negative = you will finish over budget
To-complete performance index	TCPI = (BAC − EV) / (BAC − AC)	The efficiency you need from now on to meet the BAC

Example: a 6-month project with a budget of COP 100 million. At the end of month 3, the plan said you should be at 50% (PV = 50 M), you are at 40% of the work (EV = 40 M), and you have spent 48 M (AC = 48 M).

• CV = 40 − 48 = −8 M → cost overrun
• SV = 40 − 50 = −10 M → delay
• CPI = 40 / 48 = 0.83 → for every peso spent, you produce 83 cents of value
• SPI = 40 / 50 = 0.80 → you are moving at 80% of planned speed
• EAC = 100 / 0.83 ≈ 120 M → if nothing changes, the project will cost 20 M more
• ETC = 120 − 48 = 72 M
• VAC = 100 − 120 = −20 M
• TCPI = (100 − 40) / (100 − 48) = 60 / 52 ≈ 1.15 → to meet the original budget, you would have to be 15% more efficient than planned for the rest of the project. With a current CPI of 0.83, that is unrealistic: you need to re-baseline or negotiate scope.

That is the value of EVM: detecting in month 3 a problem that, without indicators, would only appear in month 6.

3. Quantitative risk analysis: expected monetary value (EMV)

EMV = Probability × Impact. Threats have a negative impact; opportunities, a positive one.

Risk	Probability	Impact	EMV
The API provider changes its pricing policy	30%	−20 M	−6 M
Delays in client approvals	50%	−4 M	−2 M
Reusing components from a previous project	20%	+10 M	+2 M
Total EMV			−6 M

That −6 M is a technical basis for sizing the contingency reserve, instead of adding a "10% just in case" with no backing. In addition, the probability and impact matrix helps you prioritize which risks deserve an active response (avoid, transfer, mitigate, or accept; for opportunities: exploit, share, enhance, or accept).

PMBOK vs. other frameworks

	PMBOK	PRINCE2	Scrum
Type	Body of knowledge / standard	Process-based methodology	Agile framework
Prescriptiveness	Low: you adapt it	High: defined roles, stages, and products	Medium: fixed events, roles, and artifacts, free practices
Best for	Conceptual foundation in any industry	Organizations seeking formal governance	Products with changing requirements
Associated certification	PMP, CAPM (PMI)	PRINCE2 Foundation / Practitioner	PSM, CSM, among others

They don't compete. In practice, many organizations use the PMBOK as a common vocabulary, Scrum for development, and a predictive-style governance layer for budgeting and executive reporting. That is a hybrid approach, and the 8th edition treats it as normal, not as an exception.

How to apply the PMBOK without bureaucratizing your project

1. Start with the domains, not with the 40 processes. Ask yourself: is it clear how decisions are made (governance), what is delivered (scope), when (schedule), with what money (finance), with whom (stakeholders and resources), and what can go wrong (risk)?
2. Define the development approach: predictive if requirements are stable, adaptive if they are uncertain, hybrid if you have both.
3. Choose the minimum artifacts: project charter, WBS or backlog, schedule or roadmap, risk register, stakeholder register.
4. Measure from day one. Even if it's a simplified EVM in a spreadsheet.
5. Review and adapt at every milestone. The plan is a hypothesis; tailoring is continuous.

What if you are starting a business?

Project management is one of the least valued skills among entrepreneurs and one of the ones that saves the most money. Launching a product, opening a store, or implementing software are all projects. If you are on that path, check out our roadmap for learning entrepreneurship: project management appears in the operations and growth stage, and it is worth arriving there with these foundations.

And if you want to train in project management, marketing, and strategy with a practical approach for Latin America, check out the training offer at Leo Transforma.

---

Frequently Asked Questions

What is the PMBOK? It is the guide from the Project Management Institute (PMI) that gathers the body of knowledge of project management. It is not a methodology, but a reference that each organization adapts.

Which is the current edition of the PMBOK? The 8th edition, published by the PMI in November 2025. It has 6 principles, 7 performance domains, and 40 processes organized into 5 focus areas.

What are the performance domains of PMBOK 8? Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk.

What is the difference between PMBOK 7 and PMBOK 8? The 7th had 12 principles and 8 domains and removed processes from the main body. The 8th consolidates into 6 principles and 7 domains, brings back 40 processes, elevates sustainability to a principle, and moves procurement to an appendix.

Is the PMP exam based only on the PMBOK? No. The PMP is based on the PMI's Examination Content Outline and includes agile and hybrid approaches. The PMBOK is a central reference, but not the only one.

Which PMBOK formulas are the most important? The earned value ones: CV = EV − AC, SV = EV − PV, CPI = EV / AC, SPI = EV / PV, EAC = BAC / CPI and TCPI = (BAC − EV) / (BAC − AC).