Scope Document Template

Introduction

The purpose of the Project Scope Statement is to provide a baseline understanding of the
scope of a project to include the project’s scope and deliverables, the work required to
complete the deliverables, and ensure a common understanding of the project’s scope
among all stakeholders. The Project Scope Statement template defines the following:

• Purpose and Justification of the Project

• Scope Description
• High Level Project Requirements
• Project Boundaries
• Project Strategy
• Project Deliverables
• Project Constraints
• Project Assumptions
• Cost Estimates

e.g., Gmail needs to be created.

Project Purpose and Justification

• It is important that project stakeholders understand the purpose and justification of a

project. Write why the project has come into existence.
• Write is it a Need or an Opportunity that the project will cater to.
• Write which stakeholders came up with the idea of this project. (Senior Management,
Middle Management, Lower Management)
• Projects are conceived to support various business goals and objectives and these must be
communicated to ensure understanding of how the project will improve business.
• This template also helps stakeholders understand the investments being made and how
this translates into better business performance.
 Goal: (put a SMART Goal)

 To have 1 million customers at end of 6 months of launch

 To occupy 10% of email market share
 Target age groups – 16 years to 28 years
 50 million emails to be sent / received in 6 months
 Initially start in US, tier 1 countries and then to other countries
 Initial offering in English
 Get 5000 corporate accounts in next 6 months

Scope Description

The Scope Description should include all known characteristics of the project’s product or
service. It is important to note that as the project moves further along in its lifecycle, this
scope description will become more defined. All details may not be known at the onset of
the project and this may be progressively elaborated as the project moves forward. This
section of the project scope statement template is key as it serves as a primary reference for
project planning and execution later in the lifecycle. This section should contain descriptions
of what is included in the product or service as well as the desired outcome of the project.

In-Scope Items

• Draw Use Case Diagram. Explain it in detail.

• Write who are the actors and the role the have in the software development.
• Draw Context Diagram. Explain data flow in and out of the system

Use Cases:
 Login to Gmail
 Change password
 Forgot password
 Compose mails
 View Inbox
 Read emails
 Delete emails
 Empty trash
 Create folders
 Create Spam option
  Create promotions options
 Send notifications
 Withdraw sent emails
 Schedule time to send emails
 Auto Delete from Trash
 Etc etc ……………………………

Out of-Scope Items

• Write in bullet points all out of Scope Items

• E.g. No captcha validation,

• Data Storage 15 GB
• One person can have only x number of accounts
• One person can send only x number of emails
• No notifications for certain emails
• No keyboard shortcuts
• No saving to google drive directly from email
• No translate to other languages
• No organize emails with sub-labels
• No bookmarking of emails
• No undo sent emails
• No switching between Gmail accounts
• No attachments greater than x size
High Level Requirements

This section should describe the capabilities to be met by successful completion of the
project. Depending on the size of the project, there may be very many or very few
requirements. However, during the creation of the scope statement, it is important to
capture, at least, the high-level requirements as many detailed requirements may not yet be
known.

e.g. Login will be one of the use cases identified by the BA. He will write high level
requirements for the login.

e.g. Login Functionality to encompass the following:

 Screen based login to be provided with user id and password screen.

 Change password functionality to be provided
 Forgot password functionality to be provided.
 Captcha functionality to be provided
 OTP to be sent to users registered mobile number for login.
 OTP to be sent to users registered email address number for login.

Change Strategy

This section of the project scope statement should describe the strategy the project team
will use in executing the project. Depending on the size and complexity of the project,
strategy can differ significantly. As the number of stakeholders, deliverables, and complexity
grow, the strategy may become more difficult to plan. Change Strategy is sometimes referred
to as the approach the team will take to complete the project.

Release Plan or Transition Plan will be mentioned.

e.g. Phase 1: of the project to cover the following functionalities.

 Login (change password, forgot password included)

 Inbox (full table structure to be created)
 Compose mails, send mails, delete mails.
  Search emails

Phase 2:

 Trash
 Create folders to put emails in respective folder.
 Add profile details, change settings
 Create starred emails

Phase 3:

 Themes
 Inbox views can be changed.
 Reading panes
 Spam

Deliverables

Project deliverables are the products or outputs that project is intended to produce.
Deliverables may also include various reports or documentation. This section should
describe the project’s deliverables which may be in general terms and not a high level of
detail. During the project lifecycle more detail can be added as it is determined.

BA will write what BA will deliver in the Project. Technical team will write what they will
deliver. Some examples of what BA will deliver:

• Scope Document
• BRD
• FRD / SRS
• Business Case (ROI Calculations)
• Vision Document
• Functional Test Cases
• Traceability Matrix
 Technical Team will deliver the following:

• High Level Design Document

• Low Level Design Document
• Unit Test Cases
• Test Plan / Test Strategy
• UAT Test Cases etc
Constraints

Project constraints are limitations that the project faces due to funding, scheduling/time,
technology, or resources. Constraints may also be physical (i.e. inadequate space or
facilities). Constraints must be carefully planned for and communicated to all stakeholders
as they may require an elevated level of urgency or flexibility to work within and successfully
complete the project. This section of the project scope statement template describes the
project’s constraints to ensure that all stakeholders understand the limitations within which
the project must be completed.

Assumptions

Project assumptions are factors affecting the project that we believe to be true but that we
have not verified to be true. It is important to document our assumptions because there is a
level of uncertainty associated with them which introduces risk to a project. This section of
the template describes the assumptions for the project so all stakeholders are aware and so
that they can be analyzed going forward in order to mitigate risk.

Cost Estimate

The project cost estimate is the foundation for budgeting for the project. It represents an
estimate of the funding which will be needed to successfully complete the project. While all
costs may not be exactly known until later in the project lifecycle, it is extremely important
to develop as accurate an estimate as possible. This section should provide a project cost
estimate with