Does the "Plan Scope Management Process" contain many sub-processes? The PMBOK 5th edition has 24 processes for the Planning Process Group. For the Knowledge Area of "Project Scope Management," we have the following: * Plan Scope Management Process * Collect Requirements * Define Scope * Create WBS * Validate Scope * Control Scope Based on the online tutorial that I've read, it seems that "Plan Scope Management Process" contains the following: * Collect Requirements * Define Scope * Create WBS * Validate Scope * Control Scope Therefore, is it reasonable to view "Plan Scope Management Process" as the process containing the previous items as sub-processes? This seems clearer because "Plan Scope Management Process" appears dependent on these other things.

Plan Scope Management Process (as part of the process group) is mostly concerned about how scope will be managed during the project: after discovering requirements, how it will be decided if they are part of scope or not; how to determine their priority / complexity; and later, how to handle scope changes

PMI suggests to consider those topics in advance, so the scope / requirement management plans must be outlined before starting requirements analysis, scope definition, etc. Of course, it will be refined during planning processes.