This document outlines the scope of a project to <Meaningful Title for Project>. It describes the background and need for the project, objectives, deliverables, resources, budget, and approval process. The key stakeholders are identified as the project manager, technical lead, client, and sponsor. The project will <Describe the product or service that this project will produce> to address a specific business need. Upon completion, the deliverables will be tested and signed off by the client before closing the project.

1. PROJECT SCOPE STATEMENT
Note: Save document as ProjectScope_<Title of Project>. If there are sections that do not pertain to your project, please indicate by typing ‘NA’. Do not
delete the section.
Project Work ID <Remedy ID>
Project Title: <Meaningful Title for Project>
Prepared by: <Name of Project Manager>
Date of Document: <MM/DD/YYYY>
Version History
Version Date Author Comments
1.0 Initial release
2.0
1. BACKGROUND
1.1. Request Information
Submitted by: <Name of person that submitted the initial request>
Request Date: <Original Remedy Request Name>
Description: <Original Remedy Description>
1.2. Business Need/Opportunity
<The statement of need/opportunity should explain, in business terms, how the proposed project will address specific needs or opportunities.
Typically, satisfaction of a need or opportunity will provide specific benefit to the organization. May want to also include Strategic Direction
Cornerstone, Client Priority List, etc.>
1.3. Product Description
<Describe the product or service that this project will produce (e.g., “This project will manage relocation to a new headquarters location for
ABC Corporation)>
1.4. Key Project Stake Holders
Project Manager: <The Project Manager is the individual from ITS Department who will coordinate the Project Team and see that
the project stays on track. The Project Manager may also be either the Business Lead or the Technical Lead.>
Technical Lead: <The Technical Lead is the individual from the IT Department with the technical expertise to ensure a successful
project >
Client: <Subject Matter Expert who understands the business processes underlying this project and who represents business interests>
Sponsor: <Who is the primary proponent of this project>
Performing Organization: <Name of organization responsible for project>
2. PROJECT DESCRIPTION
2.1. Objectives
2.1.1. Business Objectives<Define the results that must be achieved for a proposed solution to effectively respond to the
need/opportunity, i.e. the business objectives are the immediate reason for investing in the project. Objectives also serve as the “success
factors” against which the organization can measure how well the proposed solution addresses the business need or opportunity>
10/1/2014 PAGE 1 OF 5 Project Scope Statement
Template Version 2.2

