Program Governance Model — MedConnect Mobile

1. Purpose & Governance Principles

This document defines who has authority to decide, and how exceptions get resolved, on the MedConnect Mobile program — distinct from the Team Charter, which describes how the teams work day to day. It's deliberately lighter than a PMBOK-style governance model, sized to a two-team, 18-week program rather than a multi-year enterprise platform build.

Transparency — decisions and rationale are visible in the RAIDD Log and Change Control Log, not made informally.

Fast, proportionate escalation — most decisions are made at the team or Product Owner level; only baseline-impacting changes go further.

Clinical and compliance authority is never overridden by schedule pressure — see Section 9.

2. Governance Structure

See the Organizational Chart for the full reporting structure. In summary: Executive Sponsor (M. Delacroix) → Product Owner & Agile Delivery Lead (C. Tyrrell) → two Scrum teams, with matrixed advisory lines to Clinical (Dr. Nguyen) and Compliance (T. Brannigan).

3. Decision Rights

Full activity-by-activity assignment is in the Agile RACI. Summary tiers:

Tier	Decision Type	Authority
1	Backlog prioritization, re-estimation, story splits within approved scope	Product Owner (C. Tyrrell)
2	Cost, schedule, or scope-boundary change to the approved baseline	Executive Sponsor (via formal Change Request)
3	Clinical workflow or PHI/compliance exception	CMIO / Compliance Director (see Section 9)

4. Escalation Process

Team Scrum Master attempts resolution within the team → raised at Scrum-of-Scrums for cross-team blockers → Product Owner escalates to Sponsor/Clinical/Compliance as needed → Sponsor decision if scope, budget, or timeline is affected. Full detail in the Agile Team Charter.

5. Meeting Cadence & Reporting

Cadence	Forum	Purpose
Daily	Team Standup	Day-to-day coordination, blockers
2x/week	Scrum-of-Scrums	Cross-team dependency sync
Per sprint	Sprint Review + Retrospective	Stakeholder demo/feedback; team-only improvement
Monthly	Steering Committee	Formal program-health review using the Steering Committee Deck

6. Change Control Governance

All formal changes to the budget or schedule baseline are evaluated and logged on the Change Control Log. Backlog reprioritization within approved scope does not require this process — see Change Handling in Agile for exactly where that line sits.

7. Vendor Governance

Two vendors, two governance models: PulseConnect (active, ongoing SLA management, technical POC A. Singh) and Vantix Health Systems (outgoing, checklist-driven offboarding, compliance-owned deletion certification). Any vendor contract change with cost impact requires Sponsor approval — see CR-01 on the Change Control Log for a worked example. Full detail in the Vendor Management Plan.

8. Release Gates

Rather than PMBOK-style phase gates, this program uses two release gates, each requiring a formal Go/No-Go decision at Sprint Review:

Gate	Go/No-Go Criteria	Approval
Release 1 (MVP)	All Release 1 acceptance criteria met; zero open P1/P2 defects; Compliance and Clinical sign-off obtained	Executive Sponsor
Release 2 (Cutover)	Full historical migration validated; CareLink Classic decommission-ready; Compliance sign-off obtained	Executive Sponsor

9. Compliance & Clinical Oversight

Compliance & Clinical Veto Authority

Any story touching PHI or a clinical workflow cannot be marked Done, and no release can go live, without sign-off from T. Brannigan (Compliance) and, for clinical-workflow changes, Dr. L. Nguyen (CMIO) — regardless of sprint schedule pressure. This is a standing exception to the normal Product Owner decision rights in Section 3, established at Program Kickoff and enforced via the Definition of Done.

10. Performance Monitoring

Program health is monitored via the Velocity Chart, Release Burnup, and reported monthly through the Steering Committee Deck. Key thresholds: predictability (delivered/committed) at or above 90%; zero open P1/P2 defects at any release gate; budget variance managed within the approved Contingency Reserve.

11. Approval

This governance model is approved for use across the MedConnect Mobile program.

M. Delacroix, Executive Sponsor

C. Tyrrell, Product Owner & Agile Delivery Lead