A Guide to the Project Management Body of Knowledge

Published by the Project Management Institute (PMI), this seventh edition contains two integrated components: The Standard for Project Management, which carries formal designation as an American National Standard (ANSI/PMI 99-001-2021), and the PMBOK® Guide, which provides practical guidance for applying the standard's principles. The edition departs significantly from its predecessors, shifting from a prescriptive, process-based framework to one organized around principles and performance domains, which are interactive, interrelated, and interdependent areas of project focus. It also introduces PMIstandards+, a digital content platform that supplements the printed publication with current and emerging practices.

The Preface situates the revision within a rapidly evolving project management landscape. Stakeholder feedback emphasized four priorities: maintaining credibility and relevance, improving readability, providing vetted supplemental content, and preserving value from previous editions. The Preface traces the PMBOK® Guide's evolution from its 1987 origins, noting milestones such as the 1996 shift to a process-based standard, the 2004 Third Edition's formal ANSI designation, and the 2017 Sixth Edition's first incorporation of agile content. The Seventh Edition replaces the Knowledge Areas of prior editions, which organized content into topic-based management categories, with eight performance domains and introduces sections on tailoring and on models, methods, and artifacts.

The standard opens by defining essential terminology. A project is a temporary endeavor to create a unique product, service, or result. Project management is the application of knowledge, skills, tools, and techniques to meet project requirements. Value is the worth, importance, or usefulness of something, perceived differently by different stakeholders. An outcome is an end result focusing on benefits and value beyond mere outputs. Additional terms include portfolio (projects, programs, and operations managed as a group to achieve strategic objectives), program (related projects managed coordinately for benefits unavailable individually), and system for value delivery (strategic business activities aimed at advancing an organization). The standard applies regardless of industry, size, or delivery approach: predictive (well-defined requirements with substantial up-front planning), adaptive (short iterations under uncertain requirements), or hybrid (combining both).

The standard presents a systems view of value delivery. Projects exist within larger systems and create value through new products or services, social or environmental contributions, improved efficiency, or organizational change. Value delivery components, including portfolios, programs, projects, products, and operations, work together in alignment with organizational strategy. Information flows bidirectionally: Senior leadership shares strategic direction downward through portfolios to programs and projects, while performance information flows upward. Governance systems provide oversight, control, and decision-making frameworks. Internal factors (such as organizational culture and employee capability) and external factors (such as marketplace conditions and regulatory requirements) also shape project outcomes.

The core of the standard presents 12 principles, developed through engagement with a global practitioner community. These are foundational behavioral guidelines aligned with the PMI Code of Ethics and Professional Conduct. The first principle calls for diligent, respectful stewardship encompassing integrity, trustworthiness, and compliance. The second advocates creating a collaborative team environment with clear distinctions among authority, accountability (which cannot be shared), and responsibility (which can be shared). The third emphasizes proactive stakeholder engagement, recognizing that stakeholders can influence scope, schedule, cost, quality, risk, and project success. The fourth focuses on value as the ultimate success indicator; if a project no longer aligns with its intended value, the organization may terminate it.

The fifth principle addresses systems thinking, urging teams to recognize how project components interact with each other and with external systems. The sixth concerns leadership, distinguished from formal authority; effective leadership can come from any team member and adapts to the situation. The seventh advocates tailoring based on context, using "just enough" process. The eighth calls for building quality into processes and deliverables across dimensions such as performance, reliability, and sustainability.

The ninth principle addresses complexity arising from human behavior, system behavior, ambiguity, and technological innovation. The tenth focuses on optimizing risk responses, defining risk as an uncertain event or condition with potential positive or negative effects on objectives. The eleventh embraces adaptability (responding to changing conditions) and resiliency (recovering from setbacks), supported by short feedback loops and continuous learning. The twelfth concerns enabling change, distinguishing organizational change management from project change control and favoring motivational over forceful strategies.

The PMBOK® Guide builds on these principles through eight performance domains that run concurrently throughout a project. The Stakeholder Performance Domain covers identifying, analyzing, prioritizing, engaging, and monitoring stakeholders. The Team Performance Domain addresses management structures, servant leadership (focused on understanding team needs and removing obstacles), team culture, and skills including emotional intelligence and conflict management. The Development Approach and Life Cycle Performance Domain describes delivery cadences (single, multiple, periodic, or continuous) and development approaches from predictive to adaptive, with hybrid approaches combining elements of both through iterative (repeated cycles that refine outputs) and incremental (delivering work in successive usable pieces) methods; factors such as requirements certainty and organizational capability inform the selection.

The Planning Performance Domain covers estimating, scheduling, budgeting, communication, procurement, and alignment. Estimating addresses range, accuracy, precision, and confidence through deterministic, probabilistic, and flow-based methods (which calculate estimates from work flow rates and throughput). Schedule compression techniques include crashing (adding resources) and fast tracking (performing sequential activities in parallel). The Project Work Performance Domain addresses process optimization through lean methods and retrospectives, balancing competing constraints, managing procurement, and fostering learning through explicit and tacit knowledge transfer.

The Delivery Performance Domain centers on scope, requirements, and quality. Scope may be elaborated through work breakdown structures or agile constructs such as themes (broad groupings of related work), epics (large requirements broken into smaller items), and user stories (short descriptions of needs from the user's perspective). Quality is addressed through the cost of quality framework, which categorizes prevention, appraisal, internal failure, and external failure costs. The Measurement Performance Domain presents key performance indicators, metrics following SMART criteria (specific, meaningful, achievable, relevant, timely), and presentation methods including dashboards and information radiators (highly visible displays sharing current project data). Measurement pitfalls include the Hawthorne effect (behavior changes when people know they are being measured), vanity metrics, and confirmation bias. The Uncertainty Performance Domain addresses ambiguity, complexity, volatility, and risk; threats may be avoided, escalated, transferred, mitigated, or accepted, while opportunities may be exploited, shared, enhanced, or accepted.

The Tailoring section presents a four-step process: selecting an initial development approach using a suitability filter (criteria evaluating culture, team, and project factors for fit), tailoring for the organization, tailoring for the project, and implementing ongoing improvement. The Models, Methods, and Artifacts section catalogs commonly used tools, including leadership and communication models, change models such as Kotter's 8-Step Process and the ADKAR® Model, complexity frameworks such as the Cynefin framework, estimating methods, and artifacts from project charters to kanban boards. Appendices address project sponsors as critical success factors, the evolving forms of project management offices, the transition toward product-centric thinking, and the research methodology behind the standard's development, including a public exposure draft that drew comments from nearly 600 individuals.