M Reference PMOF007 Rev 1 Date Of Impl 18Oct10

m reference: pmo-f-007 rev: 1 date of impl: 18-oct-10 inistry of works pms - project scope statement

M
Reference:
PMO-F-007
Rev:
1
Date of Impl:
18-Oct-10
inistry of Works

PMS - Project Scope Statement
Project Name
ProjID
Type
(Con, BI, SM)
Project Sponsor
Classification
(A,B, C)
Project Manager
Sector / Directorate
SectorRef #
Prepared By
Name:
Directorate:
Department:
Address:
Telephone:
Email:
Template Revision History
DATE
REVISION#
SECTION
CHANGE BY
DESCRIPTION OF CHANGE
18-Oct-2010
1
Approvals
Hammad Khaliq
Pg#9 Removed “Tracking Information”
Document Review/Update Control
Date
By
Position/Role
Description of Changes/Updates/Comments
Contents
========
Project Definition 4
Project Overview: 4
Product Description: 4
Completion Criteria 5
Success Criteria 5
Project Boundaries 6
Assumptions 7
Constraints: 7
Risks: 7
Functional Organizations Involved: 8
Project Milestones 8
Attachments / Supporting Documentation 8
Approvals 10
Project Definition
------------------
Project Overview:
NOTE: The second row in each table (and in blue font) consists of help
text only (e.g. this row). These rows should be deleted from the final
document.
The Project Scope Statement is the key document required to define
exactly what the project is: What the service(s) and/or product(s) to
be developed are and how we will know when we’ve achieved those
objectives; what is in and what is out of Scope, both in terms of the
Project Boundaries and any other data required to further define and
support those boundaries. It contains many sections that interact with
each other, The Work Breakdown Structure, Boundaries, Assumptions,
etc. Therefore completing this document is an iterative process.
Plan to start this document at the same time as starting the Project
Charter. Properly defining the end point of the project will better
enable the Charter to be as complete as possible at time of signing.
This template should be used for all project Scope Statements,
regardless of whether the project is a Construction, Service &
Maintenance or BI. It should also be used for all Class A, B and C
projects but it is expected that the level of detail will be different
for each project classification.
Provide below a high level statement below as to what this project is
and why this project is needed and/or what business needs it
addresses. This information can be extracted from the Project Charter.
e.g.
This is a Roads maintenance project required in accordance with the
……objectives to provide efficient and safer roads Or
This project is to develop systems and procedures to enable the ……….
Directorate……… to be able to respond to all ……... enquiries from
………….in a timely and professional manner.
Product Description:
Specifically state the actual products and/or services that will be
delivered by this project
e.g.
A …………… facility for ……………
A report covering ……………………
A process and tool set for managing…………..
A review of …………….. for …………….
Etc.
Completion Criteria
List all the criteria that need to be achieved in order for the
project to be ‘accepted’ by the users and for the project to be
declared ‘completed’
e.g.
drainage network commissioned
System transferred to Production
User signoff obtained
etc.
1
2
3
4
Success Criteria
List all the criteria that would need to be met such that the project
could be declared a ‘success’
e.g.
Completed on budget
Completed on schedule
New Road handling traffic flow as specified
Zero accidents, etc.
1
2
3
4
Project Boundaries
As thoroughly as possible, list all the reports, presentations,
drawings, documents, configurations, services, meetings/reviews,
objectives, regulation/standards to be met etc. that will be (or not
be) part of this project
Very Important:
*
It is much easier (and makes it much clearer to the reader) to
properly establish project boundaries by having listings of both
“Inclusions” – or What’s in Scope - and “Exclusions” – or What’s
Not In Scope.
*
This section is the most critical part of this document. Use it to
validate and update all of your WBS, constraints, assumptions and
risks etc. (and vice versa) and plan to revisit it several times
while completing the rest of this document and the Project
Execution Plan (PEP)
These listings of Inclusions and Exclusions will also likely be larger
depending on the Project Classification.
e.g. (all of the following could be either an Inclusion or Exclusion
on your project):
Construction of………….,
Completing an “As Is” assessment and assembling existing documentation
for………..
Preliminary Design Report for…….
Meetings with………….in regard to ………..
etc.
In Scope (Inclusions)
*
*
Not In Scope (Exclusions)
*
*
Assumptions
Assumptions could relate to internal factors (e.g. availability of
internal resources, financial control processes, the organizational
culture, etc.) or external factors (e.g. local marketplace conditions,
the influences/authority of external regulatory bodies, etc.)
For Class A and Class B projects, include details of the impacts
likely if the assumptions prove to be false
e.g.
Internal resources available as/when required will use contract staff
(more BD)
xyz project.(which this relies on) is on schedule schedule delay
#
Assumptions:
Impact if False:
A1
A2
A3
A4
A5
Constraints:
Constraints could relate to internal factors (e.g. availability of
internal resources, financial control processes, the organizational
culture, etc.) or external factors (e.g. local marketplace conditions,
the influences/authority of external regulatory bodies, etc.)
For Class A and Class B projects, include details of who they are
imposed by and why.
e.g.
Must be completed before July Local weather conditions
Contractor selection must be tendered MoF guidelines
Must comply with new environmental laws MoE
#
Constraint:
Imposed by:
C1
C2
C3
C4
C5
Risks:
For all Project Classes, provide details of all the major Risks below
and attach the Risk Register detailing recommended risk actions. This
should include as a minimum all the Risks listed in the Charter
e.g.
There might be a shortage of materials during construction purchase
ahead of time
Users might not be available to provide requirements.
#
Risk
Recommended Action
R1
R2
R3
R4
R5
Functional Organizations Involved:
Document all the functional organizations that would be involved in,
interested in or impacted by this project and their participation
level in the project
e.g.
Planning & Design Review all contractor designs for tech. compliance
IT provides the infrastructure for storing deliverables
HR Will oversee training programs developed etc.
Organization
Participation
Project Milestones
Include below a listing showing the major milestones of the project
and any critical dependencies these have to other milestones and/or
especially to events outside the control of the project team (e.g.
getting MoF approval, another project being completed on time, etc.)
For Class A and Class B projects, a schedule should be developed and
attached using a tool such as Microsoft Project Professional (or
Primavera if this is the preferred package of project Consultants and
Contractors). This would enable the Work Packages to be further broken
down into tasks as appropriate and to also capture all the
dependencies between Work Packages and/or tasks.
For Class A projects, this schedule should also include the resource
assignments for each Package or task and these resources should be
leveled across the projects, taking into account any other commitments
outside of the projects that those resources might have
The milestone list or schedule contained in the signed version of this
document shall be the ‘Schedule Baseline’ and a copy of this baseline
schedule must be kept separately so that comparisons back to this
baseline can be made from time to time during the project as required.
#
Milestone Description
Date
Critical Dependencies
1
Project Start
2
3
4
5
Project end
Attachments / Supporting Documentation
List all documents that exist and support this Charter
e.g.
Business Case
Project Charter
Consultant Contracts
Risk Register, etc.
*Attach WBS in MSProject with this document
Approvals
---------
Project Manager’s Signature
I have prepared/reviewed this Project Scope Statement in accordance to
the Project Management System (PMS) and based on the information
provided to me in the attached documents and in consultation with the
Project Sponsor my project team and other Stakeholders.
Name
Signature
Date
Project Sponsor’s Authorization and Approval
I have reviewed and agree with the information contained in this
Project Scope Statement
Name
Signature
Date
Other Approvals
Name
Signature
Role:
Date
Name
Signature
Role:
Date
Name
Signature
Role:
Date
____________________________________________________________________________________________________________________
Department Name, Project Name Project Scope Statement Page: 10 of 10