ExamFinch.com My Study

Study guide

1.2 PMBOK 7th Edition Overview

Practice this exam

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

1.2 PMBOK 7th Edition Overview

Key Takeaways Explain This Topic AI

PMBOK 7 shifted from a process-based model (49 processes) to a principle-based model built on 12 principles

Eight performance domains replaced the ten knowledge areas: Stakeholders, Team, Development Approach & Life Cycle, Planning, Project Work, Delivery, Measurement, Uncertainty

Quality is a principle (build quality in), not a separate performance domain — a frequent exam trap

The Standard for Project Management defines a value delivery system spanning projects, programs, and portfolios

The CAPM also draws on Process Groups: A Practice Guide, which retains the 5 process groups and ITTOs from PMBOK 6

Last updated: October 2026

A Shift in Philosophy

Note

PMI published the PMBOK Guide – Eighth Edition in November 2025 (six principles and seven performance domains). The current CAPM Exam Content Outline lists the Seventh Edition among the references its questions are drawn from, so this section teaches the Seventh Edition model.

The PMBOK Guide — Seventh Edition (released 2021) was 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.

  • Aspect PMBOK 6 PMBOK 7
  • Core unit 49 processes 12 principles
  • Structure 10 Knowledge Areas 8 Performance Domains
  • Emphasis Inputs, Tools, Outputs (ITTOs) Outcomes and value
  • Scope PM processes Value delivery system
  • Approach bias Mostly predictive All approaches
  • The 12 Principles

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

Be a diligent, respectful, caring steward — act ethically, protect resources and the environment.

Create a collaborative team environment — build trust and psychological safety.

Effectively engage stakeholders — understand needs and influence, not just inform.

Focus on value — tie work to benefits, not just scope/schedule/cost.

Recognize and respond to system interactions — see the project inside its larger system.

Demonstrate leadership behaviors — anyone can lead; adapt your style.

Tailor based on context — fit method to project size, risk, and culture.

Build quality into processes and deliverables — prevention over inspection.

Navigate complexity — use systems thinking for ambiguity.

Optimize risk responses — manage both threats and opportunities.

Embrace adaptability and resiliency — learn and recover.

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.

  • Performance Domain Focus
  • Stakeholders Engaging those who affect/are affected
  • Team Building a high-performing team
  • Development Approach & Life Cycle Choosing predictive/adaptive/hybrid and phases
  • Planning Organizing and detailing the work
  • Project Work Executing and managing resources/procurement
  • Delivery Delivering scope, requirements, and value
  • Measurement Metrics, EVM, and forecasting
  • Uncertainty Risk, ambiguity, complexity

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.

  • Source document What it gives the CAPM
  • PMBOK 7 12 principles, 8 performance domains, tailoring
  • Process Groups: A Practice Guide 5 process groups, 49 processes, ITTOs
  • Agile Practice Guide Scrum, Kanban, XP, hybrid
  • PMI Guide to Business Analysis Requirements, traceability, roadmaps

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.

  • Symptom in a scenario Most likely domain
  • Unclear or shifting requirements Delivery / Planning
  • Surprised or disengaged sponsor Stakeholders
  • Team conflict or low morale Team
  • Repeated unforeseen events Uncertainty
  • Schedule/cost off track with no early warning Measurement
  • 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.