Project Management uses the term “project scope statement” often. It is part of the project management knowledge area Scope Management, as stated in the PMP certification course. Scope Management, which is PMP Scope Management, helps to define the scope of the project. Six processes are involved in this knowledge area. The second process, Define Scope, produces the primary output: Project Scope statement. We will describe Scope Statement in greater detail in this article.
Take part in our 100% online & self-paced 1-hour PMP training.

What is the Project Scope Statement (or Project Scope Statement)?
An online PMP course will teach you that the Project Scope Statement, which is the primary output from the Define Scope process, can be found. This process defines the project’s boundaries, outlines the work to be done throughout the project, and identifies the main deliverables. After reviewing and evaluating all customer requirements, the Define Scope process aims to finalize the project scope.

The scope statement for a project officially outlines the work that will be done. Every stakeholder in the project must agree to the scope statement once it is prepared. Because it will contain the detailed scope of the project as well as what will be delivered throughout it.
Scope baseline is a baseline project. The Scope Statement, Work Breakdown Structure Dictionary and Scope Statement together form the Scope baseline. The work breakdown structure shows the hierarchy and deliverables of project deliverables. The Work Breakdown Structure Dictionary gives detailed information about each item within the Work Breakdown Structure.

The project scope statement is an important part of the project management plan. Although it is not a management plan, it is an important document as it will detail the scope of the project.
What is included?
Let’s now look at the scope statement and the 5 items it contains.

Product Scope: The product scope is an output of the project. Features, specifications, and details about the product can be found in the product scope. Because the product is a project deliverable it will also be included in the Project Scope Statement.
Deliverables: Projects will produce deliverables until the project scope is complete. Let’s say you are working on an e-commerce website project. For sure, the final product will be an end-to-end functioning e-commerce shopping site. There will be interim deliverables like login screen, category page and member profile screen. These interim deliverables can be used to test the customer’s product before delivery. These deliverables are a smaller part of the overall project scope and are included in the scope statement.
Product Acceptance Criteria: This is a list of conditions under which the customer will accept the project. This is a handshake between project team and customer. It explains how the customer will accept the final project. These criteria are usually derived from requirements. If the customer agrees that the member login will take less than two seconds, it is written in product acceptance criteria. Customer must accept if the member logins are completed successfully in less then 2 seconds when the ecommerce shopping website is ready to go.

What is not part the project? It must be included in the project scope statement. Some project stakeholders might consider some items outside of the scope of the project scope. It is important to clearly define the critical points that are not within the scope of the project. Let’s say you are installing a new database.