Figure Inputs Tools and Techniques in Scope Management
PMBOK v8 Definition
Figure Inputs, Tools and Techniques, and Outputs (ITTOs) represent the standardized framework used across all project management processes in PMBOK v8, showing the specific inputs required, tools and techniques applied, and outputs produced for each process. Within the Scope Performance Domain, these ITTOs are visualized in Figures 2-13 through 2-19, covering processes from Plan Scope Management through Validate Scope, each with its unique combination of inputs, tools and techniques, and outputs that must be memorized for exam success.
Why It Matters for the Exam
PMI exam questions frequently test your ability to identify which inputs feed into which scope processes, what tools are used at each stage, and what outputs are produced. These ITTO questions appear in approximately 15-20% of the exam, often as scenario-based questions where you must select the correct tool for a given situation or identify missing inputs/outputs in a process flow.
Key Points to Remember (for the exam)
- Plan Scope Management Inputs: Project charter, project management plan (all components), enterprise environmental factors, organizational process assets
- Elicit and Analyze Requirements Inputs: Project charter, project management plan (scope management plan, requirements management plan, stakeholder engagement plan), project documents, business documents, agreements, enterprise environmental factors, organizational process assets
- Define Scope Inputs: Project charter, project management plan (scope management plan), project documents (assumption log, requirements documentation, risk register), enterprise environmental factors, organizational process assets
- Develop Scope Structure (WBS) Inputs: Project management plan (scope management plan), project documents (project scope statement, requirements documentation), enterprise environmental factors, organizational process assets
- Validate Scope Inputs: Project management plan (scope management plan, requirements management plan, change management plan), project documents (lessons learned register, quality reports, requirements documentation, requirements traceability matrix), verified deliverables, work performance data
- Monitor and Control Scope Inputs: Project management plan (scope management plan, requirements management plan, change management plan, performance measurement baseline), project documents (assumption log, lessons learned register, requirements documentation, requirements traceability matrix), work performance data, agreements
- Common Confusion: Confusing "Define Scope" (creates project scope statement) with "Develop Scope Structure" (creates WBS and WBS dictionary) – they are sequential but distinct processes
Typical PMI Exam Example
A project manager is reviewing stakeholder requirements and needs to document, prioritize, and baseline these requirements before creating the WBS. Which process is being performed? Answer: Elicit and Analyze Requirements (Figure 2-15), which uses tools such as interviews, focus groups, and document analysis to produce requirements documentation and requirements traceability matrix.
PMI Exam Traps
- Trap: Thinking "Validate Scope" happens after "Control Scope" → Reality: Validate Scope occurs before Control Scope in the process flow, and Validate Scope focuses on acceptance of deliverables while Control Scope monitors scope changes
- Trap: Confusing "Verified Deliverables" (output of Control Quality) with "Accepted Deliverables" (output of Validate Scope) → Reality: Verified deliverables are inputs to Validate Scope; accepted deliverables are outputs of Validate Scope
- Trap: Assuming all scope processes use the same inputs → Reality: Each scope process has unique inputs; for example, only Validate Scope uses "verified deliverables" as an input
- Trap: Thinking the WBS is created during Define Scope → Reality: The WBS is created during Develop Scope Structure (Figure 2-17), not Define Scope (Figure 2-16)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Charter | Input to Plan Scope Management, Elicit and Analyze Requirements, Define Scope | The project charter provides high-level requirements and project description that feed into scope processes |
| Requirements Management Plan | Component of Project Management Plan | Guides how requirements will be elicited, analyzed, documented, and managed throughout the project |
| Change Management Plan | Input to Validate Scope and Monitor and Control Scope | Controls how scope changes are processed and approved |
| Work Performance Data | Input to Validate Scope and Monitor and Control Scope | Provides raw data about completed work and work in progress for scope verification and monitoring |
Quick Review Questions
- Which scope process uses "verified deliverables" as an input, and what is the corresponding output?
- What is the difference between the outputs of Define Scope and Develop Scope Structure?
- Which tools and techniques are used in Elicit and Analyze Requirements but not in Define Scope?
- What inputs are shared between Validate Scope and Monitor and Control Scope?
- Which project documents serve as inputs to both Define Scope and Develop Scope Structure?
PMBOK v8 Reference
Section 2.3 - Scope Performance Domain Figures 2-13 through 2-19, pages 39-44 Specifically: Figure 2-14 (Plan Scope Management), Figure 2-15 (Elicit and Analyze Requirements), Figure 2-16 (Define Scope), Figure 2-17 (Develop Scope Structure), Figure 2-18 (Monitor and Control Scope), Figure 2-19 (Validate Scope)