Explanation/Reference:
Explanation:
5.3.3.1 Project Scope Statement
The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. The project scope statement documents the entire scope, including project and product scope.
It describes, in detail, the project's deliverables and the work required to create those deliverables. It also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team's work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project's boundaries.
The degree and level of detail to which the project scope statement defines the work that will be performed and the work that is excluded can help determine how well the project management team can control the overall project scope. The detailed project scope statement, either directly, or by reference to other documents, includes the following:
Product scope description. Progressively elaborates the characteristics of the product, service, or result
described in the project charter and requirements documentation.
Acceptance criteria. A set of conditions that is required to be met before deliverables are accepted.
Deliverable. Any unique and verifiable product, result, or capability to perform a service that is required to
be produced to complete a process, phase, or project. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.
Project exclusion. Generally identifies what is excluded from the project. Explicitly stating what is out of
scope for the project helps to manage stakeholders' expectations.
Constraints. A limiting factor that affects the execution of a project or process. Constraints identified with
the project scope statement list and describe the specific internal or external restrictions or limitations associated with the project scope that affect the execution of the project, for example, a predefined budget or any imposed dates or schedule milestones that are issued by the customer or performing organization.
When a project is performed under an agreement, contractual provisions will generally be constraints.
Information on constraints may be listed in the project scope statement or in a separate log.
Assumptions. A factor in the planning process that is considered to be true, real, or certain, without proof
or demonstration. Also describes the potential impact of those factors if they prove to be false. Project teams frequently identify, document, and validate assumptions as part of their planning process.
Information on assumptions may be listed in the project scope statement or in a separate log.
The project team must complete a scope statement for developing a common understanding of the project scope among stakeholders. This lists project deliverables - summary level sub-products, whose full and satisfactory delivery marks the completion of the project.
5.4 Create WBS
Definition: WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. Key Benefit: The key benefit of this process is that it provides a structured vision of what has to be delivered.
Inputs
1. Scope management plan
2. Project scope statement
3. Requirements documentation
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Decomposition
2. Expert judgment
Outputs
1. Scope baseline
2. Project documents updates
