What was needed
Modernize selected SIEM components and improve BookEasy's event delivery without disrupting the existing service.
Back to portfolio
Junior Technical Project Manager · Fictional case study
Aegis Security Cloud Modernization
A fictional implementation project to modernize AegisShield's security monitoring service and pilot the changes with BookEasy.
PM contribution
Turned an incomplete sponsor request into a scoped pilot, coordinated risks and dependencies, and managed a one-week delay caused by duplicate events.
Methodology
Hybrid: a clear plan for scope, risks, approvals, and dates, with small build-and-test steps for the technical work.
Illustrative outcome
The fictional BookEasy pilot was accepted and the increment released; project closure moved from week 12 to week 13.
View and print all project documents (PDF)
21 curated project documents in one printable file, with document and spreadsheet-style tables.
Project timeline and documents
From handoff to project closure
Follow the fictional implementation in order. Each document records what the team planned, decided or delivered.
Phase 1
Initiation
- 01Before week 1
Sponsor Handoff and Scenario
The sponsor hands the PM the proposed pilot boundaries and assessment findings for the BookEasy increment.
Details - 02Week 1
Project Brief
The PM summarizes the business need, target state, and proposed BookEasy pilot scope.
Details - 03Week 1
Project Charter
The sponsor authorizes the project, its boundaries, responsibilities and success criteria.
Details - 04Week 1; updated during delivery
Stakeholder Register and Communication Plan
The PM identifies the people involved and agrees how each group will receive project updates.
Details - 05Week 1
Kickoff Meeting Notes
The project team confirms the objective, responsibilities, first actions and open questions.
Details
Phase 2
Planning
- 06Weeks 1–2
Implementation Requirements
The team agrees what the modernization must accomplish and how each requirement will be checked.
Details - 07Weeks 1–2
Technical Approach and Delivery Plan
Technical leads define the target, migration sequence and release safeguards.
Details - 08Week 2 baseline
Work Breakdown Structure
The approved project scope is organized into deliverables and manageable work packages.
Details - 09Week 2
RACI and Team Responsibilities
The team agrees who carries out, owns, advises on and receives updates about each deliverable.
Details - 10Week 2 baseline
Technical Backlog
The work packages become prioritized tasks with owners, dependencies and acceptance evidence.
Details - 11Week 2 baseline
Project Schedule
The team maps the initial twelve-week milestones and their dependencies.
Details - 12Week 2 baseline; reviewed weekly
Risk Register
The team records what could threaten delivery and assigns owners to reduce or manage each risk.
Details - 13Weeks 2–4; used through release
Test, Migration and Rollback Plan
Technical owners define how the team will verify the changes, rehearse the migration and recover if the release fails.
Details
Phase 3
Execution
- 14End of week 8
Project Status Report
The PM reports progress, the test defect and the forecast impact before the sponsor decides.
Details - 15Week 8; resolved in week 10
Issue Log
The team tracks the duplicate-event defect, its owner, actions and resolution.
Details - 16Week 9
Schedule Change Request and Decision
The PM requests a one-week change after ISS-01, and the sponsor records the decision and follow-up actions.
Details
Phase 4
Validation and release
- 17Weeks 8–10
Test Results
QA records the agreed test outcomes and the retest of the duplicate-event defect.
Details - 18Week 11
BookEasy Pilot Review and Acceptance
BookEasy reviews the agreed pilot scenarios and records its acceptance before release.
Details - 19Week 12
Go/No-Go Decision and Release Record
The sponsor reviews readiness, authorizes the controlled release, and the team records the execution result.
Details - 20Week 13
Operations Handover
The delivery team transfers the service, recovery procedures and support responsibilities to operations.
Details - 21Week 13
Project Closure and Lessons Learned
The sponsor accepts the project outcome and the PM records results, the delay and lessons learned.
Details
GitHub Projects
The board in three moments
The case has a separate public repository and three linked GitHub Projects boards: planning, the issue in execution, and close-out.
About this case
This is a fictional educational case. Companies, participants, decisions, timeline and outcomes are simulated. The web pages and combined PDF present the same illustrative project records; they do not represent a real client engagement or production deployment.