Project Scope Statement Template - Free Download

Share:

What is Project Scope Statement?

A Project Scope Statement is written by the project manager post the project charter and outlines the project details and the outcome that is expected from the project. It helps to provide clarity on the project scope to all stakeholders.

This document provides a basic understanding of the project scope including the deliverable, assumptions and constraints and clearly lists down the high level project requirements and boundaries.


Project Scope Statement Template
Project Scope Statement Template
Thus, a project scope statement acts a formal document that defines the scope of the project which is agreed and approved by all stakeholders of the project. A well written Project scope statement is very vital for the success of a project.

As per the Project Management guidelines, every project scope statement should cover the SMART Objectives:


Specific: The objective should be clearly stated.

Measurable: List down metrics to determine if the objectives have been met.
Attainable: The team agrees that the objective is achievable and realistic.
Relevant: Objective fits into the overall organizational goal & supports the project charter.
Timely: A target date to achieve the objective is clearly stated.

Basics of Project Scope Statement Template

  • The scope statement can be used as a reference document to monitor the progress of the project and to ensure that the project is on track as per the original defined scope.
  • Hence, it is essential that a successful project scope statement should be clear and concise providing specific and exact details of the project. 
  • A scope creep may lead to project failure.
  • The scope statement serves as a formal document for the accepted project scope and should be agreed and approved by the sponsor, project team and all involved stakeholders before the commencement of the project.
Project Scope Statement
Title
Timesheet Reporting Tool
Date
June 08, 2017
Project Manager
Nicole Hansen
Project Justification
The Timesheet Reporting tool will be the creation of a user-friendly web based application. The application will automate the process of tracking the daily time entries made by employees
Project Scope Description
The timesheet reporting tool will be used as a tracking tool to review the time entries by the Information Technology employees globally
Project Objective
To create a tool to track the timesheet entries for all the Information Technology employees
High Level Requirements
·         User access for the tool granted to all employees
·         Admin access to support team
·         Report generation access to project managers
·         Enable users to remotely access the tool
·         Standard templates for all reports
In Scope
·         Multi – level approvals for timesheets
·         Timesheet tasks additions to the tool by Admin access users
·         ‘Copy Previous Week’ timesheets feature
·         Access tool via Desktop
Out of Scope
·         New project/task addition to the tool by managers
·         Connectivity with HRMS to update employee leaves automatically
·         Role based task list template
·         Access tool via mobile and tablet
Cost Estimate
Cost Item
Estimated Project Cost
Actual Spend
Cost until completion
Variance
Software
$2300
$900
$1400
NA
Hardware
$5000
$1500
$3500
+/- 1000
Other
$750
$0
$750
+/- $100
Total
$8050
$2400
$5650

Assumptions
·         Timesheets will be updated by users daily.
·         Timesheets task list will be updated once a month
Deliverables
·         Single system to record time hours for FTE and Contractors
·         Run timesheet reports to identify missing entries
·         Generate reports to identify productive tasks and work hours
·         Generate charts for steering committee packs
·         Detailed user guide on steps to update the tool for all users
Constraints
·         Unplanned leaves not captured from the leave system
·         Timesheet view access for team only to Direct managers

Key elements of a Project Scope Statement 

  • Project Justification: The project scope statement helps to define and justify why the project has been initiated and what is the purpose of the project being undertaken.
  • Project Description: It is essential to clearly specify the goals that the project aims to achieve. This field provides a brief description or summary of the project.
  • Project Objectives: Every project aims to achieve certain results or produce a certain outcome. This field defines the deliverable and outcome that the project will produce and it is necessary that the Project objectives are clearly defined for every project.
  • High Level Requirements: This field captures the high level requirements that are expected to be completed for the project objective to be fulfilled. The requirements for each project may vary depending on the size of the project. While detailed requirements may not be known at this stage, it is necessary to list down the high level ones in the scope statement.

  • In Scope: This field defines the activities that are in scope for the project. All activities that fall within the project boundaries are considered “in scope” and are planned for in the Planning phase.
  • Out of Scope: All out of scope activities are clearly outlined in this field to set clear expectations of the areas that are out of scope of the project.
  • Cost Estimate: This field captures the budget estimate that will be required for the successful completion of the project. It is essential to provide an accurate estimate to ensure all stakeholders are aware of the cost that will be incurred to undertake this project.
  • Assumptions: To define a project scope it is necessary to list down the assumptions in a project. Assumptions are made when certain events are expected to occur during the course of the project which may delay of the project timelines. These assumptions need to re-visited during the project as any false assumptions may impact the overall scope.
  • Deliverables: This field lists down the results or output expected to be produced by the project. The deliverable from the project should support the project objectives.
  • Constraints: All the constraints or limitations in terms of time, resources, and functionalities need to be listed here.

No comments