HKSM
Control Schedule
A continuous activity that tracks project progress, updates the schedule to reflect actual performance, and governs approved changes to the schedule baseline.
Key Points
- Compares actual progress against the schedule baseline to identify variances.
- Updates the schedule model and forecasts completion dates using current performance data (e.g., SV, SPI).
- Submits and manages change requests to the schedule baseline through integrated change control.
- May apply techniques such as critical path analysis, what-if analysis, and schedule compression (crashing/fast tracking).
Example
Midway through a software project, several critical-path tasks slip. The project manager records actual start/finish dates, recalculates the critical path, forecasts a two-week delay, and evaluates fast tracking to recover time. Because the change affects the baseline finish date, the PM raises a change request for approval and then updates the baseline and schedule once approved.
PMP Example Question
During execution, the team reports multiple delays on critical activities. What is the most appropriate next step in Control Schedule?
- Rebaseline the schedule immediately to reflect the new dates.
- Analyze impacts, update actuals, forecast outcomes, and submit a change request for any baseline changes.
- Ask the sponsor to extend the project deadline informally.
- Add more resources to all late activities without reviewing the critical path.
Correct Answer: B — Analyze, update, forecast, and manage changes through the change control process
Explanation: Control Schedule requires measuring performance, updating the schedule, forecasting, and processing any needed baseline changes via integrated change control, not rebaselining or making unilateral changes.
