<Project Name> Scope Management Plan. <Author> <Date> Name Date Reason For Changes Version <author> initial draft 1.0 draft1

Transcription

1 <Project Name> Scope Management Plan <Author> <Date> <Version> 1.0 Revision History Name Date Reason For Changes Version <author> initial draft 1.0 draft1 2.0 Statement of Purpose The purpose of this document is to document the processes that will be used to manage <project name> s scope. This document includes (a) a project overview, (b) the roles and responsibilities of those responsible for managing project scope, (c) the project requirements, (d) the project deliverables, (e) the project success criteria, (f) information about the work breakdown structure development, (g) procedures for scope baselining, (h) how scope documentation will be conducted (i) the scope change management process, (j) the plan modification rules, and (k) a section for approval signatures. 1

2 Project Overview Project Objectives Provide a list of what <project name> will accomplish in terms of the products/service that will be produced. Also, indicate the target benefits of <project name.> Roles and Responsibilities <Describe how people involved in <project name> will be involved in the management of scope.> Role <Add rows as necessary> 2

3 Documentation Work Breakdown Structure The different tasks that need to be completed for <project name> will be accumulated in a work breakdown structure (WBS), which is located in an appendix to this plan. Scope Change Management Process Explain how changes in <project name> s scope will be addressed. This involves a description of how any changes in scope will be identified, addressed, communicated, and documented. Provide a list of the members of the Change Control Board who will be approving/rejecting any changes, as well as the procedures in place to request a change. 3

4 Work Breakdown Structure Work Breakdown Structure 1. Main Task Sub-Task 1.2. Sub-Task 1.3. Sub-Task Sub-Subtask Sub-Sub-Subtask Sub-Sub-Subtask 1.4. Sub-Task 1.5. Sub-Task 2. Main Task Sub-Task 2.2. Sub-Task 2.3. Sub-Task Sub-Subtask Sub-Subtask Sub-Subtask 3. <Add main tasks and sub-tasks as necessary.> Work Breakdown Structure Dictionary WBS Item Number <Enter WBS item number here> WBS Item Name <Enter WBS item name here> WBS Item Description <Enter WBS item description here> 4

5 Change Request Form 2.0 Change Information Change No. Change Requestor Change Request Date Change Urgency Change Description <Assign a number of the change request form> <Specify the person who has requested this change> <Record the date on which the change was requested here> <Enter the priority of the change (High, Medium, or Low) <Add a brief description of the change requested here> 3.0 Change Drivers <Describe the events that made this change necessary.> Example: recent change in stakeholder s request 4.0 Justification for Change <Enter justification for the change here.> 5

6 5.0 Change Recommendation <Enter how the change will be implemented if the request is accepted.> 6.0 Impact of the Proposed Change Impacts Scope Schedule Cost Staffing Risk Other Description <Describe the impact on <project name> s scope if this change is implemented> Example: An additional web page will need to be designed <Describe the impact on <project name> s schedule if this change is implemented> Example: The project end date will be delayed by one week <Describe the impact on <project name> s budget if this change is implemented> Example: The cost of the project will increase by $1000 <Describe the impact on staffing requirements if this change is implemented> Example: Two additional junior programmers will be needed <Describe the impact on the risks associated with <project name> if this change is implemented> Example: The use of a new software will be risky <Describe how the change will affect other areas of <project name> 6

7 7.0 Required Approvals Name Position Signature Date Approve/Reject The signatures above represent stakeholders decision whether to approve/reject the change. 7