This Schedule Baseline Software Development document shows the approved version of the ProjectAdm SaaS platform schedule — the time-phased plan of 28 sprints, 5 milestone gates, and 12 WBS packages that Eduardo Montes baselined on January 28, 2025 and used as the Schedule Performance Index (SPI) reference for all 13.5 months of development. This Excel workbook is the frozen version of the Project Schedule against which all schedule variances were measured.

What Is a Schedule Baseline?

The Schedule Baseline is a PMBOK 8 output in the Planning Performance Domain that represents the approved version of the project schedule, used as the reference for measuring schedule performance. Once approved, the schedule baseline can only be changed through the integrated change control process — informal adjustments to the schedule are a form of scope creep that undermines the EVM measurement system. The schedule baseline is the "SV = EV – PV" denominator: the Planned Value (PV) at any point in the project comes from the baseline, not from the current working schedule.

What This Schedule Baseline Software Development Includes

The ProjectAdm Schedule Baseline workbook contains the approved time-phased schedule in three views:

• Milestone Baseline (Sheet 1) — M1: Jan 31, 2025; M2: Apr 30, 2025; M3: Jul 31, 2025; M4: Oct 31, 2025; M5: Feb 28, 2026; all 5 dates fixed and unchanged through project closure; actual delivery dates identical to baseline dates for all 5 milestones
• Sprint-Level Baseline (Sheet 2) — 28 rows: Sprint number, start date, end date, planned story points, cumulative planned SP, planned value (PV) in dollars; baseline velocity: 40 SP/sprint (Sprints 1–5), 42 SP/sprint (Sprints 6–28 after Phoenix calibration); total baseline: 1,092 SP; actual total: 1,200 SP (108 SP from CRs added to working schedule but not to baseline)
• WBS Package Baseline (Sheet 3) — Start sprint, end sprint, planned SP, planned cost per package; key entries: 1.4 Kanban (Sprints 4–8, 120 SP, $44,800); 1.7 Gantt/CR-002 (added to working schedule v1.2, not in original baseline — tracked separately); 1.10 AI Engine (Sprints 18–24, 112 SP, $28,400)
• Baseline Version History — v1.0 (Jan 28, 2025): original; v1.1 (Feb 4, 2025): CR-001 dark mode resequencing; v1.2 (Feb 21, 2025): CR-002 Gantt added; v1.3 (Mar 15, 2025): CR-003 PagSeguro removed (freed 2 sprints); v1.4 (Apr 10, 2025): CR-004 WBS view added; final approved baseline: v1.4
• SPI Performance Against Baseline — Sprint 1–12: SPI 0.97–1.02 (GREEN); Sprint 13–16: SPI 0.82–0.95 (ISS-002 impact, YELLOW); Sprint 17–28: SPI 0.97–1.01 (GREEN — recovered); Final SPI at M5: 0.99; Schedule variance at closure: -5 SP (ISS-006 optimization deferred post-launch)

How Eduardo Montes Used This Schedule Baseline Software Development

Eduardo Montes used the Sprint-Level Baseline (Sheet 2) as the primary EVM source for all SPI calculations. The baseline's fixed planned value per sprint allowed him to calculate SPI to two decimal places every Friday afternoon in under 5 minutes — a calculation that would have taken 30 minutes without a clean, structured baseline. The Sprint 15 SPI of 0.82 — visible in the SPI column — triggered the corrective action that prevented a schedule extension.

How to Use This Schedule Baseline Software Development Document

When establishing your own Schedule Baseline Software Development, resist the temptation to update the baseline whenever the working schedule changes. The ProjectAdm team managed ISS-002's 3-sprint delay within the buffer without a baseline update — which correctly showed SPI below 1.0 (a warning signal) rather than resetting to 1.0 and hiding the performance problem. Only approved change requests should trigger baseline updates.

Download the Template and Deepen Your Knowledge

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

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