Who needs what, how often, and in what format — set at Program Kickoff and held for the life of the program. Ceremony-based communication (standups, reviews) is covered in the Team Charter; this plan covers everything above the team level.
| Stakeholder | Information Need | Frequency | Format | Owner |
|---|---|---|---|---|
| M. Delacroix (Sponsor) | Overall program health, budget, release readiness, go/no-go decisions | Monthly (~every 2 sprints) | Steering Committee Deck | C. Tyrrell |
| Dr. L. Nguyen (CMIO) | Clinical workflow changes, patient-safety-relevant stories, sign-off requests | Per-story (as triggered) + Sprint Review attendance | Direct sign-off request + Sprint Review demo | C. Tyrrell / Scrum Masters |
| T. Brannigan (Compliance) | PHI-handling stories, migration validation reports, pre-cutover sign-off | Per-story (as triggered) + pre-release checkpoints | Direct review request + Sprint Review demo | C. Tyrrell / Engineering Leads |
| Pilot provider cohort | What's changing, when, and how to give feedback | Ad hoc, concentrated around Release 1/2 | Sprint Review invite + release notes | C. Tyrrell |
| Both delivery teams (Falcon & Anchor) | Day-to-day coordination, cross-team dependencies, blockers | Daily (standup) + 2x/week (Scrum-of-Scrums) | Ceremony (verbal, logged) | Scrum Masters / C. Tyrrell |
| ACME Health IT Operations | Infrastructure scaling needs, CareLink Classic decommission timing | Ad hoc, concentrated in Sprints 5 and 8 | Direct coordination + Sprint Status Report | A. Singh (Engineering Lead, Anchor) |
| App Store / Play Store review teams | Release build submissions | Per-release (Sprint 5 and Sprint 8) | Formal submission via developer portal | D. Whitfield (Engineering Lead, Falcon) |