---
name: project-management-body-of-knowledge
description: Use when asked about PMBOK (the Project Management Body of Knowledge, published by PMI) specifically — its knowledge areas and process groups — as distinct from the general project-management discipline and from a specific methodology like prince2.
---

# Project Management Body of Knowledge (PMBOK)

The Project Management Body of Knowledge (PMBOK) is a set of standard
terminology and guidelines for project management, published by the
Project Management Institute (PMI) and best known through its flagship
publication, *A Guide to the Project Management Body of Knowledge* (the
PMBOK Guide). It underlies PMI's PMP (Project Management Professional)
certification.

## Structure

Historically organized around **process groups** (Initiating, Planning,
Executing, Monitoring & Controlling, Closing) crossed with **knowledge
areas** (integration, scope, schedule, cost, quality, resource,
communications, risk, procurement, and stakeholder management). More
recent editions of the PMBOK Guide have shifted toward a
principles-and-performance-domain structure, reflecting a broader
industry move away from strictly linear, plan-driven process framing —
worth checking which edition a specific team or certification
references, since the two framings organize the same underlying
knowledge differently.

## How it relates to this collection's other project-management skills

- **[[project-management]]** — the general, methodology-independent
  discipline; PMBOK is one specific, formally published codification of
  much of that same underlying knowledge.
- **[[prince2]]** — a distinct, specific *methodology*
  (Projects IN Controlled Environments), with its own defined processes
  and roles, rather than PMBOK's broader knowledge-area/process-group
  framing; a team might follow PRINCE2 as its methodology while still
  drawing vocabulary from PMBOK, or vice versa.
- **[[risks-actions-issues-decisions]]**, **RAID** in
  [[project-management]] — PMBOK's risk-management knowledge area
  is the broader home these more specific tracking tools sit under.

## Common pitfalls

- **Treating PMBOK as a single fixed methodology** — it's a body of
  knowledge and terminology, not a prescriptive step-by-step method the
  way PRINCE2 is; teams draw on it selectively rather than "doing
  PMBOK" wholesale.
- **Citing an edition without checking which one** — PMBOK has gone
  through multiple editions with real structural differences (notably
  the shift from process-groups/knowledge-areas toward principles and
  performance domains); confirm which edition a specific claim or
  certification requirement refers to.
- **Confusing PMBOK with PMP** — PMBOK is the body of knowledge; PMP is
  PMI's certification that tests knowledge of it (among other things);
  the two names are related but not interchangeable.
- **Assuming PMBOK is the only recognized project-management standard**
  — other frameworks (PRINCE2, and various agile-specific bodies of
  knowledge) exist alongside it, each with different scope and
  philosophy.

## Learn more

- [Project Management Institute (PMI)](https://www.pmi.org/) — publisher of the PMBOK Guide.
- [[project-management]] for the general, methodology-independent discipline.
- [[prince2]] for a specific, prescriptive alternative methodology.
- [[software-engineering-body-of-knowledge]] for the parallel body-of-knowledge standard in software engineering specifically.