Project scope statement
“Project Scope Statement” is an output for the process “Define Scope”.
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.
Although the project charter and the project scope statement are sometimes perceived as containing a certain degree of redundancy, they are different in the level of detail contained in each. The project charter contains highlevel information, while the project scope statement contains a detailed description of the scope elements. These elements are progressively elaborated throughout the project. Table 5-1 describes some of the key elements for each document.
Table 5-1. Elements of the Project Charter and Project Scope Statement Project Charter Project purpose or justification Measurable project objectives and related success criteria High-level requirements High-level project description High-level risks Summary milestone schedule Summary budget Stakeholder list Project approval requirements (what constitutes success, who decides it, who signs off) Assigned project manager, responsibility, and authority level Name and authority of the sponsor or other person(s) authorizing the project charter Project Scope Statement Project scope description (progressively elaborated) Acceptance criteria Project deliverables Project exclusions Project constraints Project assumptions
“Project Scope Statement” is an input for the process “Create WBS”.
The project scope statement describes the work that will be performed and the work that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
“Project Scope Statement” is an input for the process “Sequence Activities”.
The project scope statement contains the product scope description, which includes product characteristics that may affect activity sequencing, such as the physical layout of a plant to be constructed or subsystem interfaces on a software project. Other information from the project scope statement including project deliverables, project constraints, and project assumptions may also affect activity sequencing. While these effects are often apparent in the activity list, the product scope description is generally reviewed to ensure accuracy.
“Project Scope Statement” is an input for the process “Estimate Activity Durations”.
The assumptions and constraints from the project scope statement are considered
when estimating the activity durations. Examples of assumptions include, but are not limited to:
– Existing conditions,
– Availability of information, and – Length of the reporting periods.
Examples of constraints include, but are not limited to:
– Available skilled resources, and – Contract terms and requirements.
“Project Scope Statement” is an input for the process “Develop Schedule”.
The project scope statement contains assumptions and constraints that can impact the development of the project schedule.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping