The closest thing an Agile program has to a traditional project-plan Gantt chart — a high-level, rolling view of sprints, epics, and release milestones, without pretending to know the day-by-day detail that a PMBOK WBS would claim months in advance.
Why this looks different from the Enrollment & Claims WBS/Gantt Console:
that program planned 315 detailed line items up front because its scope was fixed at baseline. This program's
detailed plan only ever existed one or two sprints ahead (see Sprint Backlogs) — this schedule is the rolled-up,
after-the-fact picture of how those sprints landed against the Epics, useful for exactly the kind of retrospective
or stakeholder-facing view a Gantt chart would normally provide, without overstating how far in advance any of it
was actually known.
Epic-Level Schedule
| Epic / Phase | Sprint 0 | S1 | S2 | S3 | S4 | S5 | S6 | S7 | S8 |
|---|---|---|---|---|---|---|---|---|---|
| Program Setup (Sprint 0) | |||||||||
| Epic 1 — Patient Identity & Onboarding | |||||||||
| Epic 2 — Scheduling & Reminders | |||||||||
| Epic 3 — Video Visit Experience | |||||||||
| Epic 4 — Provider Console | |||||||||
| Epic 5 — Data Migration & Decommission | |||||||||
| Epic 6 — Messaging & Refills | |||||||||
| 🟢 Release Milestones |