Project Scope Statement

The project scope statement assists in defining and developing the project and product scope. The project scope statement should contain at least this information:

  • Project scope description
  • Project deliverables
  • Product acceptance criteria
  • Project exclusions

The project scope statement can receive information from:

  • Project charter
  • Assumption log
  • Scope management plan
  • Requirements documentation
  • Risk register

It provides information to:

  • Work breakdown structure
  • Scope baseline

The project scope statement is an output from the process 5.3 Define Scope in the PMBOK® Guide – Sixth Edition. It is developed once and is not usually updated unless there is a significant change in scope.

Tailoring tips

Consider the following tips to help tailor the project scope statement to meet your needs:

  • For smaller projects you can combine the project scope statement with the project charter.
  • For agile projects you can combine the information with the release and iteration plan.


The project scope statement should be aligned and consistent with the following documents:

  • Project charter
  • Work breakdown structure
  • Requirements documentation
Document element Description 
Project scope description Project scope is progressively elaborated from the project description in the project charter and the requirements in the requirements documentation.
Project deliverables Project deliverables are progressively elaborated from the project description key deliv- erables in the project charter.
Product acceptance criteria Acceptance criteria is progressively elaborated from the information in the project charter. Acceptance criteria can be developed for each component of the project.
Project exclusions Project exclusions clearly define what is out of scope for the product and project.
Project constraints Constraints are limitations imposed on the project, such as the limitation of cost, schedule, or resources, and you have to work within the boundaries restricted by these constraints. All projects have constraints, which are defined and identified at the beginning of the project.
Project assumptions An assumption is a belief of what you assume to be true in the future. You make assumptions based on your knowledge, experience or the information available on hand. These are anticipated events or circumstances that are expected to occur during your project’s life cycle.