The partner or customer logo can be inserted if required in the right-hand header cell.

This must be done individually for each section.

The project name can be changed under File Properties. It will then be updated
throughout the document.

"input project title here":

Project Scope Statement

project logo

Page 1 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

Project: "input project title here"

Title: Project Scope Statement
Document number:
Version 0.1
Document status: Draft
Author:
Responsible:
Date created: 29.03.2016
Protection class: "For internal use only"

The Project and Author fields are filled automatically with the data from the document properties (File
 Properties). Once the appropriate entries have been made here, these fields can be updated with
the "Update Field" function (can be found in the context menu for the individual fields).
Possible states for the document status include "Draft,” "Released" and "Final." The status of the
current document should be specified respectively in the field above.

Document history

Version Date Author Comment / Change

0.1 29. Mar. 2016 Draft

The document history should provide an overview of the development of the document. Different versions with
their date, author and possible comments should be entered here.

Tips for using this template:

The blue text contained in the template should provide assistance for usage. It briefly describes how the
individual elements and styles are to be understood.
Please delete all of the blue text before you disseminate or print the document; it is intended exclusively for
internal use.
The Project Scope Statement fine-tunes the requirements defined in the project order/charter. Contents already
listed in the project order/charter should be taken over. The project order/charter described can be used as a
template.
The Project Scope Statement is signed at the end of the project conception phase by an approved signatory
member of the steering committee, the customer and project manager.

Page 2 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

Contents

Page
1 Background..................................................................................................................... 5
2 Goals and project closing criteria.................................................................................6
2.1 Delivery units and services....................................................................................................... 6
2.2 Scheduling goals / Milestones.................................................................................................. 6
2.3 Project budget.......................................................................................................................... 7
3 Scope............................................................................................................................... 8
3.1 Scope of business processes................................................................................................... 8
3.2 Scope of organization............................................................................................................... 9
3.3 Scope of sites........................................................................................................................... 9
3.4 Scope of resources.................................................................................................................. 9
3.5 Scope of data........................................................................................................................... 9
3.6 Scope of technologies............................................................................................................ 10
3.7 Scope of customers / suppliers.............................................................................................. 10
4 Assumptions, constraints and external dependencies.............................................11
5 Responsibility of the customer....................................................................................12
5.1 Jobs and tasks....................................................................................................................... 12
5.2 Resources and staffing........................................................................................................... 12
6 Critical success factors................................................................................................13
7 Risks.............................................................................................................................. 14
8 Valid change requests towards project scope...........................................................15
Annex................................................................................................................................... 16
A. Glossary and abbreviations.................................................................................................... 16
B. References, accompanying documents..................................................................................17

The table of contents does not have to be created again. To accept the changes made, simply select the "Update
Field" option from the context menu. If hew headings have been inserted since the last update or if the structure
has changed in some other way, it is recommended to select the "Update entire table" option. Otherwise, you
could simply select "Update page numbers only." Up to Level 3 headings can be listed in the table of contents.

The styles should be used to structure the document. These allow simple and consistent formatting of the
documents used in the specific project, but also across all projects.
The “Heading 1 noIndex” style is formatted in exactly the same way as the "Heading 1" style, but is not taken
into account in the table of contents. (See document history)
The "Heading 1 noNumber” headings do not have a structure number, but do appear in the table of contents.
(See Annex)
The "Heading 1 Annex” style is provided for formatting the individual sections in the annex. The individual
headings are structured with uppercase letters instead of numbers in this case. The "Heading 2 Annex” style is
provided additionally for further subsections in the annex.

Page 3 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

Standard text should be formatted with the "Text" style in order to avoid problems when changing the standard
style.
The following chapters and sections frequently contain tables, which are suitable for providing a clear overview.
If the points being described are very extensive however, a table listing can also be omitted.

The project scope statement is the description of the project scope, major deliverables, assumptions, and
constraints. The project scope statement documents the entire scope, including project and product scope. It
describes, in detail, the project’s deliverables and the work required to create those deliverables. 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.

Page 4 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

1 Background
This section describes the customer's company in relation to the project. It clarifies why the project
was initiated, its significance for the customer's company, specific or long-term goals that the company
wants to achieve and the contribution made by the project to the customer's overall strategy.

The significance, goals and strategy of company can be cited at this point however, because the project order is
an internal document.
The background description out of the project charter could be used at starting point here, but should be
described in more detail may be.

Page 5 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

2 Goals and project closing criteria

This section briefly describes which goals are to be realized with the project. Apart from the factual
goals, these include scheduling goals and the financial framework within which the project is to be
executed. The individual goals are used primarily as a measure of the success of the project upon its
completion. The goals therefore have to be depicted in a measurable way so that it can later be
established to what extent the goals were realized and hence the project was successful.
Again the related chapter out of the project charter could be copied and paste here, but has to be developed and
described in as much detail as possible.

2.1 Delivery units and services

This section lists all delivery units, elements or services that are to be provided by company as part of
the project.
This chapter can be subdivided further in the case of more comprehensive or complex projects.

Delivery unit Description/Comment

A deliverable is 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 tangible
components completed to meet the project objectives and can include elements 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.

2.2 Scheduling goals/Milestones

The dates defined for the project history are documented here.

Schedule date/ Description/Comment

Milestone

Page 6 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

2.3 Project budget

The financial framework within which the project has to operate is described here. Depending on the
size of the framework, it may make sense to provide further details for individual parts.

Area Amount

Project

Subproject

