This Scope Baseline Software Development document shows how Eduardo Montes established and maintained the approved scope baseline for the ProjectAdm SaaS platform — integrating the Project Scope Statement, the Work Breakdown Structure (12 packages), and the WBS Dictionary into the single reference standard against which all deliverables were measured across 28 sprints and five milestone gates. This document is the definitive answer to "what exactly was agreed to be built?" for the ProjectAdm project.

What Is a Scope Baseline?

The Scope Baseline is a PMBOK 8 output in the Planning Performance Domain that consists of three integrated components: the approved Project Scope Statement, the approved Work Breakdown Structure (WBS), and the approved WBS Dictionary. Together, these three documents define exactly what the project will deliver — the product scope (what), the deliverable structure (how it's organized), and the detailed description of each WBS element (what done looks like). The scope baseline is used as the measurement reference for scope performance, and any work outside the baseline constitutes scope creep unless approved through change control.

What This Scope Baseline Software Development Includes

The ProjectAdm Scope Baseline integrates all three baseline components:

• Component 1 — Project Scope Statement (Summary) — Multi-tenant SaaS project management platform; 12 WBS packages; 152,400 LOC target; 5 epics / 1,092 story points; Technology: PHP 8.1 + CodeIgniter 4.4.4 + MariaDB + JavaScript; Exclusions: native mobile, offline mode, PagSeguro (CR-003); Version: v1.4 (post-M4, reflecting CR-001 through CR-004)
• Component 2 — WBS (12 Packages) — 1.1 Architecture + Infrastructure; 1.2 Authentication + User Management; 1.3 Project + Board Management; 1.4 Kanban Engine; 1.5 Team + Collaboration; 1.6 Notifications; 1.7 Gantt Chart Module (added CR-002); 1.8 Billing + Subscriptions; 1.9 Admin Panel; 1.10 AI Suggestions Engine; 1.11 WBS View (added CR-004); 1.12 Landing Page + Documentation
• Component 3 — WBS Dictionary Key Entries — 1.4 Kanban Engine: HTML5 Drag-and-Drop Kanban, unlimited columns, swimlanes, Sprint planning view, Safari-compatible (ISS-003 resolved), delivered Sprint 4–8; 1.7 Gantt Chart Module: D3.js-based Gantt, task dependencies, drag-to-reschedule, critical path highlight, PDF export, delivered Sprint 12–14; 1.10 AI Suggestions Engine: OpenAI API integration with request queuing (ISS-001 mitigation), Sprint 20–24
• Baseline Version History — v1.0 (Jan 28, 2025): original baseline; v1.1 (Feb 21, 2025): CR-001 dark mode added; v1.2 (Feb 21, 2025): CR-002 Gantt chart added (+WBS 1.7); v1.3 (Mar 15, 2025): CR-003 PagSeguro removed; v1.4 (Apr 30, 2025): CR-004 WBS view added (+WBS 1.11)
• Scope Performance at Closure — All 12 WBS packages delivered and accepted; 0 unauthorized scope additions; 4 approved scope changes via formal CRs; final story point count: 1,092 planned + 108 CR additions = 1,200 total, delivered at 42.9 SP/sprint average
• Scope Measurement — Sprint velocity tracked against baseline story point plan; milestone scope accepted by Henry Douglas using Deliverables Acceptance Checklist; scope creep incidents: 0; scope exclusion challenges resolved in both cases within 24 hours by reference to exclusions list

How Eduardo Montes Used This Scope Baseline Software Development

Eduardo Montes referenced the Scope Baseline Software Development document at every sprint review and change request evaluation. When a stakeholder in Sprint 20 asked why PagSeguro wasn't available, Eduardo could point to Scope Baseline v1.3 (March 15, 2025) and CR-003, formally approved six months earlier. The clear version history prevented any "I didn't know that was removed" misunderstandings at the M4 and M5 milestone reviews, saving what could have been hours of unproductive discussion at critical governance gates.

How to Use This Scope Baseline Software Development Document

When maintaining your own Scope Baseline Software Development document, version every change with a date and a reference to the approving change request. The ProjectAdm four-version history created a complete audit trail showing exactly when and why the scope changed — information that proves invaluable when explaining the final product to stakeholders who joined the project at different stages.

Download the Template and Deepen Your Knowledge

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

• Download the Scope Baseline Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Scope 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 Word (.docx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning