PROJECT SCOPE MANAGEMENT PLAN TEMPLATE
Project title / Code / Date / File nameProject Sponsor / Project Manager / Project client
Prepared by
Document owner(s) / Project/organisation roleProject charter version control
Version / Date / Author / Change description[Replace this text with the name of the document owner.] / Document created
[Replace this text with the name of the change owner.] / [Replace this text with a list of changes for this owner on this date and version.]
- [Change 1]
- [Change 2]
- [Change n]
TABLE OF CONTENTS
1SCOPE MANAGEMENT PLAN PURPOSE
2PROJECT OVERVIEW
3PROJECT SCOPE STATEMENT
3.1Goals and objectives
3.2Organisational impacts
3.3Project deliverables
3.4Deliverables Out of Scope
3.5Project Estimated Costs and Duration
4PROJECT CONDITIONS
4.1Project assumptions
4.2High-level project risks
4.3Project constraints
5Creating the work breakdown structure (WBS)
6Verifying completion of project deliverables
7Managing requests for changes to project scope
8APPROVALS
1PROBLEM/ BACKGROUND
[Replace this text with your own statement of the scope management plan purpose.]
2SCOPE MANAGEMENT PLAN PURPOSE
[Replace this text with your own statement of the scope management plan purpose.]
3PROJECT OVERVIEW
[Replace this text with the rationale and business justification for undertaking this project.]
4PROJECT SCOPE STATEMENT
4.1Goals and Outcomes
Goals / Outcomes[Replace this text with project goals. For example: The project will provide an improved system for managing product returns.] / [Replace this text with outcomes for each goal. For example:
- Develop a system by June that tracks an end-to-end process for 100% of product returns.
- Integrate new system with Sales in order to improve customer satisfaction 40% by year end.]
4.2Organisational Impacts
[Impacts to organisations business activities, capability and or processes.]
1.2.
3.
4.
5.
4.3Organisational benefits
[Benefits that will be measured throughout and or after the project.]
1.2.
3.
4.
5.
4.4Project deliverables
Milestone / Deliverable- [Milestone description]
- [Deliverable 1—description]
- [Deliverable 2—description]
- [Deliverable 3—description]
- [Milestone description]
- [Deliverable 1—description]
- [Deliverable 2—description]
- [Deliverable 3—description]
- [Milestone description]
- [Deliverable 1—description]
- [Deliverable 2—description]
- [Deliverable 3—description]
4.5Exclusions
[Replace this text with a description of key logical areas not considered part of the boundaries of this project. Examples of these out-of-scope deliverables may include data, processes, tasks, applications, or business management.]
4.6Project estimated duration
Project milestone / Date estimate / Deliverable(s) included / Confidence level[Milestone 1] / [mm/dd/yy] / [Deliverable 1]
[Deliverable 2] / [High/Medium/Low]
[Milestone 2] / [mm/dd/yy] / [Deliverable 1]
[Deliverable 2] / [High/Medium/Low]
4.7Project estimated cost
Project critical tasks / Cost estimate / Indicative budget[Critical task/ deliverable 1] / [$] / [Information supporting the budget]
[Critical task/ deliverable 2] / [$] / [Information supporting the budget]
Total estimated cost
5PROJECT CONDITIONS
5.1Project assumptions
- [Assumption 1]
- [Assumption 2]
- [Assumption 3]
5.2High-level project risks
# / Risk area / Likelihood / Risk owner / Project impact-mitigation plan1 / [Project risk] / [High/
Medium/
Low] / [Replace this text with a description of the mitigation plan.]
2 / [Project risk] / [High/
Medium/
Low] / [Replace this text with a description of the mitigation plan.]
5.3Project constraints
- Time – [Replace this text with a description of the details for each key constraint.]
- Costs – [Replace this text with a description of the details for each key constraint.]
- Specifications – [Replace this text with a description of the details for each key constraint.]
- Resources – [Replace this text with a description of the details for each key constraint.]
6Creating the work breakdown structure (WBS)
[Replace this text with a description of how the work of the project will be structured and what approach will be used to identify work packages/activities and tasks.
[Attach the WBS for this project as an appendix]
7Verifying completion of project deliverables
[Replace this text with a description of how the project deliverables will be verified as complete. Please include roles and responsibilities for verifying completion of project deliverables.]
8Managing requests for changes to project scope
All change requests, approvals and actions must be completed in accordance with the GSE procedure as stated in the Change Management Plan Template located on the GSE Intranet.
9APPROVALS
Prepared by:Project manager
Approved by:
Project sponsor
Executive sponsor
Client sponsor
Global Star Enterprises is a fictional company created for educational and training purposes only. This document may not be reproduced or distributed, without the prior written permission of the copyright holder. Copyright © Raw Pixel 2015
Project Scope Management Plan Template V1.1 October 2015Page 1 of 6