This Project Schedule Software Development document shows the complete time-phased schedule for the ProjectAdm SaaS platform — presenting all 28 sprints, 12 WBS packages, 5 milestone gates, and key activities from January 15, 2025 through February 28, 2026 in a structured Excel workbook. Eduardo Montes used this schedule as the baseline against which SPI was calculated biweekly, providing the EVM measurement foundation for all schedule performance reporting.

What Is a Project Schedule?

A Project Schedule is a PMBOK 8 output in the Planning Performance Domain that links activities, resources, and time into an integrated plan showing when project work will be performed. It includes planned start and finish dates, durations, dependencies, and milestones. In hybrid projects, the schedule must represent both the Agile sprint cadence (showing story points and velocity) and the predictive milestone structure (showing fixed gate dates and deliverable acceptance deadlines). The approved project schedule becomes the Schedule Baseline, the reference point for all schedule variance and SPI calculations.

What This Project Schedule Software Development Includes

The ProjectAdm Project Schedule workbook presents the schedule at three levels of detail:

• Level 1 — Milestone Schedule (Sheet 1) — M1: Jan 31, 2025 (Architecture + Infra); M2: Apr 30, 2025 (MVP Core); M3: Jul 31, 2025 (SaaS Engine); M4: Oct 31, 2025 (Advanced Features); M5: Feb 28, 2026 (Go-Live); all 5 milestones delivered on original target dates
• Level 2 — Sprint Schedule (Sheet 2) — All 28 sprints: Sprint number, start date, end date, working days, planned story points, WBS packages in scope, key deliverables, milestone gate (if applicable); velocity column updated biweekly with actuals; variance column = actual SP – planned SP; cumulative SPI calculated at each sprint
• Level 3 — WBS Package Schedule (Sheet 3) — Start sprint, end sprint, total sprints, planned story points per WBS package: 1.1 Architecture (Sprints 1–3, 48 SP); 1.2 Auth (Sprints 2–6, 72 SP); 1.4 Kanban (Sprints 4–8, 120 SP); 1.7 Gantt/CR-002 (Sprints 12–14, 80 SP); 1.10 AI Engine (Sprints 18–24, 112 SP); 1.12 Landing Page (Sprints 25–27, 40 SP)
• Critical Path Activities — Architecture setup → Authentication + Database schema → Kanban board + Multi-tenant isolation → Billing integration → AI Engine → Production deployment; float on non-critical paths: 84 SP total across 28 sprints; ISS-002 consumed 36 SP of float in Sprints 14–16 and was fully recovered by Sprint 20
• Schedule Performance History — SPI never fell below 0.82 (Sprint 15 low); recovered to 0.97 by Sprint 18; SPI at M5 closure: 0.99; total schedule variance at closure: -5 story points (delivered 1,200 vs. planned 1,205 — 5 SP of ISS-006 optimization deferred to post-launch)
• Schedule Baseline Updates — Baseline v1.0 (Jan 28, 2025): original; v1.1–v1.4: updated per CRs (CR-001 through CR-004); ISS-002 3-sprint delay absorbed without baseline update (managed within buffer); Final baseline: v1.4 (Apr 10, 2025)

How Eduardo Montes Used This Project Schedule Software Development

Eduardo Montes updated the Project Schedule Software Development workbook every other Friday, entering the actual sprint velocity and recalculating the SPI trend. The Sprint 15 SPI dip to 0.82 — visible in the SPI trend chart in Sheet 2 — triggered the corrective action that prevented a schedule extension. The schedule's "planned vs. actual" velocity columns were Eduardo's most frequently used project management tool: they showed at a glance whether the project was on track without requiring a Gantt chart interpretation session.

How to Use This Project Schedule Software Development Document

When building your own Project Schedule Software Development workbook for a hybrid project, maintain both the sprint velocity view (for the team) and the milestone date view (for stakeholders) in the same workbook. The ProjectAdm approach of keeping both views synchronized meant Eduardo never had to manually reconcile two separate tracking tools — a common source of reporting errors on hybrid projects.

Download the Template and Deepen Your Knowledge

Ready to create your own project schedule? Download the blank Project Schedule Template (PMBOK 8).

• Download the Project Schedule Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Project Schedule 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: Planning