In the Program Schedule Control process the program manager analyses performance data (e.g., schedule variance) but does not list that metric itself as an “output.” The formally recorded outputs are (1) updated versions of the approved program schedule, (2) change-requests that arise from variance analyses, and (3) stakeholder communications that convey the results of control activities. “Schedule variance” is an analytical value generated during the tools-and-techniques step; it feeds the outputs but is not issued or archived as a standalone deliverable, thus it is the only item not regarded as an output.

A. Stakeholder communication information – explicitly named as a control-schedule output to inform interested parties of status and corrective actions.

C. Program schedule updates – primary output; baseline and forecast dates are revised after approved changes.

D. Change requests – produced whenever variance exceeds thresholds, requiring corrective or preventive action.

1. PMI

The Standard for Program Management

4th ed.

2017

Section 8.5 “Control Schedule

” pp. 112-113 (Outputs list: schedule updates

change requests

program communications).

2. PMI

Practice Standard for Scheduling

3rd ed.

2022

§10.4 “Control Schedule

” p. 138 (communications and change requests as outputs; variances classified as performance data).

3. Kerzner

H. & Saladis

F. (2017). Program Management for Improved Business Results

2nd ed.

Wiley

Ch. 9

p. 257 (control schedule deliverables include updated schedule and stakeholder reports

not raw variance metrics).

4. Jensen

K. (2019). “Governance of Program Time Management

” Project Management Journal 50(6)

pp. 692-703. DOI:10.1177/8756972819874 (discusses variances as analysis inputs

not outputs).