Page 7 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

3 Scope
This section describes the boundaries of the project. It should be clarified which aspects belong to the
project and may be changed in the framework of the project and which aspects should remain
unchanged. This could include, for example, customers, suppliers, products, processes, organizations,
data, volumes, technologies or resources.
The sections listed below should help elaborate an overview of which aspects will be considered in the
course of further proceedings and which will be ignored. In addition, the responsible persons or
contacts for the points can of course also be added.
The points listed here should be taken as a suggestion. They can be supplemented or also removed as required in
actual projects.
The preparation of a detailed project scope statement is critical to project success and builds upon the major
deliverables, assumptions, and constraints that are documented during project initiation. During project
planning, the project scope is defined and described with greater specificity as more information about the
project is known. Existing risks, assumptions, and constraints are analyzed for completeness and added or
updated as necessary. The Define Scope process can be highly iterative. In iterative life cycle projects, a high-
level vision will be developed for the overall project, but the detailed scope is determined one iteration at a time
and the detailed planning for the next iteration is carried out as work progresses on the current project scope
and deliverables.
Project exclusion: Generally identifies what is excluded from the project. Explicitly stating what is out of scope
for the project helps to manage stakeholders’ expectations.

3.1 Scope of business processes

The "business process" domain describes which activity the company will pursue, how it will pursue
this activity, which sequence it will observe, which rules it will follow and what type of results can be
achieved. Changes in the "business process" domain determine the changes in all other domains.

Processes considered Processes excluded

3.2 Scope of organization

The "Organization" domain refers to the employees of the company, their culture, their skills, their
roles, their team structures and their organizational units. In addition, these domains refer to the
support systems that enable organizational change.

Organizational units considered Organizational units excluded

Page 8 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

3.3 Scope of sites

This section defines which sites are to be affected by this project in terms of the site types and also the
special, physical facilities at a particular site.

Sites considered Sites excluded

3.4 Scope of resources

This section defines which resources used in the organization are to be considered. This could
include, for example, machines, information systems or applications.

Resources considered Resources excluded

3.5 Scope of data

This section describes which data is to be considered in the project.

Data considered Data excluded

3.6 Scope of technologies

The technologies to be considered are defined here.

Technologies considered Technologies excluded

Page 9 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

3.7 Scope of customers/suppliers

This section defines which customers or suppliers from the customer area are to be considered in the
project.

Customers/suppliers considered Customers/suppliers excluded

Page 10 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

4 Assumptions, constraints and external dependencies

Assumptions are expectations that form the basis for decisions. This section lists the main
assumptions on the basis of which appraisals, plans and methods are defined for the project.
Assumptions should also cover all known open points, if the project is also to be continued even
though certain questions have not yet been clarified. The description of the individual assumptions
should always indicate how critical the respective point is. Fulfilling a responsibility on the part of the
customer should not be listed as an assumption.
A constraint is a restriction that applies in conjunction with the project. Constraints can relate to
methods, priorities, human resources, times, technologies, environments, decision cycles, tools and
techniques or to other aspects of the project. Identification of constraints acts as a stimulus for
management for managing these constraints and thereby ensuring the success of the project.

A R E Item

A = Assumption R = Constraint E = External dependency

• Constraints. A limiting factor that affects the execution of a project or process. Constraints identified with the
project scope statement list and describe the specific internal or external restrictions or limitations associated
with the project scope that affect the execution of the project, for example, a predefined budget or any imposed
dates or schedule milestones that are issued by the customer or performing organization. When a project is
performed under an agreement, contractual provisions will generally be constraints. Information on constraints
may be listed in the project scope statement or in a separate log.
• Assumptions. A factor in the planning process that is considered to be true, real, or certain, without proof or
demonstration. Also describes the potential impact of those factors if they prove to be false. Project teams
frequently identify, document, and validate assumptions as part of their planning process. Information on
assumptions may be listed in the project scope statement or in a separate log.

Page 11 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

5 Responsibility of the customer

This section lists what the customer is to contribute in the course of the project. These responsibilities
can be split into two categories.

5.1 Jobs and tasks

Task Comment Contact

5.2 Resources and staffing

Resources/Staffing Comment Contact

Page 12 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

6 Critical success factors

This section outlines which factors are essential for the project to succeed. Project risks frequently
arise in the absence of these factors.

Critical Description /Comment

success factor

Page 13 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

7 Risks
This section describes some of the key project risks and their potential impact on the success of the
project. This list of risks should be regarded as provisional rather than complete because risks are
identified and have to be dealt with continuously during the course of the project. Risks can relate to
operating principles, conflicts of interest or priority, choosing between alternatives, the use of
resources or unfulfilled responsibilities.
Use the list of High Level Risks out of the project charter as a starting point here and develop the list
based on the knowledge gained during conducting this scope statement.

Risk Possible impacts on the project

Page 14 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

8 Valid change requests towards project scope

The following change requests were accepted in the course of the project and therefore belong to the
scope of the project.

No. Date Change Responsible

Page 15 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

Annex
I. Glossary and abbreviations
If abbreviations have been used in this document as well as terms that need to be defined in greater detail,
whose common understanding for every user is a prerequisite for the success of the project, this is an
opportunity to do this.

Term Explanation

Page 16 of 17
 Customer Company
logo here "input project title here": Project Scope Statement logo here

II. References, accompanying documents

If reference has been made in this document to other, external documents, these documents should
be listed here.

Reference Title Doc. no.

no.

Page 17 of 17