Purpose
This charter is the agreement both delivery teams operate under for the life of the MedConnect Mobile program. It's referenced at every Sprint Retrospective and revised by team consensus — not imposed top-down — when something isn't working.
01Team Roster & Roles
Product Owner & Agile Delivery Lead
C. Tyrrell
Program-level — owns the single prioritized backlog both teams pull from, facilitates Scrum-of-Scrums, is the program's voice to the Steering Committee
Scrum Master
J. Marsh
Team Falcon (Mobile App)
Scrum Master
R. Okafor
Team Anchor (Platform & Integration)
Engineering Lead
D. Whitfield
Team Falcon — iOS/Android native app
Engineering Lead
A. Singh
Team Anchor — APIs, EHR integration, data migration, provider console
Executive Sponsor
M. Delacroix
VP, Digital Health — ACME Health
Clinical Stakeholder
Dr. L. Nguyen
Chief Medical Information Officer — clinical workflow & patient-safety sign-off
Compliance & Security
T. Brannigan
Director, Information Security & Compliance — HIPAA review gate
02Ceremony Cadence
| Ceremony | Frequency | Length | Who |
|---|---|---|---|
| Daily Standup | Daily | 15 min | Each team, separately — Falcon and Anchor run their own |
| Scrum-of-Scrums | 2x/week | 15 min | C. Tyrrell + both Scrum Masters + both Engineering Leads — cross-team dependencies only |
| Backlog Refinement | Weekly (mid-sprint) | 60 min | PO + both teams |
| Sprint Planning | Day 1 of each sprint | 90 min | PO + each team, separately |
| Sprint Review / Demo | Last day of each sprint | 45 min | Both teams + PO + invited stakeholders |
| Sprint Retrospective | Last day of each sprint (after Review) | 45 min | Each team, separately — team-only, psychologically safe space |
| Steering Committee Update | Monthly (~every 2 sprints) | 30 min | C. Tyrrell + Sponsor + Clinical + Compliance stakeholders |
03Working Norms
Story & Board Discipline
- WIP limit: no more than 2 stories "In Progress" per developer at a time
- No story enters a sprint without meeting the Definition of Ready
- Every story must reference its parent Epic/Feature for traceability
Cross-Team Dependencies
- Any story that blocks or is blocked by the other team gets flagged at Scrum-of-Scrums the same day it's identified — not held for the next scheduled sync
- Cross-team dependencies are tracked as a labeled category on the shared board (see Backlog & Board section)
Stop-the-Line for Patient-Safety Defects
- Any defect with potential patient-safety or PHI-exposure impact is raised immediately to C. Tyrrell and T. Brannigan — does not wait for standup
- Release does not proceed with an open P1 clinical or security defect, regardless of sprint schedule pressure
Communication
- Core collaboration hours: 9:00–3:00 CT, both teams co-located in the same time zone for this program
- Async updates go in the team's channel; anything needing a same-day decision gets a direct ping, not left buried in a thread
04Escalation Path
Used when a blocker can't be resolved at the team or Scrum-of-Scrums level.
Step 1Team Scrum Master attempts resolution within the team
→
Step 2Raised at Scrum-of-Scrums for cross-team blockers
→
Step 3C. Tyrrell escalates to Sponsor/Clinical/Compliance as needed
→
Step 4Steering Committee decision, if it affects scope, budget, or timeline