Typically this process involves collecting requirements, defining scope, creating WBS, verifying scope and controlling the scope. The project scope statement, WBS and WBS dictionary defines the scope baseline. Controlling the scope process must minimize scope creep.

Scope management in project management involves defining, controlling, and managing what is and is not included in a project. It encompasses the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Here’s a more detailed breakdown of what scope management involves:

Scope Planning: This involves outlining the scope of the project, including its objectives, deliverables, constraints, assumptions, and what is considered in and out of scope. It’s crucial to have a clear understanding of what the project will and will not entail.
Scope Definition: This step involves further detailing the project scope by identifying specific tasks, requirements, features, and functionalities. It’s about breaking down the project into manageable components.
Scope Verification: This is the process of formalizing acceptance of the project scope. It involves getting stakeholders’ agreement that all the work required and only the work required has been completed satisfactorily.
Scope Control: This is about monitoring and controlling changes to the project scope. It includes ensuring that any changes are assessed for their impact on the project’s objectives, schedule, budget, and other constraints. Scope control helps prevent scope creep, which is the unauthorized expansion of project scope.

In essence, scope management is about defining what needs to be done, ensuring that it gets done, and controlling changes to it throughout the project lifecycle. It’s a critical aspect of project management as it helps ensure that projects stay on track, within budget, and deliver the intended outcomes.