Scribd
Upload
100 views2 pages

Project Scope Statement Template

The document provides a template for a project scope statement with guidelines for its key elements: the project purpose, goals and objectives, a scope summary and boundary conditions, and details of what is in and out of scope. The scope statement aims to concisely summarize the project scope and boundaries to help team members understand why the project is being done and what work is included.

Uploaded by

Hanseas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
100 views2 pages

Project Scope Statement Template

The document provides a template for a project scope statement with guidelines for its key elements: the project purpose, goals and objectives, a scope summary and boundary conditions, and details of what is in and out of scope. The scope statement aims to concisely summarize the project scope and boundaries to help team members understand why the project is being done and what work is included.

Uploaded by

Hanseas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Project Scope Statement Template

There are many scope statement templates available, but most are really “Charter Lite” type documents;
they contain more information in them than the scope. The purpose of this template is to provide an easy
to understand summary of the project scope that can be used to help project team members understand
why the project is being done and the scope/boundaries of the project. All other details are left out and
will form part of the project charter (where they should belong).

Project Purpose

Goals & Objectives


1.
2.
3.
4.
5.
Scope Summary/Boundary Conditions

Scope Details
In Scope Out of Scope
Guidelines

 Project Purpose: A summary of the business justification for the project. This should be written
in a way that project team members without a detailed understanding of the background and
history of the project can understand and should seek to be an answer to the question, “Why is
this project being done?”
 Goals & Objectives: The key objectives that the project is aiming to deliver, ideally listed in
decreasing priority order. This should align with the business case and should contain the same
level of detail.
 Scope Summary/Boundary Conditions: This is the brief summary of the project scope that is
then expanded on in the subsequent fields. This field should be sufficient to provide an
overview of the project for individuals who simply need an overview. The concept of boundary
conditions is for scenarios where the limits of scope can be defined--date ranges, geographic
reach, offices, etc.
 Scope Details: This section provides greater details of the items that are included in scope or
that are specifically excluded from the project. This information should supplement the Scope
Summary for team members who need a greater level of information.
o In Scope: Specific items/features that will be delivered as part of the project. At the
scope statement level, this should still be fairly high level; details will be provided in
requirements documentation, but this should identify the categories of requirements
that will be developed and will establish a framework for the project work. Each
different area of work should be separated, and in order to provide a complete
summary of work to be performed on the project non-functional requirements can be
included.
o Out of Scope: This section identifies areas where there may be confusion around the
scope and explicitly excludes those areas. This should only be used if it adds value or
removes confusion from the scope--statements like “anything not defined as in scope”
do not add value.

You might also like