This Schedule Forecasts Software Development workbook captures the sprint-by-sprint projections of when the ProjectAdm SaaS platform would be delivered — updated every two weeks by Eduardo Montes using the Schedule Performance Index (SPI) and qualitative team intelligence to predict whether M5 (Feb 28, 2026) was still achievable. This Excel file is the living evidence that schedule forecasting is not a one-time estimate but a continuously recalibrated prediction updated as the project produces real performance data.

What Are Schedule Forecasts?

Schedule Forecasts are a PMBOK 8 output in the Measurement Performance Domain representing estimates or predictions of conditions and events in the project's future based on information and knowledge available at the time of the forecast. The primary quantitative tool is the Schedule Performance Index (SPI = EV ÷ PV): an SPI below 1.0 indicates the project is behind schedule; above 1.0, ahead. The Estimated Date of Completion (EDC) is derived from the SPI: EDC = Status Date + (Remaining Duration ÷ SPI). Schedule Forecasts also include qualitative adjustments — a team with high velocity in the most recent sprints may forecast a faster recovery than the raw SPI suggests, while a team facing a known risk event may forecast a slower delivery despite a healthy SPI.

What This Schedule Forecasts Software Development Includes

The ProjectAdm Schedule Forecasts workbook contains four worksheets maintained sprint-by-sprint for all 28 sprints:

• SPI Tracker — Sprint number, status date, PV (Planned Value), EV (Earned Value), SPI, and SPI trend (3-sprint rolling average); color-coded: green (SPI ≥ 0.95), yellow (0.85–0.95), red (< 0.85)
• EDC Projections — Estimated Date of Completion calculated by three methods: SPI-based, velocity-based (Agile story points remaining ÷ average velocity), and expert-judgment adjustment; consensus EDC used for reporting
• Schedule Variance Log — Sprint-by-sprint SV (SV = EV – PV) in dollars; cumulative SV; root-cause annotation for significant variances (e.g., Sprint 5: "ISS-002 MariaDB degradation — 3-sprint delay; SV = −$21,000")
• Recovery Scenario Analysis — Three scenarios (pessimistic: +4 sprints; base: +2 sprints; optimistic: on-time) with probability estimates; updated each sprint when SPI < 0.90

How Eduardo Montes Used This Schedule Forecasts Software Development

Eduardo Montes updated the Schedule Forecasts workbook at every Sprint Review, presenting the consensus EDC to Henry Douglas (PO/Tech Lead/Co-Sponsor) and the steering committee. Sprint 5 was the critical inflection: ISS-002 caused SPI to drop to 0.71 — the lowest point in the project. Eduardo's scenario analysis showed that if the team achieved velocity ≥ 42 story points per sprint (vs. the baseline 38), the Feb 28, 2026 delivery date was recoverable without a baseline change. The team accepted the challenge: by Sprint 12, SPI had recovered to 0.94; by Sprint 20, SPI = 1.02 (ahead of schedule). The Schedule Forecasts workbook provided the evidence that the recovery strategy was working — without it, the steering committee would have had no basis for deciding whether to extend the deadline or compress scope.

How to Use This Schedule Forecasts Software Development Document

When building your own Schedule Forecasts Software Development tracker, combine SPI with velocity trends rather than relying on SPI alone. SPI is a lagging indicator — it reflects what happened in past sprints. Velocity trend (story points per sprint over the last 3 sprints) is a leading indicator: a rising velocity trend predicts SPI improvement before it shows up in the numbers. The ProjectAdm team used this combined view to give Henry Douglas early confidence that M3 (Jul 31, 2025) was achievable even when cumulative SPI was still below 1.0. Document the root cause of every significant SV — the annotation tells the story that the number alone cannot.

Ready to create your own schedule forecasts tracker? Download the blank Schedule Forecasts Template (PMBOK 8).

• Download the Schedule Forecasts Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Schedule Forecasts in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Measurement