keymodels
Menu
SearchStart free
TemplateTemplate / formTeam

Program Scope Management Plan

When and how should program scope management plan be applied?

Public preview

What this template contains.

Purpose. Use this plan to define how programme scope will be developed, decomposed, accepted, controlled and communicated throughout the lifecycle. It establishes the process for producing the detailed programme scope statement and programme work breakdown structure, then managing changes without losing alignment with objectives and benefits. Application. Scope management must connect what the programme will deliver with the work required to deliver it. It should also distinguish product scope from programme scope

Program Scope Management Plan23 fields
Document control
Program nameProgram managerProgram sponsor
A. Purpose
Purpose
B. Product and program scope
Product scope and program scope
C. Scope stability
Expected stability of program scope
D. Scope statement process
Scope statement development process
E. Work breakdown structure
Program work breakdown structure development process

Use context

Purpose, application, discipline.

Purpose

Use this plan to define how programme scope will be developed, decomposed, accepted, controlled and communicated throughout the lifecycle. It establishes the process for producing the detailed programme scope statement and programme work breakdown structure, then managing changes without losing alignment with objectives and benefits.

Application

Scope management must connect what the programme will deliver with the work required to deliver it. It should also distinguish product scope from programme scope so that completion is assessed against the correct requirements and plans.

Completion discipline

Complete the document from current evidence, name its owner and approving authority, and link the plans, registers or decisions that support it. Retain approved versions and review the document whenever a material assumption, dependency, requirement or governance decision changes.

Field summary

Structured sections without protected files.

8 fields

Document control

Program name, Program manager, Program sponsor, Actual start date

1 fields

A. Purpose

Purpose

1 fields

B. Product and program scope

Product scope and program scope

1 fields

C. Scope stability

Expected stability of program scope

1 fields

D. Scope statement process

Scope statement development process

1 fields

E. Work breakdown structure

Program work breakdown structure development process

1 fields

F. Scope change control

Program scope change-control process

9 fields

G. Approvals

Program manager, Program sponsor, Program management office director, Governance Board chairperson

Protected resources

Included resource formats.

Working sheetImplementation contextField schema
Working sheet - CSV

Related models