Back to case study

Fictional product and launch case · Document 05

Project Charter

The CTO authorizes the product-definition and technical-validation stage and sets its limits.

AegisShield Web Application Firewall · Stage authorization

AegisShield, BookEasy, the people, findings and decisions are fictional and created for portfolio demonstration.

Authorization

The CTO authorizes the Project Manager to coordinate a limited product-definition and technical-validation stage for the AegisShield Firewall. This authorization does not approve production protection or a broad product launch.

Approved boundary

The team may define and validate the AegisShield Firewall for one BookEasy web application. It may assess an existing security engine, create a visual prototype, define rules and exceptions, estimate resources and costs, and prepare pilot controls.

The team may not deploy production protection, roll out to other customers, build a proprietary engine or redesign the existing SIEM.

Authority and ownership

RoleAccountability
CTO / sponsorApproves scope, budget boundary, major risks and pilot-build authorization
ProductOwns customer value, first-release priorities and acceptance scenarios
EngineeringOwns feasibility, engine evaluation, estimates and implementation options
SecurityOwns controls, data protection and rule-safety review
OperationsOwns monitoring, support, recovery and handover requirements
Project ManagerCoordinates the plan, decisions, risks and escalations

Initial milestones

MilestoneTarget
Charter and first-release scope approvedWeek 2
Prototype and requirements reviewedWeek 4
Technical and cost options assessedWeek 5
Pilot test plan and controls readyWeek 7
Sponsor decision on pilot buildWeek 8

Success criteria

The stage succeeds when the sponsor receives a clear scope, evidence of a real customer problem, a feasible technical path, a safe test approach, an initial cost and schedule view, and a recommendation with conditions.

Have a project that needs to get done?

Contact me