← Back to case study
Fictional case study · Document 04 · Week 1; updated during delivery
Stakeholder Register and Communication Plan
The PM identifies the people involved and agrees how each group will receive project updates.
Illustrative project record. AegisShield, BookEasy, the people, decisions and outcomes are fictional.
Purpose
The PM maintains this fictional register from project initiation through closure. Roles are used instead of names; the register and communication cadence are updated when responsibilities or project needs change.
Stakeholder register
| Stakeholder | Interest and role | Key involvement |
|---|---|---|
| CTO / project sponsor | Business outcomes, customer continuity and delivery risk | Authorizes the project, significant schedule changes and production go/no-go |
| Project manager | Delivery coordination, risks and visibility | Maintains the plan, coordinates decisions and escalates blockers |
| Engineering lead and backend engineer | Technical compatibility and connector reliability | Define the design and implement runtime and connector changes |
| Database engineer | Data integrity and recoverability | Plans the database migration and validates restoration |
| DevOps / SRE | Service availability and operational readiness | Owns deployment, monitoring and the operational rollback procedure |
| Security engineer | Authentication and security controls | Reviews the design, security findings and release evidence |
| QA engineer | Product behavior and test coverage | Plans and executes tests and validates defect fixes |
| Customer Success and BookEasy representative | Pilot coordination and customer impact | Coordinate customer communication and validate agreed pilot scenarios |
Communication plan
| Audience | Information and channel | When |
|---|---|---|
| Sponsor | Written status, decisions and escalations | Weekly and at decision gates |
| Delivery team | Working meeting: progress, dependencies and blockers | Twice weekly |
| BookEasy and Customer Success | Pilot preparation, expected impact and results | Weekly during pilot preparation and execution |
| Security, QA and operations | Design, test evidence and release readiness reviews | At agreed review gates |
Escalation
The PM alerts the sponsor promptly when a material schedule or scope change needs a decision. Technical owners raise security, data integrity and service-continuity risks as soon as they are identified.