
Project Management Processes: 40 Nonprescriptive Activities for Performance Domains
PMBOK v8 Definition
Project management processes are a formalized series of logically connected activities that manage a project throughout its life cycle. The PMBOK v8 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 processes are illustrative but not comprehensive, offering a technical description of project management without being a prescriptive framework or methodology. The 40 processes are organized across seven performance domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk.
Why It Matters for the Exam
The 40 processes form the operational backbone of the PMBOK v8 exam. PMI tests your ability to identify which process belongs to which performance domain, what its key inputs and outputs are, and how processes connect across domains. Exam questions frequently present a scenario and ask you to select the correct process, its primary output, or the domain it supports. Mastering the 40 processes is essential for situational and definitional questions.
Key Points to Remember (for the exam)
-
40 Nonprescriptive Processes: The PMBOK v8 includes exactly 40 processes. They are not a mandatory methodology-they are illustrative industry practices that teams adapt through tailoring.
-
Seven Performance Domains: Each process belongs to one of seven domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, or Risk. No process belongs to more than one domain.
-
Inputs, Tools & Techniques, Outputs (ITTOs): Each process has a sampling of ITTOs. The exam tests recognition of the primary ITTO for key processes-not every possible input or output.
-
Processes Are Logically Connected: Processes are not isolated; they form a series of activities that manage the project across its life cycle. Outputs from one process often become inputs to another.
-
Tailoring Is Expected: Processes can be adapted to varied approaches, life cycles, and environments. The exam tests whether you know when to tailor, not how in detail.
-
Relationship to Focus Areas: Processes map to five Project Management Focus Areas: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Each process aligns with one focus area.
-
Artifacts and Approaches Repeat: Several artifacts and approaches are used in multiple processes. This interconnectivity is frequently tested-know which artifacts appear in more than one domain.
Typical PMI Exam Example
Scenario: A project manager is defining the activities required to produce project deliverables. The team needs to review industry common practices for the Schedule performance domain. According to PMBOK v8, what should the team consult?
Answer: The 40 nonprescriptive processes described in the PMBOK v8 Guide, specifically those within the Schedule performance domain, which list inputs, tools and techniques, and outputs as illustrative industry practices.
PMI Exam Traps
-
Trap: Confusing the 40 processes with a mandatory methodology. Reality: Processes are illustrative, not prescriptive. The exam tests adaptability, not rigid adherence.
-
Trap: Assuming every process has a unique set of ITTOs. Reality: Several artifacts and approaches are used in multiple processes. Overlap is normal and expected.
-
Trap: Memorizing all ITTOs for all 40 processes. Reality: The exam tests recognition of primary ITTOs for key processes, not exhaustive lists. Focus on the most frequently tested connections.
-
Trap: Thinking processes are ordered by importance or sequence. Reality: The seven performance domains have no specific weighting or order. Processes are interrelated and interdependent, not linear.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Performance Domains (7) | Container for processes | Each process belongs to exactly one domain. Know which domain contains which key processes. |
| Focus Areas (Initiating, Planning, Executing, M&C, Closing) | Classification axis | Processes align with one focus area. Exam tests matching processes to focus areas. |
| Tailoring Considerations | Adaptation mechanism | Tailoring examples show how to adjust processes to different life cycles and environments. |
| Artifacts and Approaches | Reusable across processes | Same artifact (e.g., risk register) appears in multiple processes across domains. |
Quick Review Questions
-
How many processes does the PMBOK v8 Guide present to describe the mechanics of performance domain activities?
-
A process in the Stakeholders performance domain lists its inputs, tools and techniques, and outputs. According to PMBOK v8, are these lists comprehensive or illustrative?
-
True or False: The seven performance domains are presented in a specific order of importance.
-
A project team is working on the Schedule performance domain. They need to understand industry common practices. What should they review?
-
Can the same artifact be used in multiple processes across different performance domains?
PMBOK v8 Reference
Section 2, Project Management Performance Domains (Processes section, Table 2-1) Preface (Processes description) Section 4, Inputs and Outputs Section 5, Tools and Techniques