Just as the program scope statement defines the extents and boundaries within which to manage the program, the program scope management plan defines how to prepare and manage the program scope statement. It also is developed in the plan program scope process in the Standard for Program Management—Second Edition (2008).
Program Scope Management Plan Instructions
The scope management plan will include the following:
Purpose: A brief introductory statement defining the purpose of the scope man-agement plan, such as:
The scope management plan describes the process of managing scope throughout the program.
This plan describes the process to follow to develop a detailed program scope statement, the program work breakdown structure (PWBS), and the approach to follow for effective scope change control. It also sets forth the rela-tionship between product scope and program scope as it serves to identify the process and activities to produce deliverables and benefits to achieve program goals. This plan then is used to define the program’s goals and objectives.
In the Project Management Institute’s Standard for Program Management—
Second Edition (2008), the scope management plan is an output of plan program scope process. It is an input to the define program goals and objectives process.
Product scope and program scope: This section states the difference between product scope and program scope. It recognizes that product scope involves the features and functions that characterize the products, services, and results of the program, while program scope describes the work required to deliver a major product, service, or benefit. Separate processes may be needed for product scope and program scope, which would be stated in this section. This
64 Implementing Program Management: Templates for Success
section notes that completion of product scope is measured against program requirements, while completion of program scope is measured according to the program management plan and the benefits realization plan.
Expected stability of the scope of the program: This section describes the expected stability of the scope of the program based on information from program stakeholders. The stakeholder register, and its accompanying analy-sis, is reviewed and analyzed, and stakeholders are contacted to define and prioritize their requirements and to obtain inputs concerning program scope acceptance. Program deliverable acceptance criteria are defined in this section for use in determining the overall stability of the scope of the program.
Scope statement development process: This section describes the process to follow to develop the scope statement for the program. A detailed program scope statement is critical to program success. The scope statement addresses the vision, range, capacity, and extent of the program endeavor. It serves to provide a common understanding of the program’s scope by the stakeholders, as it establishes the direction to be taken and the essential aspects of the pro-gram to be accomplished. The process notes appropriate policies, procedures, and templates, which may be helpful in the development of the scope state-ment. It also describes tools and techniques to be used in the development of the scope statement, such as expert judgment, interviews, focus groups, and customer acceptance reviews.
Program work breakdown structure development process: This section describes the process to follow to develop the PWBS. The PWBS provides the framework for organizing and managing the work in the program. The objective is to structure the work in order that future activities and scope are easily managed. This section notes specific PWBS templates that may be con-sidered, the use of expert judgment, lessons learned from previous programs, the various options to consider in program management in order that there is a balance between program deliverables and business objectives, the roles and level of involvement of specific individuals in the ownership of key activities, and methods to verify that the level of decomposition desired is necessary and sufficient.
Program scope change control process: This section describes the methods to use to identify program scope changes. The classification of these changes also is included in this section to determine the types of changes that the pro-gram manager can approve and others that need escalation to the propro-gram governance board. It also describes the process to follow to manage scope so scope creep does not occur, and states how program scope changes will be integrated into the overall program. Specific configuration management tools to be used are stated in this section to be able to monitor change control while enhancing organizational control so there is consistent documentation and product versions throughout the program.
The Program Setup Phase 65
Approvals: This section contains the written approval of the scope management plan by the program sponsor, program manager, program management office, members of the program board or governance board, and other stakeholders.
Scope Management Plan Template
<Insert Program Name>
Scope Management Plan
Program name:
Program manager: PM’s email address here as a hyperlink Program sponsor:
Actual start date:
Approved end date:
Program no.:
Revision history:
Business unit:
A. PurPoSe
A brief introductory statement defining the purpose of the scope management plan, such as:
The scope management plan describes the process of managing scope throughout the program.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
B. ProDuCT SCoPe AnD ProGrAM SCoPe
This section states the difference between product scope and program scope.
It describes how product scope and program scope are measured and states whether there is a need for separate processes to be used for product scope and program scope.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
66 Implementing Program Management: Templates for Success
C. exPeCTeD STABIlITy oF The SCoPe oF The ProGrAM
This section describes the expected stability of the scope of the program based on information from program stakeholders. It defines program deliverable accep-tance criteria as part of this process.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
D. SCoPe STATeMenT DeveloPMenT ProCeSS
This section describes the process to follow to develop the scope statement for the program. It notes appropriate policies, procedures, and templates that may be helpful in the development of the scope statement and describes specific tools and techniques that will be used.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
e. ProGrAM Work BreAkDoWn STruCTure DeveloPMenT ProCeSS This section describes the process to follow to develop the PWBS. It notes the tools and techniques to be used, and the methods to verify that the level of decomposition desired is necessary and sufficient.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
F. ProGrAM SCoPe ChAnGe ConTrol ProCeSS
This section describes the methods to use to identify program scope changes. It includes how changes are classified and the process to follow to manage scope so scope creep does not occur. It states how program scope changes will be integrated into the overall program. It also describes specific configuration man-agement tools to be used.
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
G. APProvAlS
This section contains the approval of the scope management plan by the pro-gram sponsor, propro-gram manager, propro-gram management office, members of the governance board, and other key stakeholders.
The Program Setup Phase 67
SignatureSand date approval obtained
Program manager ____________________________________
Program sponsor ____________________________________
Program management office director ____________________________________
Governance board chairperson ____________________________________
Governance board member 1 ____________________________________
Governance board member N ____________________________________
Stakeholder 1 ____________________________________
Stakeholder 2 ____________________________________
Stakeholder N ____________________________________