Fictional case study · Document 08 · Week 2 baseline
Work Breakdown Structure
The approved project scope is organized into deliverables and manageable work packages.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
WBS hierarchy
Aegis Security Cloud Modernization
├── 1.0 Project management
│ ├── 1.1 Approved project baseline
│ ├── 1.2 Project reporting and decisions
│ └── 1.3 Project closure
├── 2.0 Modernized application
│ ├── 2.1 Validated runtime and dependencies
│ ├── 2.2 Reliable BookEasy connector
│ └── 2.3 Operational monitoring
├── 3.0 Database migration
│ ├── 3.1 Validated migration and recovery procedures
│ └── 3.2 Verified production database migration
└── 4.0 Validation and delivery
├── 4.1 Integrated test results
├── 4.2 BookEasy pilot acceptance
├── 4.3 Approved application release
└── 4.4 Operations handoverThe WBS describes what the project will deliver. The project is divided into project management, modernized application, database migration, and validation and delivery. The lower-level packages are: 1.1 approved project baseline, 1.2 project reporting and decisions, 1.3 project closure; 2.1 validated runtime and dependencies, 2.2 reliable BookEasy connector, 2.3 operational monitoring; 3.1 validated migration and recovery procedures, 3.2 verified production database migration; 4.1 integrated test results, 4.2 BookEasy pilot acceptance, 4.3 approved application release, and 4.4 operations handover. Detailed activities, owners and acceptance checks are recorded in the backlog and responsibility matrix.
Deliverables and work packages
| WBS ID | Deliverable or work package | Completion evidence |
|---|---|---|
| 1.0 | Project management | Coordinated and closed project |
| 1.1 | Approved project baseline | Charter, requirements, schedule and responsibilities recorded |
| 1.2 | Project reporting and close-out | Status, decisions and closure recorded |
| 2.0 | Modernized application | Supported application ready for integration testing |
| 2.1 | Runtime and dependencies validated | Selected supported runtime and compatible libraries tested |
| 2.2 | BookEasy connector and monitoring validated | Retry, duplicate handling and operational alerts tested |
| 3.0 | Database migration | Migrated database and recovery readiness |
| 3.1 | Migration and restore rehearsal completed | Reconciliation and restore evidence recorded |
| 3.2 | Database migration completed | Approved database migration executed and verified |
| 4.0 | Validation and delivery | Customer-accepted pilot and controlled release |
| 4.1 | Integrated test evidence completed | Agreed functional, security and recovery checks completed |
| 4.2 | BookEasy pilot accepted | BookEasy accepts agreed pilot scenarios |
| 4.3 | Application and connector production release authorized | Sponsor go/no-go and controlled deployment recorded |
| 4.4 | Operations handover completed | Runbook and support responsibilities transferred |