2. PROJECT SCOPE STATEMENT
2.1.1.1.
2.1.2. Project Objective <Are the specific goals of the project. Project objectives, if properly defined and met, will lead directly
to accomplishment of the Business Objectives. While Business Objectives relate to the goals and objectives of the organization, Project
Objectives relate specifically to the immediate goals of the project. For example, the project goal “implement a new time tracking
system” has no value in and of itself. That goal only brings value to the organization when it leads to accomplishment of the Business
objective (e.g. “Reduce costs and improve productivity through improved resource management”
2.1.2.1.
2.2. Project Scope
2.2.1. High Level Requirements/Deliverables<List the high-level project sub-products whose satisfactory
delivery mark completion of the project
2.2.1.1.
2.2.1.2.
2.2.2. Out of Scope
2.2.2.1. Any work not specifically defined in the scope of this document will be
considered as “work or activities out of scope and can only be included via the
change control process
2.2.2.2.
2.3. Project Completion Criteria<Task as determined by Client and PMO that indicates that the project can be closed.
Depending on size of project this may be the same as Deliverables>
2.3.1. Completion of all deliverables
2.3.2. User Acceptance Testing and Signoff of all deliverables
2.4. External Dependencies <Will project success depend on coordination of efforts between the project team and one or more
other individuals or groups? Has everyone involved agreed to this interaction? Ex. Special Authority, Committee Approval, etc.
2.4.1. Change Advisory Board
2.4.2.
2.5. Assumptions <List Assumptions from the basis for project planning (e.g., support and attention will be provided by the Sponsor;
Resources will be available to adequately staff the project, etc.). Assumptions are a source of project risk and must be identified.>
2.5.1.Client resources will be available during the time allocated on WBS
2.5.2.
2.6. Constraints <List any conditions that may limit the project team’s options with respect to resources, personnel, or schedule
2.6.1.Client and IT resources assigned to this project have also been allocated to other
institutional and divisional projects in addition to daily operational support
3. PROJECT MILESTONES Client and IT resources assigned to this project have also been
allocated to other institutional and divisional projects in addition to daily operational support
Note: Constraint dates are based on original project estimates as well as IT and Client resource availability. Any change in either of these
will result in a change to the project completion date
Milestone Date Constraint Comments
Project Start
10/1/2014 PAGE 2 OF 5 Project Scope Statement
Template Version 2.2

3. PROJECT SCOPE STATEMENT
Project Finish
4. PROJECT OVERVIEW
4.1. Project Approach <High-Level task and any other known technical details>
4.1.1. 1st
4.2. Communication Plan
4.2.1. Project Meetings<Include Attendees, Frequency, Format>
4.2.1.1. Project Kickoff Meeting
4.2.1.2. Project Status Meetings
4.2.2. Status Reporting <Include Distribution List, Frequency, Format>
4.3. Resources The following individuals and organizations will be actively involved in the project or
have a stake in the project outcome:<Include Internal and External Resources>
Name Organization Role
4.4. Known Risks or Issues < Identify any and all risk that will have a negative or positive impact on the project>
4.4.1. Security Risk Assessment (Y/N)
4.4.2. Contract or Click Wrap Issue (Y/N)
4.5. New service, or change to existing service that will require a new or updated Service
Level Agreement (Y/N)
5. QUALITY PLAN
<Include how system, application, process, etc will be tested and verified for acceptance signoff and production usage
10/1/2014 PAGE 3 OF 5 Project Scope Statement
Template Version 2.2

4. PROJECT SCOPE STATEMENT
6. PROJECT BUDGET
<Include skill set and cost estimates for any major expenditures such as Equipment, Outside Consultation, etc.
Note: As requirements are further defined, estimates may be re-evaluated and updated as needed
6.1 IT Resource/Skill Type Estimated Hours1,2
Resource Estimate in hrs
[See footnote below for projects with DBA
resources]
6.2 Estimated cost of Software/Hardware/Services/Other
6.3 Estimation of ongoing Service and Support
Freq
(Annual/5years
/monthly)
Cost
Skill Set (list specific skill sets)
·
Maintenance/Licensing
(SSL Certificate, etc)
Infrastructure
Network
Server refresh
VM Server
Other
1 Customization or Simple Upgrade - If a project is for a MIS customization of an existing service such as Banner
or a simple upgrade of a single existing component such as Banner Financial Aid upgrade, then the hour
estimates for DBA work is 10 hours. The DBA role is limited to operational task of fulfilling production control
requests and time estimates are not required - simply use a placeholder of 10 hours. These will be DBA
Architect Hours.
2 New Service, New Software, New Implementation - If a project is to implement a new service with new
software that requires a new database or an extensive upgrade of multiple Banner modules then the DBA group
needs to review the project to provide time estimates. In these cases, chances are that it involves Systems and
Networks time as well.
10/1/2014 PAGE 4 OF 5 Project Scope Statement
Template Version 2.2

5. PROJECT SCOPE STATEMENT
7. PROJECT CHANGE MANAGEMENT
<List the different approvals for your project. Such as Scope Changes, Production Downtime, Budget,etc.>
8. PROJECT SCOPE STATEMENT APPROVAL
The purpose of this document is to provide a vehicle for documenting the initial planning efforts for
the project. This scope statement is used to reach a satisfactory level of mutual agreement among the
project manager, sponsor, and client with respect to the objectives and scope of the project before
significant resources are committed and expenses incurred
The signatures below certify that the Project Manager has met with and reviewed this Project Scope
Statement with the individuals below and the information contained herein are accurate
Name Role Signature Date
10/1/2014 PAGE 5 OF 5 Project Scope Statement
Template Version 2.2

6. PROJECT SCOPE STATEMENT
7. PROJECT CHANGE MANAGEMENT
<List the different approvals for your project. Such as Scope Changes, Production Downtime, Budget,etc.>
8. PROJECT SCOPE STATEMENT APPROVAL
The purpose of this document is to provide a vehicle for documenting the initial planning efforts for
the project. This scope statement is used to reach a satisfactory level of mutual agreement among the
project manager, sponsor, and client with respect to the objectives and scope of the project before
significant resources are committed and expenses incurred
The signatures below certify that the Project Manager has met with and reviewed this Project Scope
Statement with the individuals below and the information contained herein are accurate
Name Role Signature Date
10/1/2014 PAGE 5 OF 5 Project Scope Statement
Template Version 2.2