HKSM

Schedule forecasts are predictions of future schedule performance and key dates based on actual progress, trends, and expected conditions. They estimate milestone completions, final delivery dates, and likely variances, often expressed as ranges with stated assumptions.

Key Points

• Schedule forecasts predict future start and finish dates for milestones and the overall project, along with expected variances from the baseline.
• They are derived from current progress, trend analysis, critical path changes, and performance metrics such as SPI or earned schedule.
• Results are best presented as ranges with confidence levels and documented assumptions.
• Forecasts should be updated at a regular cadence or when significant changes occur.
• They guide corrective and preventive actions, resource adjustments, and change control decisions.
• Forecasts integrate with cost, risk, and resource information to provide a realistic outlook.

Purpose

Provide an evidence-based view of when work is likely to finish and where schedule risk exists, enabling timely decisions to protect or recover delivery dates.

• Support stakeholder expectations with credible dates.
• Enable proactive schedule control and resource planning.
• Trigger risk responses and contingency use when trends worsen.
• Inform change requests if baseline dates are no longer achievable.

Data Sources

• Approved schedule baseline and current schedule model.
• Actual start/finish dates, percent complete, and work remaining.
• Milestone status and critical/near-critical path analysis.
• Performance metrics (PV, EV, SPI; earned schedule metrics if used).
• Resource availability and calendars.
• Risk register and quantitative analysis outputs (e.g., Monte Carlo results).
• Change log, issue log, and external dependencies or constraints.

How to Compile

• Collect actual progress and update the schedule model with true status (starts, finishes, remaining durations).
• Recalculate the schedule to refresh critical and near-critical paths and total float.
• Analyze variances versus the baseline for key activities and milestones.
• Compute performance trends (e.g., SPI or earned schedule) and review near-term slippages.
• Run what-if scenarios to test recovery options; perform quantitative risk analysis if applicable.
• Produce forecast dates for milestones and project completion; express as ranges with confidence levels where possible.
• Document assumptions, constraints, and drivers behind the forecast (e.g., resource limits, learning curve, vendor lead times).
• Review with the team and stakeholders; update the forecast and escalate potential baseline changes through governance.

How to Use

• Communicate realistic dates in status reports and steering reviews.
• Prioritize corrective actions on the critical and near-critical paths.
• Adjust sequencing, leads/lags, or resource allocations to improve outcomes.
• Activate risk responses and schedule reserves when thresholds are breached.
• Initiate change requests if the forecast shows sustained deviations from the baseline.
• Coordinate with cost forecasts to assess overall project viability and trade-offs.

Sample View

• Milestone: Design Complete — Baseline: 05 Apr — Forecast: 12 Apr (Slip: +7 days), Confidence: 80%, Drivers: approval delays.
• Milestone: UAT Start — Baseline: 18 Jun — Forecast: 22 Jun (Slip: +4 days), Confidence: 70%, Drivers: resource bottleneck.
• Project Finish — Baseline: 30 Sep — Forecast Range: 08–20 Oct (P70: 14 Oct), Key Risks: vendor lead time, rework.
• Trend Note: SPI = 0.92 last 4 weeks; near-critical path gaining risk (float < 5 days).
• Recovery Options: add tester for 3 weeks, fast-track two validation tasks, or defer low-value scope.

Interpretation Tips

• Focus on the critical and near-critical paths; variance off the critical path may not affect finish dates.
• Treat forecasts as ranges; single-point dates can mask uncertainty.
• Do not rely on a single metric like SPI; corroborate with path analysis, remaining work, and risks.
• Check calendar effects (holidays, shutdowns) and resource availability behind the dates.
• Separate performance-driven slippage from scope or dependency changes to choose the right response.
• Update assumptions regularly; outdated assumptions make forecasts misleading.

PMP Example Question

Midway through a project, the latest schedule forecast shows a 3-week slip to the final milestone. The team identifies options: add resources to critical activities, fast-track two tasks, or request a baseline change. What should the project manager do first?

1. Submit a change request to revise the schedule baseline.
2. Analyze critical and near-critical paths and run what-if scenarios for the options.
3. Add resources immediately to recover the slip.
4. Report the slip and wait for sponsor direction.

Correct Answer: B — Analyze critical and near-critical paths and run what-if scenarios for the options.

Explanation: The manager should evaluate options using the schedule model to determine the most effective corrective action before escalating or changing the baseline. Decisions should be evidence-based and aligned to governance.