Document Code: PMBOK5.3.3.

<Organization Name>

<Project Name>
Project Scope Statement
Revision <6.0>

<Note: The text enclosed in angle brackets and usually displayed in blue italics is included to provide the prompt to the
author and must be deleted or replaced by the information specified therein before publishing the document.

Project Scope Statement is created during the process 5.3 "Define Scope" as described in A Guide to the Project
Management Body of Knowledge (PMBOK® Guide)—Sixth Edition . It is shown in the document code (the first two digits).
The Project Scope Statement is the description of the project scope, major deliverables, assumptions and constraints.
It is developed on the basis of the Project Charter, Scope Management Plan, Assumption Log, Requirements
Documentation, Risk Register and other information like enterprise environmental factors and organizational process
assets.

The Project Scope Statement documents the entire scope, including project and product scope. It describes the project’s
deliverables in detail. 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.

Note: Before publishing the document, fill in the “Quick Parts” (the blocks of text set in boxes) to insert the appropriate
document properties. Repeated Quick Parts are updated automatically. Update the table of contents just before
publishing.>

For internal use <Organization Name>, 2023 Page 1 of 6

 <Project Name> Revision: <6.0>
Project Scope Statement Date: XXX 0, 0000
Document Code: PMBOK5.3.3.1

List of Changes
Date Revision Description Author
<m/d/yyyy> <6.0> Publication for use <Author>

<The Revision is the revision number of the document (the first digit is increased and the second one is set to zero if significant
changes are made in the document; the second digit changes if the minor changes are made).
The Description is a detailed description of the revision and the amendments (for example, Publication for internal comments,
Publication for use, Publication with changes in Chapter X, etc.).
For Author, provide the full name of the amendments’ author.>

For internal use <Organization Name>, 2023 Page 2 of 6

 <Project Name> Revision: <6.0>
Project Scope Statement Date: XXX 0, 0000
Document Code: PMBOK5.3.3.1

Table of Contents
1. General Provisions

2. Normative References

3. Terms, Notations, Abbreviations

4. Product scope description

5. Deliverables

6. Acceptance criteria

7. Project exclusions

8. Appendixes

1.

For internal use <Organization Name>, 2023 Page 3 of 6

 <Project Name> Revision: <6.0>
Project Scope Statement Date: XXX 0, 0000
Document Code: PMBOK5.3.3.1

1. General Provisions
<This section describes the general characteristics of this document folder and the set of documents to which it refers.
These general provisions can be modified or supplemented in accordance with the particular project requirements.>
1.1. This document refers to <Project Name>, which is implemented by <Organization Name>.
1.2. The Project Scope Statement is the description of the project scope, major deliverables,
assumptions and constraints.
1.3. The Project Scope Statement is included in the Project Documents folder.

<The Project Scope Statement documents the entire scope, including project and product scope. It describes the project’s
deliverables in detail. 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.
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 high-level information,
while the Project Scope Statement contains a detailed description of the scope components. These components are
progressively elaborated throughout the project.>

2. Normative References
<This section should contain a complete list of documents mentioned in this document. Each document should be
identified by corresponding title, number (if applicable), date and name of publishing company or author. Define the
sources that can provide reference information.>

2.1. This document refers to the following documents:

Number Name Publishing Author
Date
A Guide to the Project Management Body of Knowledge
PMBOK® Guide 2017 PMI
— Sixth Edition
PMBOK4.1.3.1 Project Charter PMDoc
PMBOK4.1.3.2 Assumption Log PMDoc
PMBOK4.2.3.1 Project Management Plan PMDoc
PMBOK5.1.3.1 Scope Management Plan PMDoc
PMBOK5.2.3.1 Requirements Documentation PMDoc
PMBOK10.1.3.1 Communications Management Plan PMDoc
PMBOK11.2.3.1 Risk Register PMDoc

For internal use <Organization Name>, 2023 Page 4 of 6

 <Project Name> Revision: <6.0>
Project Scope Statement Date: XXX 0, 0000
Document Code: PMBOK5.3.3.1

3. Terms, Notations, Abbreviations

<This section should contain the definitions of all terms, notations and abbreviations required to properly interpret this
document. The terms, notations and abbreviations should be arranged in alphabetical order. This information can be
presented in the form of the following table, or as a reference to a Project Glossary in the Communications Management
Plan>

3.1. Terms used in this document:

Term Definition
Acceptance Criteria A set of conditions that is required to be met before deliverables are
accepted.
Assumption A factor in the planning process that is considered to be true, real or
certain, without proof or demonstration.
Constraint A limiting factor that affects the execution of a project, program, portfolio
or process.
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.
Enterprise Conditions, not under the immediate control of the team, that influence,
Environmental constrain or direct the project, program or portfolio.
Factors
Objective Something toward which work is to be directed, a strategic position to be
attained, a purpose to be achieved, a result to be obtained, a product to
be produced or a service to be performed.
Organizational Plans, processes, policies, procedures and knowledge bases that are
Process Assets specific to and used by the performing organization.
Product An artifact that is produced, is quantifiable and can be either an end item
in itself or a component item. Additional words for products are material
and goods. (See also: deliverable)
Requirement A condition or capability that is necessary to be present in a product,
service or result to satisfy a business need.
Stakeholder An individual, group or organization that may affect, be affected by (or
perceive itself to be affected by) a decision, activity or outcome of a
project, program or portfolio.

3.2. Notations used in this document:

Notation Complete Form
Organization <Organization Name>

3.3. Abbreviations used in this document:

Abbreviation Complete Form
PMBOK Project Management Body of Knowledge
WBS Work Breakdown Structure

For internal use <Organization Name>, 2023 Page 5 of 6

 <Project Name> Revision: <6.0>
Project Scope Statement Date: XXX 0, 0000
Document Code: PMBOK5.3.3.1

4. Product scope description

<This section documents the narrative description of the product scope. The product scope description progressively
elaborates the characteristics of the product, service or result described in the Project Charter and Requirements
Documentation.>
5. Deliverables
<This section describes 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 are typically the outcomes of the project and can include
components of the Project Management Plan. 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. Deliverables may
be tangible or intangible.

Change control should be applied once the first version of a deliverable has been completed. The control of the multiple
versions or editions of a deliverable (e.g., documents, software and building blocks) is supported by configuration
management tools and procedures.>
6. Acceptance criteria
<This section documents a set of conditions that is required to be met before deliverables are accepted. The definition of
acceptance criteria may significantly increase or decrease quality costs and, therefore, project costs. Satisfying all
acceptance criteria implies the needs of the stakeholders have been met.

Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. Formal
documentation received from the customer or sponsor acknowledging formal stakeholder acceptance of the project’s
deliverables is forwarded to the Close Project or Phase process.>
7. Project exclusions
<This section identifies what is excluded from the project. Explicitly stating what is out of scope for the project helps
manage stakeholders’ expectations and can reduce scope creep.>
8. Appendixes
<This section contains all appendixes to the document. In the absence of appendixes, this section is excluded from the
document.>

<Note: Fill in the Quick Parts and update the Table of Contents before publishing the document.>

For internal use <Organization Name>, 2023 Page 6 of 6