PROJECT SCOPE STATEMENT PURPOSE: Generally describes the project’s deliverables and the work required to create those deliverables. The project scope statement provides a common understanding of the project scope among all project stakeholders and describes the project’s major objectives. It also 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. Project ID NNNNNN-NN Date MM/DD/YY Project Name Prepared By: Project Objectives Project objectives include the measurable success criteria of the project, e.g., “SMART.” Projects may have a wide variety of business, cost, schedule, technical, and quality objectives. Project objectives can also include cost, schedule, and quality targets. Each project objective has attributes such as cost, volume, etc., a metric, and an absolute or relative value. Product Scope Definition Describes the characteristics of the product, service, or result that the project was undertaken to create. These characteristics will generally have less detail in early phases and more detail in later phases as they are progressively elaborated. While the form and substance of the characteristics will vary, the scope description should always provide sufficient detail to provide later project scope planning. Build off the high level scope statement as provided in the Project Charter. Project Requirements Describes the conditions or capabilities that must be met or possessed by the deliverables of the project to satisfy a contract, standard, specification or other formally imposed document. Analyses of all stakeholder needs, wants, and expectations are translated into prioritized requirements. · Requirement #1 · Requirement #2 … Resource Requirements Describes the resource requirements, and whether resources will be acquired internally, externally, or a combination thereof. Project Boundaries (Inclusions and Exclusions) Identifies generally what is included within the project. It also states explicitly what is excluded from the project, if a stakeholder might assume that a particular product, service, or result could be a component of the project. Critical Success Factors Document the factors that will ensure the success or failure of the project. Project Deliverables Deliverables include both the outputs that comprise the product or service of the project, as well as ancillary results, such as project management reports and documentation. They describe what the clients will get when the project is completed. Product Acceptance Criteria Defines the process and criteria for accepting completed products. Project Constraints List and describe the specific project constraints associated with the project scope that limit the team’s options. For example, a predefined budget or any imposed dates that are issued by the cu.

1. PROJECT SCOPE STATEMENT
PURPOSE: Generally describes the project’s deliverables and
the work required to create those deliverables. The project
scope statement provides a common understanding of the
project scope among all project stakeholders and describes the
project’s major objectives. It also 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.
Project ID
NNNNNN-NN
Date
MM/DD/YY
Project Name
Prepared By:
Project Objectives
Project objectives include the measurable success criteria of the
project, e.g., “SMART.” Projects may have a wide variety of
business, cost, schedule, technical, and quality objectives.
Project objectives can also include cost, schedule, and quality
targets. Each project objective has attributes such as cost,
volume, etc., a metric, and an absolute or relative value.
Product Scope Definition
Describes the characteristics of the product, service, or result
that the project was undertaken to create. These characteristics
will generally have less detail in early phases and more detail in
later phases as they are progressively elaborated. While the
form and substance of the characteristics will vary, the scope

2. description should always provide sufficient detail to provide
later project scope planning. Build off the high level scope
statement as provided in the Project Charter.
Project Requirements
Describes the conditions or capabilities that must be met or
possessed by the deliverables of the project to satisfy a
contract, standard, specification or other formally imposed
document. Analyses of all stakeholder needs, wants, and
expectations are translated into prioritized requirements.
· Requirement #1
· Requirement #2 …
Resource Requirements
Describes the resource requirements, and whether resources will
be acquired internally, externally, or a combination thereof.
Project Boundaries (Inclusions and Exclusions)
Identifies generally what is included within the project. It also
states explicitly what is excluded from the project, if a
stakeholder might assume that a particular product, service, or
result could be a component of the project.
Critical Success Factors
Document the factors that will ensure the success or failure of
the project.
Project Deliverables
Deliverables include both the outputs that comprise the product
or service of the project, as well as ancillary results, such as
project management reports and documentation. They describe
what the clients will get when the project is completed.
Product Acceptance Criteria
Defines the process and criteria for accepting completed
products.
Project Constraints
List and describe the specific project constraints associated with
the project scope that limit the team’s options. For example, a
predefined budget or any imposed dates that are issued by the
customer.

