Define Scope is part of the “Scope Management” Knowledge Area, and is part of the “Planning” Process Group.
Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the project, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.
Since all of the requirements identified in Collect Requirements may not be included in the project, the Define Scope process selects the final project requirements from the requirements documentation delivered during the Collect Requirements process. It then develops a detailed description of the project and product, service, or result.
The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverables, assumptions, and constraints that are documented during project initiation. During project planning, the project scope is defined and described with greater specificity as more information about the project is known.
Existing risks, assumptions, and constraints are analyzed for completeness and added or updated as necessary.
The Define Scope process can be highly iterative. In iterative life cycle projects, a high-level vision will be developed for the overall project, but the detailed scope is determined one iteration at a time and the detailed planning for the next iteration is carried out as work progresses on the current project scope and deliverables.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping
[/three_fourth]
[one_fourth_last]
Define Scope has:
Inputs:
- Organizational Process Assets
- Project charter
- Requirements documentation
- Scope management plan
Outputs:
- Project documents updates
- Project scope statement
Tools and techniques:
- Alternatives generation
- Expert judgment
- Facilitated workshops
- Product analysis
[/one_fourth_last]