Single prioritized backlog for the whole program — both teams pull from it, D. Ashworth (Product Owner) owns prioritization; C. Tyrrell (Agile Delivery Lead) owns cross-team sequencing.
Six Epics map directly to the Vision & Roadmap's Now/Next scope. Story points use a Fibonacci-like scale
(1, 2, 3, 5, 8, 13); points shown are the team's actual sprint-planning estimate, not a target.
Note: the 34 stories below are the representative product-facing backlog — the program's full delivered
scope (342 points, see Release Burnup) also
includes additional technical/infrastructure stories (API scaffolding, defect-triage batches, release
hardening) that aren't customer-facing features and so aren't itemized here.
For how these epics and stories trace through to delivery — Vision → Epic → Story →
Definition of Done → Sprint/Release — see the Requirements Traceability (Agile) view.
Epics6
Stories shown34
Total points (shown)241
Release 1 cutoffSprint 5
Release 2 cutoffSprint 8
Must Have
Should Have
Could Have
FalconMobile App team
AnchorPlatform/Integration team
BothJoint dependency
EPIC-1
Patient Identity & Onboarding
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-101 | As a new patient, I can create an account with email or phone verification | Must | 5 | 1 |
| MCM-102 | As a patient, I can log in with biometric (Face/Touch ID) after initial setup | Should | 3 | 1 |
| MCM-103 | As a patient, I can link my existing ACME Health record via a secure identity match | Must | 8 | 1 |
| MCM-104 | As a patient, I can set up and manage my profile (contact info, insurance, emergency contact) | Must | 5 | 1 |
| MCM-105 | As a patient, I can reset my password via a secure self-service flow | Should | 3 | 2 |
| MCM-106 | As a patient, I receive a guided first-run tutorial on first login | Could | 2 | 2 |
EPIC-2
Appointment Scheduling & Reminders
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-110 | As a patient, I can search for an available appointment by provider or specialty | Must | 8 | 2 |
| MCM-111 | As a patient, I can book, reschedule, or cancel a telehealth appointment | Must | 8 | 2 |
| MCM-112 | As a patient, I receive a push notification reminder 24 hrs and 15 min before my visit | Must | 5 | 2 |
| MCM-113 | As a patient, I can add my appointment to my phone's native calendar | Could | 2 | 3 |
| MCM-114 | As a patient, I can complete a pre-visit intake questionnaire before my appointment | Should | 5 | 3 |
EPIC-3
Video Visit Experience
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-120 | As a patient, I can join a video visit with one tap from my appointment card | Must | 8 | 3 |
| MCM-121 | As a platform, integrate the HIPAA-compliant video SDK with call-quality fallback to audio-only | Must | 13 | 3 |
| MCM-122 | As a patient, I see a "waiting room" state with estimated wait until my provider joins | Should | 3 | 4 |
| MCM-123 | As a provider, I can screen-share lab results or images during a video visit | Should | 5 | 4 |
| MCM-124 | As a platform, log and encrypt session metadata for HIPAA audit requirements | Must | 8 | 4 |
| MCM-125 | As a patient, if my connection drops, I can rejoin the same visit within a 5-minute grace window | Must | 5 | 5 |
EPIC-4
Provider Console
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-130 | As a provider, I can see my full daily schedule across all telehealth appointments in one view | Must | 8 | 3 |
| MCM-131 | As a provider, I can launch a visit directly from the schedule without switching systems | Must | 5 | 4 |
| MCM-132 | As a provider, I can view a patient's intake questionnaire before the visit starts | Should | 5 | 4 |
| MCM-133 | As a provider, my visit notes push directly into the ACME EHR without re-entry | Must | 13 | 6 |
| MCM-134 | As a provider, I can flag a patient case for follow-up or referral from the console | Could | 3 | 6 |
EPIC-5
Patient Data Migration & Legacy Decommission
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-140 | As a platform, build the migration pipeline and field-mapping from CareLink Classic's schema | Must | 13 | 1 |
| MCM-141 | As a platform, migrate active-patient records with automated validation and a spot-check report | Must | 13 | 4 |
| MCM-142 | As compliance, I can review a pre-cutover data-integrity validation report before go-live | Must | 5 | 4 |
| MCM-143 | As a platform, migrate full historical records (inactive patients, visit history archive) | Must | 13 | 7 |
| MCM-144 | As IT operations, decommission CareLink Classic infrastructure after cutover verification | Must | 8 | 8 |
| MCM-145 | As compliance, retain a read-only archival export of CareLink Classic per records-retention policy | Must | 5 | 8 |
EPIC-6
Messaging & Prescription Refills
| ID | Story | Priority | Pts | Sprint |
|---|---|---|---|---|
| MCM-150 | As a patient, I can send a secure message to my care team from the app | Must | 8 | 6 |
| MCM-151 | As a provider, I can respond to patient messages from the console with a templated-reply option | Should | 5 | 6 |
| MCM-152 | As a patient, I can request a prescription refill from my medication list | Must | 8 | 7 |
| MCM-153 | As a provider, I receive refill requests routed into my existing e-prescribing workflow | Must | 8 | 7 |
| MCM-154 | As a patient, I get push notification status updates on my refill request | Could | 2 | 7 |