3. Project Assumptions
Lists and describes the specific project assumptions associated
with the project scope and the potential impact of those
assumptions if they prove to be false.
Initial Project Organization
The members of the project team, as well as stakeholders, are
identified. The organization of the project is also documented.
Change Management
Document the detailed change control procedures and how they
will be monitored and controlled.
Issue Management
Document how issues will be documented, prioritized, resolved,
communicated, and monitored & controlled.
Risk Management
Document how risks will be documented, prioritized, mitigated,
and communicated. Also list 2 or 3 project-specific risks and
how they will be mitigated, should they occur.
Schedule Milestones
The customer, Project Sponsor, or performing organization can
identify milestones and can place imposed dates on those
schedule milestones. These dates can be addressed as schedule
constraints. List the key milestones along with their due dates.
Fund Limitation
Document the funding and describe any limitation placed upon
funding for the project, whether in total value or over specified
timeframes.
Project Stakeholders
List each of the key stakeholders, by role.
Approval Requirements
Identifies approval requirements that can be applied items such
as project objectives, deliverables, documents, and work. List
any standards, regulations, &/or performance requirements that
must be met.
Scope Statement Approval Form/Signatures

4. I have reviewed the information contained in this Scope
Statement and agree.
Name
Signature
Date
The signatures of the people above relay an understanding in
the purpose and content of this document by those signing it. By
signing this document you agree to this as the formal Project
Scope Statement.
REMINDER: Delete all instructions, including this line.

5. Project Charter
V 2.0
Project Charter
Delete this line and all instructions/examples prior to
submission
Project Name
Project Number
Project Manager
Prioritization
Owner(s)
Start Date:
Scheduled Completion Date:

6. Mission/ Purpose
What is your project going to accomplish? How does this
project relate to overall goals and objectives of the company? It
is part of a program or larger project?
SOW
What will this project create? What is the product of the
project? At a high level, how do you plan on doing the work of
the project? What are the high-level deliverables for this
project?
Project Purpose / Business Justification: Describe the business
need or opportunity this project addresses. Be sure to include
what is within scope and outside of scope, e.g., what is and is
not included.
Objectives
What objectives, if any, of the company is this project designed
to meet?
(in business terms) Describe the measurable outcomes of the
project, e.g., reduce cost by $xxxx or increase quality to yyyy
and use a SMART objective statement. (Include time and cost,
e.g., we will do xxx, by mm/dd/yyyy, at a cost not to exceed
$xxxx.) Each objective must relate to at least one strategic
initiative or business objective.
Business Need
Why should we do this prj? What will be gained, changed, or
modified? Is there a financial or business reason to do this
project? This area should contain any feasibility studies, NPV,
PI, PB, or PBD used to advance the prj. (List known
alternatives if you do not do the prj & pros & cons of each)
Project Manager and Stakeholders

7. Who will lead this project? Who are the major stakeholders?
Stakeholders: (e.g., those with a significant interest in or who
will be significantly affected by this project. Include
stakeholders’ names, project role, responsibilities, and contact
information)
Milestones
(include start & end dates & list of high-level deliverables)
What are the key milestone dates associated with the project?
Propose start and end dates for Project Phases (e.g., Inception,
Planning, Construction, Delivery) and other major milestones.
Also include a visual timeline for the project milestones. This
list of deliverables is high level, project management related,
such as Project Plan Completed, Requirements Approved, etc.)
Budget
What is the order-of-magnitude budget for this project?
(Provide the approved budget and summarize the spending by
phase. Also include whether or not services will be required
from external vendors)
User Acceptance Criteria/Quality
What are the minimum success criteria as defined by the key
stakeholders?
High-Level Project Assumptions
What are the assumptions on which the project is based?
(conditions that may limit the team’s options w/respect to
scope, technology, schedule, &/or expectations…predetermined
budget, end date, resources etc.)
High-Level Project ConstraintsWhat are the major limiting
factors that affect the project?
Exclusions / Boundaries
What are the boundaries of the project? What is to be included
and what is to be excluded from the project?
Major Risks

8. What are the major risks affecting the project? Identify
obstacles that may cause the project to fail (Include the risk of
doing and not doing a project )
Risk
Risk Rating (Hi, Med, Lo)
Risk Owner & High-Level Mitigation Plan
KEY STAKEHOLDERS
Project Manager Authority Level
Project Core Team
Subject Matter Experts (SMEs)
(e.g., those with a significant interest in or who will be
significantly affected by this project. Include stakeholders’
names, project role, responsibilities, and contact information)
APPROVALSType NameSignatureDate
Executive Sponsor Approval:

9. Customer/ Department Sponsor Approval:
Project Manager Approval: