1.2 PMBOK 7th Edition Overview

A Shift in Philosophy

The PMBOK Guide — Seventh Edition (released 2021) is the biggest structural change in PMI's flagship standard. It moves from a process-based model to a principle-based one, acknowledging that real projects mix predictive, agile, and hybrid approaches.

The 12 Principles

Principles are values that guide judgment, not checklist steps. The exam often asks which principle a scenario illustrates.

1. Be a diligent, respectful, caring steward — act ethically, protect resources and the environment.
2. Create a collaborative team environment — build trust and psychological safety.
3. Effectively engage stakeholders — understand needs and influence, not just inform.
4. Focus on value — tie work to benefits, not just scope/schedule/cost.
5. Recognize and respond to system interactions — see the project inside its larger system.
6. Demonstrate leadership behaviors — anyone can lead; adapt your style.
7. Tailor based on context — fit method to project size, risk, and culture.
8. Build quality into processes and deliverables — prevention over inspection.
9. Navigate complexity — use systems thinking for ambiguity.
10. Optimize risk responses — manage both threats and opportunities.
11. Embrace adaptability and resiliency — learn and recover.
12. Enable change to achieve the future state — manage adoption and transition.

Worked Example

A sponsor asks the team to skip a planned code review to hit a date. Choosing to keep the review because defects cost more to fix later reflects Principle 8 (Build quality in) — prevention is cheaper than rework. If instead the team re-scopes to deliver the highest-benefit features first, that is Principle 4 (Focus on value).

The 8 Performance Domains

These are interdependent areas you manage continuously; they are not sequential phases.

Trap: Quality is NOT one of the eight domains — it lives in Principle 8 and is folded into Delivery. Likewise, Risk is not a standalone domain; it sits inside Uncertainty.

Value Delivery System

The Standard for Project Management (bound with PMBOK 7) describes a value delivery system: organizations create value through portfolios, programs, projects, products, and operations, all aligned to strategy via Organizational Project Management (OPM). The mental model is information flowing up (status, value) and direction flowing down (strategy).

Why the CAPM Still Tests Processes

Because many organizations still run predictive projects, the CAPM also draws on Process Groups: A Practice Guide, which preserves the legacy structure:

• 5 process groups: Initiating, Planning, Executing, Monitoring & Controlling, Closing.
• 49 processes mapped across 10 knowledge areas.
• ITTOs for each process.

CAPM Exam Tip: Expect questions phrased in both vocabularies. You may be asked which process group a charter belongs to (Initiating) and, separately, which principle a tailoring decision reflects. Know the mapping, not just one model.

How the Domains Interact

A key PMBOK 7 idea is that performance domains operate simultaneously, not as a pipeline. While the team plans (Planning), it is also engaging stakeholders (Stakeholders), choosing an approach (Development Approach & Life Cycle), and tracking early metrics (Measurement). Exam scenarios test this by describing one situation and asking which domain's outcome is at stake. For example, a stakeholder who is surprised by a deliverable signals a gap in the Stakeholders domain, even if the deliverable itself was technically correct.

Tailoring: The Connective Tissue

Tailoring (Principle 7) is the bridge between principle-based and process-based thinking. PMBOK 7 expects you to select the right amount of process for the context rather than apply all 49 processes mechanically. A tiny, low-risk internal project may need only a lightweight charter and a checklist; a regulated, high-stakes project may need the full process set plus extra governance. On the CAPM, the correct answer to "how much process should we use?" is almost always enough to fit the context, never "always use everything" or "skip planning to save time."

Models, Methods, and Artifacts

PMBOK 7 also introduces a section on commonly used models (for example, situational leadership, Tuckman's team-development stages, the Salience model for stakeholders), methods (estimating, data analysis), and artifacts (charters, backlogs, registers). The CAPM may ask you to recognize an artifact by its purpose. Memorize a few high-yield pairings: a stakeholder register records who the stakeholders are and their interests; a RACI chart assigns Responsible/Accountable/Consulted/Informed roles; a risk register logs risks and responses; a product backlog holds prioritized work for adaptive delivery.