Page 1 of 5

Project Scope Statement1

 All documents referenced which appear in this document are an integral part
 Completing sections of this document made by possible links to external documents, and in
case of their absence - a text description
 In case of any discrepancies of this document with the project charter - this document is
considered more authoritative
 Works which are not contained in this document - are not included in the project

Project name

Project manager

Date (YYYY/MM/DD)

Versions (add rows, if necessary)

Date
Version Author Comments
(YYYY/MM/DD)

0.1

1
Based on Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK)® fifth
edition and Ivan Selikhovkin’s materials (http://pmlead.ru/)
Version: 0.0 Project Code: Code
Project Scope Statement
Status: Draft Author:
Project name
Date: YYMMDD Owner:
 Page 2 of 5

TABLE OF CONTENTS
Table of contents....................................................................................................................................... 2
1. General information............................................................................................................................ 3
1.1. General information on the project..............................................................................................3
1.2. Project constrains........................................................................................................................ 3
1.3. Project tolerances....................................................................................................................... 3
2. Project description.............................................................................................................................. 3
2.1. Project description....................................................................................................................... 3
2.2. Analogs of the product................................................................................................................ 3
2.3. Links to product specifications....................................................................................................3
2.3.1. Business-level requirements................................................................................................3
2.3.2. System-level requirements...................................................................................................3
2.3.3. Technical-level requirements...............................................................................................3
2.4. Project deliveries......................................................................................................................... 4
3. Project management approach.......................................................................................................... 4
3.1. Used elements of the implementation plan..................................................................................4
3.2. Does it require additional conciliation of plan elements?.............................................................5
4. Conciliation signatures....................................................................................................................... 5

Version: 0.0 Project Code: Code

Project Scope Statement
Status: Draft Author:
Project name
Date: YYMMDD Owner:
 Page 3 of 5

1. GENERAL INFORMATION
1.1. General information on the project
< Additional information to that contained in Section 1 of the charter: open - the essence of the project,
the business environment and goals. Any explanations. If no such information - a link to the charter >

1.2. Project constrains

< Specify constraints of the project, or a link to the Charter in case of their equal identity >

1.3. Project tolerances

< List all known assumptions of the project. For example: until the beginning of the implementation on
the project may not require the work of analysts from the Implementation Department; or, until the end
of the project the cost of licensed components must not be changed >

2. PROJECT DESCRIPTION
2.1. Project description
< Description of product requirements, including deployed purposes of its creation and implementation
requirements >

2.2. Analogs of the product

< Link to product analogs, if any exists >

2.3. Links to product specifications

2.3.1. Business-level requirements
< Requirements are IT-independent. Example - business objects and their attributes. In the presence
of certain documents - not to rewrite requirements, give a link to the document >

2.3.2. System-level requirements

< Requirements are IT-dependent, but platform-independent. Example - entities and their attributes. In
the presence of certain documents - not to rewrite requirements, give a link to the document >

2.3.3. Technical-level requirements

< Requirements are IT-dependent and platform-dependent. Example - database table field (as a
projection of the entities on the technical level). In the presence of certain documents - not to rewrite
requirements, give a link to the document >

2.4. Project deliveries

Delivery result Acceptance criteria

Version: 0.0 Project Code: Code

Project Scope Statement
Status: Draft Author:
Project name
Date: YYMMDD Owner:
 Page 4 of 5

< Result 1 >  < Acceptance criteria 1 >

 < Acceptance criteria 1 >
 < Acceptance criteria 1 >

< Result …n >  < Acceptance criteria n >

 < Acceptance criteria n >
 < Acceptance criteria n >

3. PROJECT MANAGEMENT APPROACH

3.1. Used elements of the implementation plan

Project delivery plan < Delivery Plan - forecast performance / delivery of a product (milestones
- to discuss the content, timing, budget, with the sponsor and owner of
the project) with an indication of possible deviations in percent (or give a
link) >

Human resource < Is there a rule of appointment and allocation of resources for the project
management plan (describe)? >
< Links to the conciliated list of project resources >

Project communications < Are there rules of communication on the project (describe)? >
< Link to the Stakeholder register >

Risk management plan < Are there any rules for dealing with risks (describe)? >
< Link to the risk register >

Procurement < The list of purchases of the project (or link )>
management plan < Does the organization rules of procurement exist and who is
responsible for the process? (describe or link) >
< Does the project procurement plans exist (describe or link) >

Configuration < What are the rules of the configurations on the project, including the
management maintenance of the code versioning, distribution, project plans (describe /
give the link)? >

The minutes of the < The list of meeting results (or link) >
meeting

Change request < What are the rules for changes in project plans and documentation
management (describe / give the link)? >

<Expand, if necessary> < Expand, if necessary >

Version: 0.0 Project Code: Code

Project Scope Statement
Status: Draft Author:
Project name
Date: YYMMDD Owner:
 Page 5 of 5

3.2. Does it require additional conciliation of plan elements?

What does require the conciliation? Who approves?

Risk management plan Project sponsor, Customer

Project plan Customer

< Example - documents: a risk management plan, WBS, < For example – Project Sponsor, three key
budget… > stakeholders (specify)… >

<…> <…>

4. CONCILIATION SIGNATURES
APPROVED

Name Position Signature Date

Signature indicates agreement signed with all the provisions of this document.

Version: 0.0 Project Code: Code

Project Scope Statement
Status: Draft Author:
Project name
Date: YYMMDD Owner: