
Figure Inputs, Tools, and Techniques in Performance Domains
PMBOK v8 Definition
The Figure Inputs, Tools and Techniques, and Outputs (ITTOs) represent the structured framework mapping each project process within PMBOK v8's Performance Domains. These figures systematically document the specific inputs required, tools and techniques applied, and outputs produced for every process across the Governance, Scope, Schedule, Resources, Communications, Stakeholder, and other Performance Domains. Each figure provides a standardized visual reference for the complete process flow, as shown in Figures 2-2 through 2-46 of PMBOK v8.
Why It Matters for the Exam
Understanding the ITTO figures is critical because the PMI exam frequently tests your ability to identify which inputs feed into which processes, which tools are applied, and what outputs are produced. Questions often present a scenario and ask you to select the correct input, tool, or output for a given process. Mastering these figures helps you answer recall-based and application-based questions efficiently.
Key Points to Remember (for the exam)
-
Standardized Structure: Every process figure follows the exact same three-column layout: Inputs (left), Tools and Techniques (center), Outputs (right). This consistency is tested.
-
Process Group Integration: Each figure belongs to a specific Performance Domain process. For example, Figure 2-3 covers "Initiate Project or Phase" under the Governance Performance Domain.
-
Common Inputs Across Processes: Project charter, business documents, enterprise environmental factors, and organizational process assets appear repeatedly as inputs across multiple figures.
-
Distinct Outputs: Each process produces unique outputs. For instance, "Manage Quality Assurance" (Figure 2-7) outputs quality reports and test and evaluation documents, while "Manage Project Knowledge" (Figure 2-8) outputs lessons learned register and project management plan updates.
-
Key Tools: Data analysis, decision making, communication, and interpersonal and team skills are recurring tool categories across processes.
-
Figure Numbering Pattern: Figures are numbered sequentially within each Performance Domain section (e.g., Figures 2-17 through 2-19 for Scope, Figures 2-21 through 2-22 for Schedule).
-
Performance Domain Mapping: Each Performance Domain has a process overview figure (e.g., Figure 2-40 for Resources Performance Domain) that shows how its processes interconnect.
Typical PMI Exam Example
A project manager is developing the project schedule. According to PMBOK v8, which figure provides the complete ITTO framework for this process? The correct answer is Figure 2-22 (Develop Schedule Inputs, Tools and Techniques, and Outputs) under the Schedule Performance Domain. The exam may ask you to identify which specific input (e.g., schedule management plan) or tool (e.g., critical path method) is used in this process.
PMI Exam Traps
-
Trap: Confusing Figure 2-17 (Develop Scope Structure) with Figure 2-18 (Monitor and Control Scope) Reality: Figure 2-17 is for creating the Work Breakdown Structure; Figure 2-18 is for tracking scope changes during execution
-
Trap: Assuming all figures have the same inputs across Performance Domains Reality: Each process has distinct inputs; for example, "Acquire Resources" (Figure 2-43) uses resource management plan as input, while "Lead the Team" (Figure 2-44) uses team performance assessments
-
Trap: Mixing up Figure 2-36 (Manage Stakeholder Engagement) with Figure 2-38 (Monitor Stakeholder Engagement) Reality: Figure 2-36 is about actively engaging stakeholders; Figure 2-38 is about tracking engagement effectiveness
-
Trap: Thinking tools and techniques are identical across similar processes Reality: While some tools repeat (e.g., meetings), each process applies specific techniques; "Plan Resource Management" (Figure 2-41) uses organizational theory, while "Estimate Resources" (Figure 2-42) uses bottom-up estimating
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Governance Performance Domain (Figure 2-2) | Contains initiation and planning processes | Exam tests which governance processes feed into other domains |
| Scope Performance Domain (Figures 2-17 to 2-19) | Sequential dependency | Validate Scope (Figure 2-19) outputs accepted deliverables to Close Project |
| Resources Performance Domain (Figures 2-40 to 2-45) | Process chain | Acquire Resources (Figure 2-43) output feeds into Lead the Team (Figure 2-44) |
| Monitor and Control (Figure 2-9) | Cross-domain integration | This process uses outputs from all other monitoring processes |
Quick Review Questions
-
Which figure provides the ITTO framework for managing quality assurance activities in a project?
-
According to PMBOK v8, what is the main output of the "Acquire Resources" process shown in Figure 2-43?
-
What is the key difference between Figure 2-36 (Manage Stakeholder Engagement) and Figure 2-38 (Monitor Stakeholder Engagement) in terms of their primary outputs?
-
Which Performance Domain process overview figure shows how resource management processes interconnect?
-
In Figure 2-7 (Manage Quality Assurance), what are the three main categories of tools and techniques listed?
PMBOK v8 Reference
Section 2 - Performance Domains and Processes (Figures 2-2 through 2-46)
- Figure 2-3: Initiate Project or Phase Inputs, Tools and Techniques, and Outputs
- Figure 2-7: Manage Quality Assurance Inputs, Tools and Techniques, and Outputs
- Figure 2-8: Manage Project Knowledge Inputs, Tools and Techniques, and Outputs
- Figure 2-9: Monitor and Control Project Performance Inputs, Tools and Techniques, and Outputs
- Figure 2-17: Develop Scope Structure Inputs, Tools and Techniques, and Outputs
- Figure 2-22: Develop Schedule Inputs, Tools and Techniques, and Outputs
- Figure 2-36: Manage Stakeholder Engagement Inputs, Tools and Techniques, and Outputs
- Figure 2-41: Plan Resource Management Inputs, Tools and Techniques, and Outputs
- Figure 2-43: Acquire Resources Inputs, Tools and Techniques, and Outputs