A program manager has a multiple-project program that is scheduled to be completed by year’s end. During the program delivery phases of the projects, several mandatory changes are identified that would extend the program’s completion date. What is the next step for the program manager?

The identification of mandatory changes that impact a program baseline, such as the completion date, necessitates formal action through the established governance framework. The program manager's primary responsibility is to analyze the impact of these changes and formally communicate them to the governing body. Submitting a change request is the correct procedural step to seek approval for modifying the program's schedule baseline. This ensures that the decision is documented, reviewed by the appropriate stakeholders (e.g., the steering committee), and officially authorized before any baselines are altered or corrective actions are implemented.

A. Applying resource leveling is a schedule compression technique that may be considered during impact analysis, but it is not the initial formal step for a baseline change.
B. The program manager cannot unilaterally update the schedule baseline. This action requires formal approval through the change control process.
C. Adjusting working hours (crashing) is a potential response to a schedule variance, but it must be evaluated and approved as part of a formal change request, not implemented independently.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.).

Section 3.4.4.3

Program Change Management: This section details the process for managing changes within a program. It states

"The program manager is responsible for establishing and managing the program’s change management process... This process includes the steps by which all changes are identified

evaluated

approved

and managed." Submitting a change request is the initial step in this formal process.

Figure 3-11

Sample Program Change Management Process: This flowchart explicitly shows that the process begins with "Identify and Document Change Request." The scenario describes the identification of a change

making the documentation and submission of a request the next logical and procedural step.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.).

Section 4.6

Perform Integrated Change Control: While focused on projects

the principle is fundamental to programs as well. This process is used to "review all change requests; approve changes and manage changes to deliverables

organizational process assets

project documents

and the project management plan; and communicate decisions." This underscores the necessity of a formal request before updating plans like the schedule.