Approach Processes More: Integrating ITTOs and Performance Domains

PMBOK v8 Definition

This edition integrates ITTOs and process descriptions directly into the performance domain structure. This combined approach provides both a thorough understanding of individual processes and a broader view of how those processes interact to produce the desired project results. The guide presents 40 processes to describe the underlying mechanics of performance domain activities, with each process listing a sampling of inputs, tools and techniques, and outputs—these are illustrative but not comprehensive, and are not intended as a prescriptive framework or methodology.

Why It Matters for the Exam

The PMI exam frequently tests your ability to understand how processes interconnect within performance domains rather than memorizing isolated ITTOs. Questions appear in situational scenarios where you must identify which process applies, what input is needed, or which tool is appropriate—testing your grasp of process mechanics within the broader domain context.

Key Points to Remember (for the exam)

• Core Structure: 40 nonprescriptive processes organized within 7 performance domains, not Knowledge Areas
• Key Integration: ITTOs are embedded inside performance domain descriptions—not in separate sections
• Purpose: Processes describe the underlying mechanics of performance domain activities
• Critical Distinction: Processes are illustrative, not comprehensive—they offer technical descriptions, not prescriptions
• Tailoring Connection: Each performance domain includes tailoring considerations showing how to adapt processes to specific environments
• Focus Areas Mapping: Processes relate to 5 Project Management Focus Areas: Initiating, Planning, Executing, Monitoring and Controlling, and Closing
• Common Confusion: Confusing processes as prescriptive steps vs. understanding them as flexible, adaptable mechanics

Typical PMI Exam Example

A project manager is adapting project management activities for a highly regulated pharmaceutical project. The team needs to understand which inputs are typically used for risk identification within the Planning Focus Area. According to PMBOK v8, the project manager should consult the performance domain processes, which list a sampling of inputs, tools and techniques, and outputs for that activity—recognizing these are illustrative and should be tailored to the regulatory environment.

PMI Exam Traps

• Trap: Thinking ITTOs are exhaustive lists → Reality: They are "a sampling" and "illustrative but not comprehensive"
• Trap: Treating processes as a rigid methodology → Reality: They are nonprescriptive and adaptable to varied approaches, life cycles, and environments
• Trap: Memorizing ITTOs in isolation from domains → Reality: ITTOs are integrated into performance domain structure—you must understand the domain context first
• Trap: Confusing the 40 processes with the 49 processes from PMBOK v6 → Reality: PMBOK v8 synthesized Knowledge Areas into 7 performance domains with 40 processes

Important PMI Connections

Quick Review Questions

1. How many processes does PMBOK v8 present, and what is their intended purpose regarding prescriptiveness?

2. A project manager needs to understand the inputs for a specific process. Where in PMBOK v8 should they look for this information?

3. What is the relationship between the 40 processes and the 7 performance domains?

4. Your exam question describes a process with specific ITTOs. What should you remember about whether these lists are complete or exhaustive?

5. How do tailoring considerations relate to individual processes in PMBOK v8?

PMBOK v8 Reference

Section 2 - Project Management Performance Domains (including Table 2-1 mapping processes to Focus Areas) Section 4 - Inputs and Outputs Section 5 - Tools and Techniques