Fictional case study · Document 01 · Before week 1
Sponsor Handoff and Scenario
The sponsor hands the PM the proposed pilot boundaries and assessment findings for the BookEasy increment.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Business context
AegisShield is a fictional provider of a cloud security monitoring service (SIEM). Its customer BookEasy runs a scheduling application for businesses. BookEasy sends security events to AegisShield; AegisShield's security analysts investigate the alerts.
Following a leadership change, the CTO commissioned an assessment. The findings and a phased modernization direction are handed to the project team as inputs; the assessment happened before this implementation project.
Assessment handoff
| Area | Finding supplied to the project |
|---|---|
| Runtime and dependencies | Node.js 14 and PostgreSQL 12 are out of community support; Express, Passport and Axios require compatibility and security review. |
| BookEasy connector | Retry behavior needs stronger duplicate protection, and delivery failures are not sufficiently visible. |
| Operations | Release, restore and monitoring procedures are incomplete; existing detections and dashboard must continue to work. |
Sponsor request
Deliver a controlled first modernization increment for BookEasy. Move selected runtime and database components toward supported versions, improve retry and duplicate handling, make delivery failures visible, and preserve existing login, event ingestion, alerts, and dashboard behavior. Preserve service continuity, protect customer data, and secure approval before production. The initial planning assumption is 12 weeks; capacity and acceptance criteria are confirmed with the delivery team, sponsor, and BookEasy.