Skip to content
PMPCAPM

Project Scope Statement

The project scope statement is a detailed description of the project scope, major deliverables, assumptions, and constraints that provides a documented basis for making future project decisions.

Share:

Explanation

The project scope statement is the primary output of the Define Scope process and serves as one of the most important project documents. It describes what the project will deliver and the work required to create those deliverables. It also documents assumptions, constraints, and exclusions to set clear boundaries.

Key components include the product scope description, deliverables list, acceptance criteria, project exclusions, assumptions, and constraints. The acceptance criteria define the conditions that must be met before deliverables are accepted by stakeholders, which directly feeds into the Validate Scope process.

The project scope statement is a critical input to Create WBS, where it is decomposed into a hierarchical structure of work packages. Together with the WBS and WBS dictionary, the approved project scope statement forms the scope baseline, which is used to measure project performance and control changes.

Key Points

  • Primary output of the Define Scope process
  • Includes deliverables, acceptance criteria, exclusions, assumptions, and constraints
  • Used as a key input to Create WBS
  • Combined with WBS and WBS dictionary to form the scope baseline

Exam Tip

The scope statement includes acceptance criteria for deliverables. These criteria are critical for Validate Scope, where the customer formally accepts the completed deliverables.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Power/Influence Grid

The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).

Part of

Scope Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.