Control Schedule

Control Schedule

Introduction: Why This Matters

Time is one of the most visible and closely monitored project constraints. Even small delays can cascade into major cost overruns or stakeholder dissatisfaction. The Control Schedule process ensures that the project schedule is monitored, variances are identified, and corrective or preventive actions are taken to keep the project on track.

On the PMP exam, this process is heavily tested through questions about schedule variance, schedule compression (crashing and fast tracking), critical path analysis, and earned value schedule metrics (SPI, SV). In practice, strong schedule control enables proactive adjustments and supports timely delivery of project objectives.

Purpose and Objectives

Primary Purpose: To monitor the project schedule and manage changes to the schedule baseline.

Key Objectives:

• Measure actual progress against the schedule baseline.
• Identify schedule variances and analyze their causes.
• Forecast future performance using schedule models.
• Apply corrective and preventive actions such as crashing or fast tracking.
• Maintain updated and realistic schedule forecasts.
• Submit change requests for significant schedule adjustments.

Overview

Control Schedule is about comparing where you planned to be against where you actually are, then deciding how to respond. You continually analyze performance, forecast future dates, and adjust the schedule baseline when necessary through formal change control.

• Measure: Collect work performance data and calculate SV and SPI.
• Analyze: Determine root causes of variances and assess impact on critical path.
• Decide: Choose appropriate actions such as crashing, fast tracking, or scope trade-offs.
• Update: Issue change requests and update the schedule baseline and forecasts as needed.

Characteristics

• Continuous: Performed throughout the project to track schedule health.
• Data driven: Relies on earned value metrics, trend analysis, and forecasting.
• Critical path focused: Prioritizes activities that determine the overall project end date.
• Change controlled: Significant schedule adjustments require integrated change control.

Inputs, Tools & Techniques, Outputs (ITTOs)

Inputs

• Project management plan (schedule management plan, schedule baseline).
• Project schedule and schedule data.
• Work performance data.
• Organizational process assets (lessons learned, reporting templates).

Tools & Techniques

• Data Analysis:
  • Earned value analysis (SV, SPI).
  • Trend analysis for forecasting completion dates.
  • What-if scenario analysis.
• Schedule Compression:
  • Crashing: Add resources to shorten critical path activities.
  • Fast tracking: Perform activities in parallel that were planned sequentially.
• Critical Path Method (CPM): Analyze the longest path through the project network.
• Resource Optimization: Level or smooth resource usage to stabilize the schedule.
• Leads and Lags: Adjust dependencies to optimize schedule.
• PMIS tools: Dashboards and software for schedule tracking.

Outputs

• Work performance information.
• Schedule forecasts.
• Change requests.
• Updates to project management plan (schedule baseline, performance baseline).
• Project document updates (schedule data, risk register, lessons learned).

Schedule Performance Metrics

• Schedule Variance (SV) = EV – PV

Positive SV means ahead of schedule, negative SV means behind schedule.

• Schedule Performance Index (SPI) = EV ÷ PV

SPI greater than 1 means ahead of schedule, SPI less than 1 means behind schedule.

• Forecasting: Estimate at completion (EAC) for schedule, based on performance trends.

Practical Example: IT Infrastructure Upgrade

Context: A company is upgrading its IT infrastructure across multiple locations.

Control Schedule activities:

• Monitoring: SPI = 0.85 indicates the project is behind schedule.
• Variance analysis: Delay is traced to late delivery of critical servers.
• Corrective action:
  • Apply crashing by bringing in additional staff for installation.
  • Apply fast tracking by overlapping server testing with network configuration.
• Forecasting: Updated projections show the project can still finish on time if actions are taken immediately.

Outcome: The project schedule is realigned with the baseline, preventing major delays.

Common Pitfalls

Ignoring critical path

• Pitfall: Focusing on non critical tasks.
• Prevention: Always prioritize critical path activities.

Overusing schedule compression

• Pitfall: Excessive crashing increases costs, while fast tracking raises risks.
• Prevention: Use crashing or fast tracking only when justified by analysis.

Weak forecasting

• Pitfall: Tracking past performance only.
• Prevention: Use trend and predictive analysis to anticipate issues early.

Uncontrolled changes

• Pitfall: Adjusting the schedule informally.
• Prevention: All baseline changes must go through integrated change control.

Quick Recap Table

Key Takeaways

• Control Schedule ensures the project finishes on time by monitoring, analyzing, and adjusting the schedule.
• Key tools include variance analysis, SPI/SV, schedule compression, and critical path method.
• Outputs include forecasts, change requests, and updates to schedule and performance baselines.
• On the PMP exam, analyze variance and root causes before deciding on corrective action.
• In practice, proactive schedule control prevents cascading delays and stakeholder dissatisfaction.

Next Step

With Control Schedule complete, the next process is Control Costs, which monitors financial performance and ensures the project stays within budget.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.