PMBOK Guide Essentials

The PMBOK Guide (Project Management Body of Knowledge) is published by the Project Management Institute (PMI) and is the global standard for project management. Now in its 7th edition (2021), it serves as a comprehensive reference of principles, practices, and terminology that project managers worldwide rely on.

Important distinction: PMBOK is not a methodology — it's a body of knowledge. It doesn't prescribe a step-by-step process like PRINCE2 does. Instead, it provides a toolkit of best practices that you adapt to your specific project context.

PMBOK 6th Edition: Process Groups & Knowledge Areas

The 6th edition (2017) organized project management into 5 Process Groups and 10 Knowledge Areas, forming a matrix of 49 processes. This structure remains widely used and is the basis for the PMP exam.

The 5 Process Groups

Initiating

2 processes

Planning

24 processes

Executing

10 processes

Monitoring & Controlling

12 processes

Closing

1 process

The 10 Knowledge Areas

Each knowledge area represents a complete area of specialization within project management:

1. Integration The "glue" that ties everything together. Includes project charter, project plan, change control, and closure.

2. Scope Defining and controlling what is and isn't included. WBS, scope validation, and scope control.

3. Schedule Time management — defining activities, sequencing, estimating durations, and building the schedule (CPM, Gantt).

4. Cost Estimating costs, determining budget, and controlling costs. Earned Value Management lives here.

5. Quality Planning quality standards, managing quality assurance, and controlling quality through inspections and audits.

6. Resource Planning, acquiring, developing, and managing the project team and physical resources.

7. Communications Planning what information to share, with whom, how often, and through what channels.

8. Risk Identifying, analyzing, planning responses, implementing responses, and monitoring risks throughout.

9. Procurement Planning purchases, conducting procurements, and managing vendor/supplier relationships and contracts.

10. Stakeholder Identifying stakeholders, planning engagement, managing expectations, and monitoring stakeholder relationships.

PMBOK 7th Edition: The Shift to Principles

The 7th edition (2021) made a major shift from being process-based to being principle-based. Instead of 49 processes, it defines 12 principles and 8 performance domains. This makes it more adaptable across predictive, agile, and hybrid approaches.

The 12 Project Management Principles

Be a diligent, respectful, and caring steward
Create a collaborative project team environment
Effectively engage with stakeholders
Focus on value
Recognize, evaluate, and respond to system interactions
Demonstrate leadership behaviors
Tailor based on context
Build quality into processes and deliverables
Navigate complexity
Optimize risk responses
Embrace adaptability and resiliency
Enable change to achieve the envisioned future state

The 8 Performance Domains

Performance domains replaced knowledge areas as the primary organizing structure:

Stakeholders — Activities related to stakeholder engagement
Team — Activities related to the project team
Development Approach & Life Cycle — Choosing predictive, adaptive, or hybrid
Planning — Organizing and elaborating the work
Project Work — Establishing processes and performing work
Delivery — Delivering scope, quality, and value
Measurement — Assessing project performance and taking action
Uncertainty — Addressing risks, ambiguity, and complexity

6th vs. 7th Edition

Aspect	6th Edition (2017)	7th Edition (2021)
Approach	Process-based (49 processes)	Principle-based (12 principles)
Structure	10 Knowledge Areas	8 Performance Domains
Methodology	Primarily predictive (Waterfall)	Covers predictive, adaptive, and hybrid
Focus	Deliverables and outputs	Value delivery and outcomes
Companion	Agile Practice Guide	PMIstandards+ (online, evolving content)

For the PMP certification exam, PMI now tests on both editions plus the Agile Practice Guide. In practice, many organizations still use the 6th edition's process structure for day-to-day work while applying the 7th edition's principles as a guiding philosophy. You don't need to choose one over the other — think of the 6th as "how" and the 7th as "why."