Skip to content

Roadmap & Milestones, Personal Training OS

Artifact: 1.3 (Phase 1, Planning) · Owner: Delivery Manager (Primary User) Version: v1.3 · Date: 2026-07-09

A roadmap communicates what by when at a high level. Two views below: the gate schedule (governance milestones) and a Now / Next / Later capability view (mapped to MoSCoW). Forcing function: go-live before race week (24 Jul).

Amendment (v1.3, 2026-07-09): as-built update. Gates G0-G7 passed; v1.0 went live 2026-07-05 (19 days ahead of the race-week forcing function) and the project was formally closed 2026-07-09 (G7: retrospective, benefits realization, and post-implementation review complete, under pm/07-closure/). Increments 2 (Garmin activities + wellness metrics, Withings weight) and 3 (hockey auto-schedule) shipped post-release and are live (operational evidence only; formal V&V of Increments 2 to 4 carried as a post-closure follow-up). Strava is scaffolded but blocked on a paid subscription.

Milestone / gate schedule

Gate Milestone Target Status
G0 Charter approved 2026-07-03 ✅ Passed
G1 Delivery plan baselined 2026-07-05 ✅ Passed
G2 Requirements baselined (+ NFRs, personas) 2026-07-06 ✅ Passed
G3 Design reviewed (coverage 100%) 2026-07-07 ✅ Passed (101/101 req to design coverage)
G4 Build complete, MVP in Notion 2026-07-20 ✅ Passed (16 DBs live 2026-07-05, well ahead of target)
G5 Verification & UAT accepted 2026-07-23 ✅ Passed (20/20 tests, 7/7 UAT, 0 open defects, 2026-07-05)
G6 Go-live (usable for race week) 2026-07-24 Passed (live 2026-07-05, 19 days early)
G7 Closure / retrospective 2026-08-01 ✅ Passed (closed 2026-07-09, ahead of target)

Timeline (Jul to Aug 2026)

Jul 03 ─ G0 ✅ Charter
Jul 04 ─ Planning (RAID, MoSCoW, Roadmap) ✅
Jul 05 ─ G1 ✅ Plan baselined
Jul 05 ─ G2 ✅ Requirements (NFRs + personas) baselined
Jul 05 ─ G3 ✅ Design reviewed (coverage 100%)
Jul 05 ─ G4 ✅ BUILD complete (Notion, 16 DBs)  [connector verified ✓]
Jul 05 ─ G5 ✅ Verification + UAT accepted (20/20, 7/7)
Jul 05 ─ G6 ★ GO-LIVE (v1.0, 19 days ahead of race week)
Jul 05 ─ Increments 2a-2c + 3 shipped (Garmin activities + wellness, Withings weight, hockey auto-schedule); live daily
Jul 25 to 26 ─ Example 5K / Example Half Marathon  (system in real use)
Jul 09 ─ G7 ✅ Closure / retro (project formally closed, ahead of the Aug 01 target)

Now / Next / Later (capability view, mapped to MoSCoW)

Horizon Capabilities
Now (v1 / by go-live) MoSCoW Must: 15 DBs + structure, People (Primary User+Secondary User), Training Sessions, Races+seeds, Shoes+mileage, Routes, Hockey attendance logic, Dashboard core views, Calendar import
Delivered post-v1 (shipped) Increment 2a: Garmin activities to Training Sessions. Increment 2b: Garmin daily wellness metrics to Metrics/Check-ins. Increment 2c: Withings weight to Metrics/Check-ins. Increment 3: hockey games auto-scheduled into Training Sessions + attended-skate linking. All live, daily 06:00 (operational evidence only; formal V&V outstanding).
Next (fast-follow, weeks after go-live) MoSCoW Should: Metrics, Nutrition, Goals, Training Blocks, Weekly Reviews, Exercise Library/Templates + first training-plan materials
Later (post-v1, gated) Strava live sync (scaffolded, blocked on a paid subscription), MyFitnessPal nutrition, Apple Health, Calendar sync, RAG/insights, users beyond the two primary, other life domains

Critical path & key risk

Build (G4), Verification (G5), and Release (G6) are complete (v1.0 live 2026-07-05). The Notion connector was verified available on 2026-07-04 (workspace "Almond Street Notion"), closing issue I1 and dependency D1, so Build ran unblocked. R8 is retired: the hockey-counts and shoe-mileage logic shipped and was validated in Build (hockey counts + shoe mileage live in the 20/20 test run). G7 closure is now complete (retrospective, benefits realization, and post-implementation review delivered under pm/07-closure/; project formally closed 2026-07-09), with two items carried forward as post-closure follow-ups: the tracked work to bring Increments 2a-2c and 3 under the formal V&V suite (they are live today on operational evidence only), and the SC1 adoption measurement (post-race-week, monitored via RAID R1).