Figure Inputs Tools and Techniques: The ITTO Framework for Exam Success

Figure Inputs Tools and Techniques: The ITTO Framework for Exam Success

PMBOK v8 Definition

The "Figure Inputs Tools and Techniques and Outputs" (ITTO) framework is the foundational structure used across all PMBOK v8 processes to define what is needed (Inputs), how work is performed (Tools and Techniques), and what is produced (Outputs). Each process within the Governance Performance Domain and other performance domains follows this standardized ITTO format, as illustrated in Figures 2-3 through 2-43 of PMBOK v8, providing a consistent method for understanding process execution from initiation through closure.

Why It Matters for the Exam

ITTO questions appear in approximately 30-40% of PMI exam items, making this the single most tested concept in the entire exam. The exam frequently asks you to identify which input belongs to which process, which tool produces which output, or what the correct sequence of ITTO elements is for a given scenario. Mastering ITTO relationships is essential for passing the PMP certification exam.

Key Points to Remember (for the exam)

  • Core ITTO Structure: Every PMBOK v8 process has three components: Inputs (documents, plans, data), Tools and Techniques (methods, frameworks, technologies), and Outputs (deliverables, updated documents, decisions)

  • Governance Performance Domain Processes: Figure 2-2 shows the Governance Performance Domain includes: Initiate Project or Phase (Figure 2-3), Integrate and Align Project Plans (Figure 2-4), Plan Sourcing Strategy (Figure 2-5), Manage Project Execution (Figure 2-6), Manage Quality Assurance (Figure 2-7), Manage Project Knowledge (Figure 2-8), Monitor and Control Project Performance (Figure 2-9), Assess and Implement Changes (Figure 2-10), and Close Project or Phase (Figure 2-12)

  • Stakeholders Performance Domain Processes: Figure 2-32 shows processes including Identify Stakeholders (Figure 2-33), Plan Stakeholder Engagement (Figure 2-34), Plan Communications Management (Figure 2-35), Manage Stakeholder Engagement (Figure 2-36), Manage Communications (Figure 2-37), Monitor Stakeholder Engagement (Figure 2-38), and Monitor Communications (Figure 2-39)

  • Resources Performance Domain: Figure 2-40 shows Plan Resource Management (Figure 2-41) as a key process with its own ITTO framework

  • Scope and Schedule Processes: Figure 2-17 (Develop Scope Structure), Figure 2-18 (Monitor and Control Scope), Figure 2-19 (Validate Scope), Figure 2-21 (Plan Schedule Management), Figure 2-22 (Develop Schedule)

  • Common Confusion: Inputs are NOT the same as Outputs from other processes—Inputs are documents/data that exist BEFORE the process starts; Outputs are created DURING or AFTER the process

Typical PMI Exam Example

A project manager is initiating a new project phase. According to PMBOK v8, which process should they use? The answer is "Initiate Project or Phase" (Figure 2-3), which has specific inputs, tools and techniques, and outputs that must be followed to properly authorize the phase. The PM must identify the correct inputs (such as project charter) and apply appropriate tools before producing the required outputs.

PMI Exam Traps

  • Trap: Confusing "Manage Quality Assurance" (Figure 2-7) with "Manage Project Execution" (Figure 2-6)

  • Reality: Manage Quality Assurance focuses on quality standards and audits; Manage Project Execution focuses on performing the work defined in the project management plan

  • Trap: Assuming "Monitor and Control Project Performance" (Figure 2-9) is the same as "Assess and Implement Changes" (Figure 2-10)

  • Reality: Monitor and Control tracks performance against baselines; Assess and Implement Changes specifically handles change requests and their approval/rejection

  • Trap: Thinking Inputs are always created within the same process

  • Reality: Inputs typically come from other processes or external sources; they are prerequisites, not products of the current process

  • Trap: Forgetting that "Close Project or Phase" (Figure 2-12) has its own distinct ITTO set

  • Reality: Closure is a formal process with specific inputs (e.g., accepted deliverables) and outputs (e.g., final report, lessons learned)

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Governance Performance DomainContains ITTO processesKnow which figures (2-2 to 2-12) belong to this domain
Stakeholders Performance DomainContains ITTO processesFigures 2-32 to 2-39 are tested together
Resources Performance DomainContains ITTO processesFigure 2-40 and 2-41 are often tested with team management
Scope and Schedule ProcessesITTO applicationFigures 2-17 to 2-22 show scope and schedule ITTOs

Quick Review Questions

  1. Which PMBOK v8 figure shows the ITTO framework for "Initiate Project or Phase"?

  2. What is the difference between an Input and an Output in the ITTO framework?

  3. Which Governance Performance Domain process (Figure 2-2) is responsible for handling change requests?

  4. In the Stakeholders Performance Domain, which figures cover communications management processes?

  5. What is the correct sequence of elements in every PMBOK v8 process ITTO diagram?

PMBOK v8 Reference

Section 2 - Governance Performance Domain (Figures 2-2 through 2-12) Section 2 - Stakeholders Performance Domain (Figures 2-32 through 2-39) Section 2 - Resources Performance Domain (Figures 2-40 through 2-41) Section 2 - Scope Performance Domain (Figures 2-17 through 2-19) Section 2 - Schedule Performance Domain (Figures 2-20 through 2-22)