Fictional case study · Document 03 · Week 1
Project Charter
The sponsor authorizes the project, its boundaries, responsibilities and success criteria.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Purpose and authorization
The CTO sponsors and authorizes the project manager to coordinate a BookEasy pilot of the SIEM core modernization. The project aims to restore supportability and improve event delivery without rebuilding the product.
Methodology
This project uses a hybrid approach. We use a planned approach for scope, risks, approvals, dates, and release decisions. We use small delivery and test steps for the technical work, so the team can find and fix issues before moving forward.
Scope
| Included | Excluded |
|---|---|
| Supported Node runtime and compatible application dependencies | A new product or complete SIEM redesign |
| BookEasy connector retries and deduplication | Modernization of every customer connector |
| PostgreSQL migration rehearsal and controlled release | A wholesale redesign of the dashboard or detection rules |
| Monitoring, testing, pilot, handover and close-out | Rollout to all customers |
Main deliverables
The project produces an approved baseline and delivery plan, current-state and dependency evidence, migration and restore rehearsal evidence, BookEasy reliability and monitoring changes, test and rollback evidence, pilot acceptance, release approval, and operations handover.
Success and constraints
Acceptance requires supported target versions, a successful restore rehearsal, passing agreed login, event ingestion, alert and dashboard tests, and BookEasy validation of the pilot sample. No unresolved critical release-blocking defect may remain.
The team must protect customer data, maintain the existing service during preparation and use an approved change window and rollback plan for production. Budget and team capacity are assumed available for this fictional case; no actual budget is claimed.
Initial risks and resources
Initial risks include regressions after the runtime update, an incomplete database restore, and duplicate events during connector timeouts. The fictional plan assumes Engineering, Database, DevOps, Security, QA, Product, Customer Success, and BookEasy reviewers are available during their assigned work windows. The Project Manager confirms capacity with the Engineering Manager and functional leads during week 1. No specific budget is claimed.
Authority and approval
The project manager coordinates the plan and escalates changes and risks. Technical leads own their designs and validation. The CTO approves scope changes and the production go/no-go decision. In this fictional case, the sponsor approves the charter at the end of week 1 on January 12, 2026.