This is the second article in the series “How to remember ITTOs”.

I have written an earlier article on How to remember ITTOs of Integration management? ITTO is an acronym that stands for Inputs, Tools and Techniques, and Outputs.

In this article, we will focus on Project scope management.

What is Project scope management?

Project scope management is the knowledge area in which the team performs the following major activities:

• Collects requirements
• Defines the scope from requirements by developing the project scope statement
• Decomposing the scope further down into more manageable components by developing the Work Breakdown Structure (WBS)
• Inspecting the verified deliverables along with customer to validate the scope
• Monitoring the scope performance of the project and controlling any changes to scope

Process Flow in Project Scope Management

I have suggested process flow diagrams as a way to remember and map the concepts in mind. Following the same approach, I have given the process flow diagram for Project Scope Management below.

I have included ONLY the major inputs and outputs, so that it is easier to understand rather than complicating it too much. Please note that it does NOT include ALL inputs and outputs. I have included only those inputs and outputs, which I felt are important. Please refer to PMBOK Guide for a complete list of ITTOs.

The best way to get the ITTOs in your mind is to draw the process flow diagram yourself. It would help your mind to map the inputs and outputs to the processes; and you would not forget it.

Tips to remember ITTOs of Project Scope Management

1. Organizational Process Assets is an input to 47 processes; only two processes do not take OPA as an input. They are 5.5 Validate Scope and 11.7 Monitor Risks.
2. Expert Judgment is a Tool & Technique used in all the 4 planning processes of Project Scope Management.
3. Enterprise Environmental Factors is an input to all the 4 planning processes of Project Scope Management.
4. Once scope management plan is developed in 5.1 Plan Scope Management, it becomes an input to all the following 5 processes in Project Scope Management.
5. Requirements documentation is developed in 5.2 Collect requirements. It becomes an input to all the following 4 processes in Project Scope Management.
6. Work performance data is an input to the 2 controlling processes; and work performance information is the relevant output from those controlling processes.
7. For all Monitoring & Controlling processes, change requests is an output; the only exception is Perform Integrated Change Control. In this process, change requests is an input and Approved change requests is an output.
8. Decomposition is a tool used in 5.4 Create WBS; it is also used in 6.2 Define Activities. In 5.4, the project scope statement is decomposed into work packages; while in 6.2, the work packages are further decomposed into activities.
9. Inspection is a tool used in 5.5 Validate Scope; it is also used in 8.3 Control Quality and 12.3 Control Procurements. In 8.3, the deliverables are inspected by internal quality control team; following this in 5.5, the deliverables are inspected by the Customer. It is general practice to perform internal quality control ahead of scope validation by customer; but, under special circumstances, you could perform both activities simultaneously. In 12.3, inspection is carried out on the deliverables from seller.

Conclusion

What is your approach to remember ITTOs in Project Scope Management? Do you think the above approach is good? Do you have any other tips you want me to include in the above list?

Share your opinions and comments in the comments box below. I will continue to work on the process flow diagram for the other knowledge areas.