Project Scope Management
Mona78
ScopeManagementPlanTemplatewithInstructions.docx
[Insert Project Name]
Project Scope Management Plan (SMP)
[Student - Template]
[Insert Project Name]
[Insert Project Name]
Scope Management Plan [Insert Version Number] | Page 2
SMP Version History
|
Version # |
Date |
Author |
Key Differences |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
3 Roles and Responsibilities 5
4 Scope Management Processes 6
4.2 Creation of the Work Breakdown Structure (WBS) and Dictionary 7
4.3 Deliverable Validation and Acceptance 10
Introduction to the Scope Management Plan Template
The Scope Management Plan (SMP) is created during the project’s Planning/Definition Process Phase and is considered a component of the Project Management Plan (PMP). The purpose of the Scope Management Plan is to document the defined scope management approach and processes, as well as the roles and responsibilities for Stakeholders participating in those processes.
The Scope Management Plan serves as a written reference guide. It describes how the project team will define and develop the project scope, create the Work Breakdown Structure (WBS), validate the scope, verify completion of project deliverables, control the scope baseline, and handle scope changes.
The following sections are constructed to match the suggested heading structure for the Scope Management Plan. Each section provides instructions and descriptions to help the reader understand the section purpose and how to complete it.
Template style conventions are as follows:
|
Style |
Convention |
|
Normal text |
Indicates placeholder text that can be used for any project. |
|
[Instructional text in brackets] |
[Indicates text that should be replaced/edited/deleted by the user] |
|
Example text in italics |
Indicates text that might be replaced/edited/deleted by the user REPLACE EXAMPLES PROVIDED WITHIN THIS TEMPLATE WITH YOUR OWN, SPECIFIC TO YOUR CHOSEN CASE STUDY PROJECT |
As you complete the template, please remember to delete all instructional text (including this section) and update the following items, as applicable:
· title page
· version history
· table of contents
· headers / footers
Introduction
[Describe the purpose of the Scope Management Plan and how scope will be managed throughout the project. Information contained in this section should be tailored to fit a particular project’s needs.]
Approach
[Describe the activities, processes, and procedures used to manage the scope of the project. This section describes the processes that will be used to prepare the project Scope Statement, create the Work Breakdown Structure (WBS), validate completion of project deliverables, and control requirement change requests to the project scope.]
Roles and Responsibilities
[Describe the Roles and Responsibilities of those involved in the Scope Management process. The following table is provided as an example and can be extended to meet a project’s specific needs.]
Example: (remember: replace examples in this document with your own)
|
Name |
Role |
Responsibility |
|
[Name] |
Project Sponsor |
· |
|
[Name] |
Executive Project Steering Committee (if used) |
· |
|
[Name] |
Project Manager |
· |
|
[Name] |
Key Stakeholder(s) |
· |
|
[Name] |
Project Team Members and Subject Matter Experts (SMEs) |
· |
|
[Name] |
Other Key Stakeholders? |
· |
Scope Management Processes
Definition of Scope
[In this section, describe the approach to developing the project scope statement.]
Creation of the Work Breakdown Structure (WBS) and Dictionary
[Discuss how the project scope is to be sub-divided into smaller deliverables in a Work Breakdown Structure (WBS) and WBS Dictionary, and how these smaller components are managed during the project. Provide a high-level WBS with accompanying WBS Dictionary components (Student Reminder: This is a high-level WBS - we will develop a detailed WBS later in the Scope Management class)
Example:
This section contains the Work Breakdown Structure (WBS) and related information. The WBS and its corresponding WBS Dictionary are important components of effective scope management.
Example: WBS (remember: replace examples in this document with your own)
|
Level 1 |
Level 2 |
Level 3 |
|
1. Widget Management System |
1.1 Initiating |
1.1.1 Evaluation and Recommendations 1.1.2 Develop Project Charter 1.1.3 Deliverable: Submit Project Charter 1.1.4 Project Sponsor Reviews Project Charter 1.1.5 Project Charter Signed and Approved |
|
|
1.2 Planning |
1.2.1 Create Preliminary Scope Statement 1.2.2 Determine Project Team 1.2.3 Project Team Kickoff |
|
|
1.3 Executing |
1.3.1 Project Kickoff Meeting 1.3.2 Verify and Validate User Requirements 1.3.3 Design System 1.3.4 Procure Hardware/Software 1.3.5 Install Development System |
|
|
1.4 Closeout |
1.4.1 Audit Procurement 1.4.2 Document Lessons Learned |
Example: WBS Dictionary
|
WBS Level |
WBS Code |
WBS Element Name |
Description of Work |
Deliverable(s) |
Committed Resources |
Comments |
|
1 |
1 |
Widget Management System |
Automated System to Manage Widgets |
Tested and accepted Widget Mgt System |
Project Manager Technical Analyst SMEs |
|
|
2 |
1.1 |
Initiating |
Initiation of Project to build Widget Management System |
Charter [include additional deliverables] |
Project Manager Business Analyst SMEs |
|
|
3 |
1.1.1 |
Evaluation and recommendations |
Evaluation of options and recommendations |
Evaluation and Recommendations Report |
Project Manager Business Analyst SMEs |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[Insert Project Name]
Deliverable Validation and Acceptance
[Document the project deliverables. Discuss how deliverables will be validated against the original scope (e.g. business case or case study overview) and how deliverables will be formally accepted by Sponsor and customer.
[Best Practice: Project deliverables should be formally accepted and signed off by the Project Sponsor throughout the project and not held back as a single set of deliverables at the end of the project.]
Control Scope
[Describe the change process for making changes to the project scope to prevent scope creep.]
