Kickoff Deck · Portfolio Demo

MedConnect Mobile

Download PowerPoint
Program Kickoff · Sprint 0, Day 1

MedConnect Mobile

Two teams. Eight sprints. One telehealth platform patients will actually want to use. Here's how we get there.
January 5, 2026Kickoff Date
C. TyrrellProduct Owner & Agile Delivery Lead
13Team Members
1
Agenda

What We'll Cover Today

1
Welcome & Program Context
2
Why This Program Matters
3
Success Metrics & OKRs
4
Scope: In and Out
5
Teams & Delivery Model
6
Sprint Timeline & Releases
7
Budget Overview
8
How We'll Work Together
9
Risks We're Watching
10
Next Steps & Q&A
2
Welcome

Glad You're Here

Thirteen people across two teams become one Scrum-of-Scrums today — and Sprint 1 starts in two weeks.

Over the next 18 weeks, Team Falcon (Mobile) and Team Anchor (Platform) will replace CareLink Classic with a native patient app, a provider web console, and a clean historical data migration — coordinated through a lightweight Scrum-of-Scrums, not a heavyweight SAFe model. Quick round of introductions: name, team, and what you're most excited (or nervous) about.

13
Named Team Members
8
Sprints to Full Cutover
2
Coordinating Teams
3
The Business Case

Why We're Doing This

CareLink Classic's vendor end-of-support date is fixed — there's no mobile roadmap coming, and no extension available.

The current telehealth platform has an announced end-of-support date 18 months out, no mobile roadmap ever delivered, and renewal pricing that rose 34% at last cycle. This program replaces it with a native mobile app and provider console — full detail lives in the Program Charter and Cost-Benefit Analysis.

$1.85M
Approved Budget
May '26
Target Full Cutover
4
Success Metrics

What Success Looks Like

1
60% of visits booked via mobile app within 60 days of Release 1
2
Login-to-visit-start time cut from ~6 min to under 2 min
3
Telehealth support tickets down from ~410/mo to under 150/mo
4
100% of active patient records migrated, zero critical data-integrity defects
5
≥85% of scheduled providers using the console daily by week 4 post-launch

Full OKR detail and release roadmap: Vision & Roadmap

5
Scope

Where the Lines Are

In Scope

  • Patient mobile app (iOS/Android) and provider web console
  • Video visit integration (PulseConnect SDK)
  • Full patient-record migration; CareLink Classic decommission
  • Secure messaging and prescription refill requests

Out of Scope (Candidate Backlog)

  • Remote patient monitoring device integration
  • Multi-language patient app support
  • Group/family visit scheduling
  • Provider analytics dashboard
6
Teams

Everyone Who's Building This

C. Tyrrell
Product Owner & Agile Delivery Lead
J. Marsh
Scrum Master, Team Falcon
R. Okafor
Scrum Master, Team Anchor

Team Falcon — Mobile 5 FTE

D. WhitfieldEngineering Lead
K. AlvareziOS Developer
S. ParkAndroid Developer
T. NguyenBackend Developer
E. MarchettiQA Lead — Falcon

Team Anchor — Platform 5 FTE

A. SinghEngineering Lead
R. KimBackend Developer
N. OseiQA Lead (Onshore)
M. ChenOffshore QA Analyst
P. KumarOffshore QA Analyst

All 13, same as the Resource Plan and Org Chart — nobody on this program is a name you'll only find in a spreadsheet: Resource Plan · Org Chart

7
Timeline

Eight Sprints to Full Cutover

Sprint 0
Kickoff
Jan 5
Sprint 2
Scheduling Core
Feb 2
Sprint 5
Release 1 (MVP)
Mar 27
Sprint 7
Full Data Migration
Apr 24
Sprint 8
Release 2 (Full Cutover)
May 8
Program
Closeout
May 15

Full sprint-by-sprint schedule: Release Schedule

8
Budget

Where the Money Goes

$1.85M
APPROVED BUDGET
Team Labor (Falcon + Anchor)
PO + Scrum Masters
Vendor/Infrastructure
Contingency Reserve

A 10% contingency reserve is built in from day one — drawn only through a formal Change Request, not spent by default.

Full detail and the 13-person rate card: Program Budget

9
Working Together

How We'll Stay in Sync

CadenceForumPurpose
DailyTeam StandupDay-to-day coordination, blockers
2x/weekScrum-of-ScrumsCross-team dependency sync
Per sprintSprint Review + RetrospectiveStakeholder demo/feedback; team-only improvement
MonthlySteering CommitteeFormal program-health review

Full governance model, decision rights, and escalation path: Program Governance Model

10
Eyes Open

Risks We're Watching From Day One

!
Data-quality issues in legacy archive records could complicate historical migration
Highest-attention risk heading into Sprint 7
!
Third-party video SDK vendor configuration/entitlement gaps
Could affect the visit experience if not caught in spike/refinement
!
Cross-team dependencies could surface late without disciplined tracking
Why Scrum-of-Scrums runs twice a week, not once

Full risk register: Agile RAIDD Log

11
Next Steps

What Happens Next

1
Sprint 0 continues through Jan 16 — environment setup, tooling access, backlog seeding
2
First Backlog Refinement session on Jan 8
3
Sprint 1 Planning on Jan 19 — Auth & onboarding work begins
12

Let's Ship Something Patients Will Actually Use.

C. Tyrrell, Product Owner & Agile Delivery Lead
MedConnect Mobile
13