
Tools Techniques Outputs: The Core of Process Framework
PMBOK v8 Definition
Tools, Techniques, and Outputs (T&T&O) represent the standardized framework used across all project management processes in PMBOK v8. Each process is defined by its Inputs (what you need), Tools and Techniques (how you perform the work), and Outputs (what you produce). This ITTO structure appears consistently throughout the Process Groups and Knowledge Areas, as illustrated in Figures 2-7 through 2-46 of PMBOK v8, including processes like Develop Schedule, Manage Quality Assurance, and Monitor Stakeholder Engagement.
Why It Matters for the Exam
The ITTO framework is tested in approximately 30-40% of PMI exam questions, making it the most fundamental concept to master. Questions frequently ask you to identify which tool belongs to which process, what output is produced by a specific process, or what input is required before performing a particular process. Understanding ITTOs is essential for situational questions where you must select the correct process step.
Key Points to Remember (for the exam)
- Three Components Always Present: Every process has Inputs, Tools and Techniques, and Outputs—never missing one component
- Inputs are Always Documents/Plans: Project management plan, project documents, enterprise environmental factors, organizational process assets
- Tools and Techniques are Action Verbs: Expert judgment, data gathering, data analysis, meetings, decision-making techniques
- Outputs are Always Deliverables: Plans, documents, updates, work performance information, change requests
- Common Input Pattern: Most processes share these inputs: project management plan, project documents, EEFs, OPAs
- Outputs Flow as Inputs: Output of one process becomes input to another process (process interdependency)
- Monitor and Control Processes: These always produce work performance information and change requests as outputs
Typical PMI Exam Example
You are developing the project schedule. Which tool and technique would you use to determine the critical path? The correct answer is "Schedule network analysis" (a tool used in Develop Schedule process, Figure 2-22). The input required is the schedule management plan, and the output is the project schedule.
PMI Exam Traps
-
Trap: Confusing "Tools and Techniques" with "Outputs" Reality: Tools are methods (e.g., critical path method), outputs are documents (e.g., project schedule)
-
Trap: Thinking all processes have unique ITTOs Reality: Many processes share common inputs (project management plan, project documents) and tools (expert judgment, meetings)
-
Trap: Confusing "Work Performance Information" with "Work Performance Data" Reality: Work Performance Data is raw data (input), Work Performance Information is analyzed data (output of Monitor and Control processes)
-
Trap: Assuming "Change Requests" are only outputs of change control processes Reality: Change requests are outputs of many Monitor and Control processes (Figures 2-9, 2-10, 2-24, 2-39)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Process Groups | ITTOs differ by group | Planning processes produce plans, Monitoring processes produce work performance information |
| Knowledge Areas | ITTOs are specific to each area | Schedule Management uses schedule network analysis; Quality Management uses quality audits |
| Project Management Plan | Common Input | Always check if the plan is an input before performing any process |
| Change Requests | Common Output | Monitor and Control processes always produce change requests as outputs |
Quick Review Questions
- What are the three mandatory components of every PMBOK v8 process?
- Which output is produced by Monitor and Control Schedule (Figure 2-24)?
- What is the common input shared by all processes in the Schedule Performance Domain?
- Identify the tool and technique used in Develop Schedule (Figure 2-22) for determining activity sequences.
- How do Outputs of one process become Inputs to another process?
PMBOK v8 Reference
Section 2 - Project Performance Domains (Figures 2-7 through 2-46) Specifically Figures 2-22 (Develop Schedule), 2-24 (Monitor and Control Schedule), and all process ITTO diagrams throughout the section