Shopware Migration

Appearance

Executive Summary ​

  • SXSW platform hits 64%: +18 completions (580/909) with only +2 scope growth—velocity down to 2.6 stories/day from prior 7.3, suggesting post-sprint cooldown or resource constraints
  • CESW board stabilizes at 67%: +46 completions (450/674) with +51 scope—tracking volatility persists but real delivery evident (Blake: 68 commits, Emil: 90, Scott: 27)
  • ARROW Frontend explodes +101 scope: 380→436 complete but 426→527 total—massive board consolidation event, real work visible in 65 commits across boilerplate repos
  • Review pipeline aging worsens: 13 stale tickets persist >30 days with max age hitting 106 days (SXSW-391)—chronic cases now 2+ weeks older, review capacity crisis deepening
  • Data migration remains frozen: Still only 1 of 42 categories Done (Peirce Customers), 6 BUs stuck at "WIP" with zero movement—3 weeks to production and no progress since July 7
SXSW  [███████████████░░░░░░░░░] 64% (580/909)
ARROW [████████████████████░░░░] 83% (436/527) [Frontend]
ARROW [█████████████████████░░░] 85% (90/106)  [Infra]
CESW  [████████████████░░░░░░░░] 67% (450/674)
W1DA  [████████████████░░░░░░░░] 64% (124/195)
ECMD  [██░░░░░░░░░░░░░░░░░░░░░░] 10% (35/349)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/31)
BSWM  [██░░░░░░░░░░░░░░░░░░░░░░] 12% (28/238)

1. SXSW Platform (Core Initiatives) ​

Current State: 580/909 stories complete (64%)

Week-over-Week (vs. 2026-07-14): +18 completed, +2 scope—velocity dropped to 2.6 stories/day from prior week's 7.3/day

Analysis: SXSW shows significant velocity deceleration. The +18 completions with minimal scope growth is healthy signal-to-noise, but absolute velocity dropped 64% week-over-week. This suggests either:

  1. Team capacity shift (resources moved to BU work)
  2. Technical complexity increase (remaining stories harder)
  3. Natural sprint cooldown after prior week's +51 push

By Initiative (deltas vs. last week):

  • Infrastructure & Architecture: 105/229 (46%)—+5 stories, still foundation gap
  • Authentication: 33/34 (97%)—unchanged for 4+ weeks, 1 story stuck
  • Catalog & Product: 61/81 (75%)—+2 stories
  • Cart & Checkout: 85/143 (59%)—+1 story
  • Account Management: 91/133 (68%)—+1 story
  • Integrations: 88/118 (75%)—+1 story
  • Specialized Features: 41/71 (58%)—unchanged
  • Branch Management: 37/41 (90%)—unchanged
  • Content Management: 6/21 (29%)—+2 stories
  • Data Migration: 10/24 (42%)—+1 story

Repository Activity (2026-07-14 to 2026-07-21):

  • ecommerce-supergraph: 138 commits (Paul Briscoe: 58, Adrian Pescar: 9, Gabriel Guzmán: 13)
  • Key work: Branch resolution (Paul), Offers API refactor (Adrian: SXSW-1160-1162), Product pricing (Paul)

Key Observations:

  • Infrastructure +5 stories but still at 46%—foundational work advancing slowly
  • Content Management finally moving—+2 stories to 29%, but still lowest completion %
  • All other initiatives stalled at <+2 stories—suggests focused push on 2-3 areas rather than broad front

Velocity Projection: At 2.6 stories/day, remaining 329 stories will complete in 126 days (late November 2026). This is 3x longer than prior projection and suggests either:

  1. Velocity will recover (likely)—prior week's 7.3/day was sprint push, this week is cooldown
  2. OR scope will compress—remaining stories will be deprioritized/closed as not required

Risk Assessment: MEDIUM-HIGH. Velocity deceleration is concerning but:

  • +18 completions with +2 scope is clean burn (no requirements churn)
  • Repository shows 138 commits (strong technical velocity)
  • Likely sprint boundary artifact rather than systemic slowdown

Recommendation: Monitor next week. If velocity stays ❤️ stories/day for 2 weeks, escalate as resourcing issue.

2. ARROW - Frontend / Open Components ​

Current State: 436/527 stories complete (83%)

Week-over-Week (vs. 2026-07-14): +56 completed, +101 scope—massive board consolidation event

Analysis: ARROW Frontend shows classic board explosion pattern: +56 completions looks good until you see +101 scope added. The net effect is completion % dropped from 89% to 83%. This represents bulk import of Open Components backlog that was tracked elsewhere.

Repository Activity (65 commits across 4 frontend repos):

  • watsco-frontend-boilerplate: 30 commits (Pablo Romero: 20, Lino Rallo: 30, Gabriel: 19)
  • baker-headless: 20 commits (Pablo Romero: 5, Tyler Hawkins: 29)
  • peirce-frontend: 13 commits (Pablo Romero: 3)
  • homans-next-frontend: 13 commits (Pablo Romero: 3, Lino: 13)

Work Completed (from commits):

  • Boilerplate v1.3.0 shipped (Pablo: ARROW-2640-2646)—Turborepo upgrade, tsc typecheck in CI, product image fixes, dev workflow hooks
  • Brands page implemented (Pablo: SXSW-190)—alphabet filter, GraphQL integration, scroll spy
  • Homans frontend progressing (Lino: ARROW-2588)—deployed to Ordin, shopping list integration
  • Baker styling (Tyler: BSWM-288, 270)—header customization, useScrollVisibility hook

Active Epics (from board):

  • Open Components: 71/73 (97%)—nearly complete
  • OC - Shopping Lists: 69/71 (97%)—Lino's work landing
  • OC - Warranty Look Up: 21/23 (91%)—almost done
  • OC POC - NPM Compatibility: 45/45 (100%)—COMPLETE

Analysis of +101 Scope: The new stories appear to be Open Components work that was tracked in separate ARROW project (not ARROW Frontend). Commit patterns show real work (Boilerplate v1.3.0, Brands page, Homans deployment) so this is tracking consolidation, not phantom work.

Status: Board metrics unreliable due to consolidation. Real progress: 65 commits across 4 repos shows healthy frontend velocity.

Recommendation: Track frontend progress via:

  1. BU frontend boards (BSWM, GSHOP) for BU-specific work
  2. Repository activity for boilerplate improvements
  3. Ignore ARROW Frontend board % metrics—consolidation events make trend analysis impossible

3. ARROW - Infrastructure / Cross-cutting ​

Current State: 90/106 stories complete (85%)

Week-over-Week (vs. 2026-07-14): +3 completed, no scope change—steady but slow progress

Analysis: Arrow Infrastructure continues incremental advance. The +3 completions align with repository evidence of performance optimization and Homans environment work.

Active Epics:

  • Demo Environment Bugs: 23/28 (82%)—stuck for 4+ weeks
  • Performance Tuning: 12/18 (67%)—unchanged
  • Homans to Arrow: 10/13 (77%)—+3 stories, Lino Rallo driving

Repository Activity:

  • Lino Rallo: 83 commits across boilerplate/peirce/homans/baker—Homans deployment, shopping list updates, cart query improvements

Key Achievement: Homans frontend deployed to Ordin (ARROW-2588)—first new BU frontend to reach environment in 3+ weeks.

Concern: Demo Environment Bugs stuck at 82% for month. These are likely polish items blocking board closure.

Recommendation:

  1. Close Demo Environment Bugs as "good enough"—don't let 5 polish items block 85% completion
  2. Focus remaining effort on Homans push (77%→100% needed for go-live)

4. CESW (CE Shopware) ​

Current State: 450/674 stories complete (67%)

Week-over-Week (vs. 2026-07-14): +46 completed, +51 scope—tracking volatility persists but real work evident

Analysis: CESW continues pattern of board explosions (+51 scope) coupled with real completions (+46). The near 1:1 ratio suggests:

  1. Team is discovering new work as fast as completing old work
  2. OR board consolidation events coinciding with real delivery

Repository Activity (217 commits):

  • Blake Saunders: 68 commits (cesw + supergraph + plugins)
  • Emil Stewart: 90 commits (cesw + supergraph + plugins)
  • Scott Kovach: 27 commits (cesw + supergraph)

Work Completed (from commits):

Blake Saunders:

  • DMI subgraph complete (CESW-817, 818)—CE lists now using Domain API
  • User permissions (CESW-1140, 1186, 1192, 1193)—approval list requirements, address handling, email invitee support
  • Customer data import (CESW-1243, 1267, 1278)—M2→SW customer migration completed

Emil Stewart:

  • System Builder (CESW-118, 1054-1061, 1069)—complete Shopware plugin + graph resolvers for AHRI bundles, FBT, curb adapters
  • Similar Products (CESW-40, 1062-1069)—Algolia-backed similar product recommendations using rule engine
  • ServiceBench complete (CESW-313, 1133)—warranty integration fully shipped

Scott Kovach:

  • Co-op Claims (CESW-1072-1077)—Conduit subgraph + claim year restrictions
  • Order Approval (CESW-829)—cart approval submission flow

Active Epics (advanced/closed this week):

  • System Builder (CESW-118): 2/11→10/11—Emil shipped complete implementation
  • Similar Products (CESW-40): 1/9→9/9—Emil shipped complete implementation
  • Customer Import (CESW-1243): Closed—Blake shipped M2 export tool + import scripts
  • DMI (CESW-58): 5/17→6/25—Blake vertical slice complete, scaling up

Pipeline Health:

  • 14 in code review—healthy review throughput
  • 2 blocked—down from 6 last week
  • 39 in progress—capacity ceiling

Key Achievement: Three major epics shipped this week (System Builder, Similar Products, Customer Import)—real delivery despite board chaos.

Recommendation: Continue tracking via epic closure and commit patterns. Board metrics (67%) understate real progress—likely 75-80% based on epic analysis.

5. W1DA (Domain API) ​

Current State: 124/195 stories complete (64%)

Week-over-Week (vs. 2026-07-14): +5 completed, +24 scope—scope explosion event

Analysis: W1DA shows first board consolidation in month. The +24 scope with only +5 completions drops completion % from 70% to 64%. This represents bulk import of Domain API backlog.

Repository Activity (16 commits):

  • Robert Dumitru: 16 commits on PQ proxy + ERP account collision fixes
  • Lino Rallo: 3 commits on http-client retry logic

Work Completed:

  • PQ manifest proxy (DOMAIN-387, 391, ARROW-2562)—Robert building persisted query infrastructure
  • ERP account collision fix (DOMAIN-376, 242)—Robert resolving schema conflicts
  • HTTP client fixes (DOMAIN-285, 385)—Lino disabling retry for non-idempotent POST

Active Epics:

Analysis of +24 Scope: New tickets appear to be checkout-related work (DOMAIN-393-394: Checkout Payment/Order Placement). This represents formalizing checkout flow that was previously tracked ad-hoc.

Status: Board metrics unreliable due to consolidation. Real velocity: 16 commits/week on PQ infrastructure and schema fixes shows focused technical work.

Recommendation: Track via epic closure. Ignore board % due to consolidation.

6. ECMDSW (ECMD Shopware) ​

Current State: 35/349 stories complete (10%)

Week-over-Week (vs. 2026-07-14): +3 completed, +21 scope—minimal progress

Analysis: ECMD continues slow burn. The +3 completions with +21 scope growth shows requirements are expanding faster than delivery. At 3 completions/week, ECMD will complete in 104 weeks (May 2028).

Repository Activity (8 commits):

  • Lucian Miculescu: 8 commits (ecm-supergraph + sw-plugin-account-structure + sw-plugin-sso)
  • Sebastian Poblete: 5 commits (ecommerce-supergraph)

Work Completed:

  • Product catalog import (ECMDSW-336)—Lucian completing import scripts
  • SSO fixes (ECMDSW-336)—Lucian fixing B2B employee login bugs
  • Document list API (W1STORE-418)—Sebastian building documentList query

Active Epics:

  • Infrastructure (ECMDSW-2): 19/36 (53%)—+1 story
  • Catalog (ECMDSW-4): 9/38 (24%)—unchanged
  • Integrations (ECMDSW-8): 1/21 (5%)—+1 story

Closed This Week:

  • ECMDSW-342: Shopware backend fixes—Lucian fixed customer.wrapped_entity null handling
  • ECMDSW-339: Domain API customer call fixing—Michelle Madsen closed

Concern: 10% completion with 3 weeks to production is crisis territory. However, most of 349 stories are verification tasks against shared platform. Real ECMD-specific work is likely 50-75 stories.

Recommendation:

  1. Audit backlog THIS WEEK—identify real work vs. verification
  2. Batch-close verification tasks—if platform capability exists, close ticket
  3. Focus Lucian on critical path—customer/product migration, catalog integration, SSO

7. GSHOP (Gemaire Shopware) ​

Current State: 0/31 stories complete (0%)

Week-over-Week: No change—still 0% after 8 weeks

Repository Activity: None captured (repos timed out)

Critical Finding: 8 weeks at 0% despite known repository activity 2 weeks ago (customer import, product import scripts committed by Girish Assudani).

Analysis: This is confirmed tracking disconnect. Either:

  1. GSHOP board abandoned—work tracked in GCOMM or GSHOP2
  2. Team not updating Jira—commits happening, tickets not transitioning
  3. Gemaire migration paused—no active work since 2 weeks ago

Recommendation:

  • Immediate audit call with Gemaire team (Yovany Cancio, Nikolay Prudnikov, Girish Assudani)
  • Decision: Fix tracking or accept lag—if work is happening in separate system, stop reporting GSHOP metrics until sync

8. BSWM (Baker Shopware) ​

Current State: 28/238 stories complete (12%)

Week-over-Week (vs. 2026-07-14): +2 completed, +1 scope—minimal progress

Analysis: Baker shows same pattern as ECMD—slow burn (2 completions/week) despite known repository activity.

Repository Activity (46 commits):

  • Tyler Hawkins: 37 commits (baker-headless + boilerplate)
  • Nick Rolando: 18 commits (baker-shopware + sw-plugin-order-sync + sw-plugin-import + sw-plugin-conduit)

Work Completed:

  • Header styling (BSWM-39, 41, 47, 270)—Tyler shipping desktop top row, mobile header, footer
  • ERP order sync refactor (SXSW-1128, BSWM-282)—Nick replacing watsco_erp_order entity with order.erp_order_id
  • Product/customer import (BSWM-30, 31, 280)—Nick fixing WatscoImport bundle table errors

Active Epics:

  • Baker Headless App (BSWM-1): 21/24 (88%)—unchanged for 3+ weeks, stuck
  • Shopware Backend (BSWM-27): 4/9 (44%)—+2 stories, Nick's work landing
  • Header (BSWM-36): 3/16 (19%)—Tyler active

Key Observation: Tyler committed 37 times on header but Header epic only shows 3/16 (19%)—suggests 1-2 week tracking lag between commits and ticket closure.

Estimate of Real Progress: Based on 46 commits (header complete, ERP sync, imports), Baker is likely 25-30% complete, not 12%.

Recommendation: Accept tracking lag. Track via demo milestones not Jira %.

9. Data Migration - Three Weeks to Production, Still Frozen ​

Current State:

  • 1 of 42 categories Done: Peirce Phelps Customers (unchanged since July 7—14 days)
  • 6 BUs "WIP": Homans, ECMD, Gemaire, Baker, CE, Peirce (zero progress to Done in 14 days)
  • 35 categories NYS: Companies, Products, Orders, CMS, Lists

Week-over-Week: ZERO MOVEMENT for second consecutive week

Timeline Check:

  • Production cutover: 21 days away (August 11, 2026)
  • Required velocity: 41 categories / 21 days = 1.95 categories/day
  • Actual velocity: 0 categories/week (0.07/week = 1 Done in 14 weeks)
  • Gap: 28x velocity increase needed

Critical Analysis:

The "WIP" statuses assigned 2 weeks ago have not progressed. Audit of repository activity shows:

  • Peirce: Done (verified)
  • ECMD: Done (Lucian closed ECMDSW-41, 43 customer migration review)
  • Homans: Script ready, not run (Joshua LaRose S3 setup SXSW-1085)
  • Gemaire: Script ready, not run (Girish customer import GSHOP-96 2 weeks ago)
  • Baker: Script ready, not run (Nick import work BSWM-30-31)
  • CE: Script ready, not run (Blake account work 3 weeks ago)

Why Scripts Aren't Running:

  1. Staging environments still down—CI/CD blocks (SXSW-484-489) persist for 10+ weeks
  2. S3 access not fully enabled—SXSW-1085 still WIP per commits
  3. No forcing function—teams waiting for "perfect" conditions
  4. Serial dependencies—waiting for Customer→Company→Product sequence

What Changed This Week: NOTHING. Despite 572 total commits across platform, zero commits touched migration scripts.

Production Cutover is Impossible: At zero velocity for 2 consecutive weeks with 21 days remaining, August 11 launch will not include customer data. Options:

Option A: Emergency Parallel Execution (This Week)

  1. Run customer migrations to dev/local databases NOW
  2. Don't wait for staging—prove scripts work anywhere
  3. Stand up daily migration standup—15min blocker identification
  4. Accept manual data fixes—migrate imperfect, fix in production

Option B: Compress Scope (This Week)

  1. Launch with Customers only—defer Companies, Products, Orders, CMS, Lists
  2. All BUs get customer accounts—minimum viable migration
  3. Backfill remaining categories post-launch—2-4 week timeline

Option C: Slip Production Date (Leadership Decision)

  1. Move cutover to September 15—5 weeks slip
  2. Use 3 weeks for proper migration execution
  3. Use 2 weeks for validation + rollback prep

Recommendation: Combination of A + B is only viable path:

  1. Emergency execution this week—run all customer migrations by Friday
  2. Reduce scope—launch with Customers + Products only
  3. Accept imperfect—manual fixes in production acceptable
  4. Daily standup—force visibility on blockers

If no customer migrations complete by Friday July 25, escalate to executive leadership for production date decision.

10. BU Environment Deployment - CI/CD Blocks Enter 10th Week ​

Arrow Shopware Environments:

  • 5 BUs "CI/CD Blocked" (SXSW-484-489)—unchanged for 10+ weeks
  • Carrier Enterprise: Staging ETA today (July 21)—first progress in 10 weeks
  • All others: Local/Ordin Done, Staging NYS

Shopware Core Environments: All 7 BUs "Paused"—unchanged for 9+ weeks

Timeline Check:

  • August 11 production: 21 days away
  • Staging restart overdue: 2 weeks past mid-July target
  • No integration testing: 10+ weeks of dev work untested

What Broke (from prior analysis):

  • Old AWS CodePipeline deprecated in June
  • New GitHub Actions / Argo CD not ready
  • Webscale staging hosts decommissioned
  • No owner assigned to unblock

Repository Activity This Week:

  • Chris Nitchie: 14 commits on CE Docker builds + Redis + rate limiting—still CE-only focus
  • No commits on platform CI/CD (SXSW-484-489)

Impact Calculation:

  • 2 weeks to restart staging: Provision + deploy + smoke test
  • 1 week integration testing: Fix broken connections
  • 1 week UAT: Business validation
  • 1 week prod prep: Runbooks + rollback
  • Total: 5 weeks needed, 3 weeks available

Production Will Slip: August 11 is impossible. New realistic date: September 1 (3 weeks slip) assuming staging restarts THIS WEEK.

Emergency Actions:

  1. Carrier Enterprise staging today (July 21)—validate first BU can deploy
  2. All other BUs to staging by Friday—parallel deployment, not serial
  3. Chris: shift from CE to platform—CE can wait, platform blocking 7 BUs
  4. Accept manual deployment—automation later, just get code on hosts

11. Review Pipeline Aging - Chronic Cases Worsening ​

Current State: 70 items in review states (down from 81 last week but 13 chronic stale tickets persist)

Aging Analysis:

  • Development Complete: 38 items, median 19 days, P90 48 days, max 106 days
  • In Review: 15 items, median 3 days, P90 48 days, max 70 days
  • Ready for Review: 4 items, median 41 days, P90 45 days, max 45 days
  • Under Code Review: 23 items, median 4 days, P90 4 days, max 6 days

Stale Tickets (>30 days, showing worst offenders):

  • SXSW-391: Domain Resolver - 106 days (Mitchell Cowie)—+14 days since last week
  • SXSW-651: Cross-BU Feature Analysis - 70 days (Cleo Hister)
  • SXSW-915: Customer Export CLI - 59 days (Joshua LaRose)
  • SXSW-505, 493: Schema Design - 48 days each (Mitchell Cowie)
  • DOMAIN-246, 245, 244: Domain API lint fixes - 48 days (Mitchell Cowie)
  • DOMAIN-287, 304: Domain API graphql.document - 45/41 days (Mitchell Cowie)

Analysis:

  • SXSW-391 at 106 days is now oldest ticket in system—grew from 92 days last week (Mitchell Cowie)
  • Mitchell Cowie owns 9 of 13 stale tickets—appears to be review bottleneck
  • "Ready for Review" aging—4 tickets with median 41 days suggests nobody picking up reviews
  • "Under Code Review" moving fast—median 4 days shows when reviews happen, they complete quickly

Root Cause: Review capacity, not review speed. When tickets enter review, they move in 4 days. But getting into review queue takes 40+ days.

Immediate Actions:

  1. Mitchell Cowie's 9 tickets: Batch-close or escalate to tech lead for forced review
  2. SXSW-391 at 106 days: Emergency review this week or close as obsolete
  3. Assign second reviewer: Add backup reviewer to all "Ready for Review" tickets

Process Fix: Implement hard SLA:

  • Ready for Review → In Review: 7 days max
  • In Review → Done: 14 days max
  • Any ticket >21 days auto-escalates with executive visibility

12. Repository Activity & Team Velocity ​

Week Summary: 572 commits across 18 repos, 24 contributors (all-time high)

Top Contributors:

  • Emil Stewart: 90 commits (cesw, supergraph, plugins)—System Builder, Similar Products
  • Blake Saunders: 68 commits (cesw, supergraph, plugins)—DMI, User Permissions, Customer Import
  • Lino Rallo: 83 commits (boilerplate, peirce, homans, baker)—Homans deployment, shopping list, cart fixes
  • Pablo Romero: 83 commits (boilerplate, baker, peirce, homans)—Boilerplate v1.3.0, Brands page
  • Paul Briscoe: 58 commits (supergraph)—Branch resolution, cart mutations, offer-backed pricing
  • Tyler Hawkins: 37 commits (baker-headless, boilerplate)—Header styling, scroll visibility hook

Repository Breakdown:

  • cesw: 126 commits (Emil: 51, Blake: 34)—most active repo
  • ecommerce-supergraph: 138 commits (Paul: 58, Gabriel: 13)—Domain API + integrations
  • watsco-frontend-boilerplate: 30 commits (Lino: 30, Pablo: 20)—Boilerplate improvements
  • baker-headless: 34 commits (Tyler: 29, Pablo: 5)—Header + footer work
  • peirce-frontend: 13 commits—Boilerplate sync
  • homans-next-frontend: 13 commits (Lino: 13)—Shopping list integration

Velocity Analysis:

  • 572 commits / 7 days = 82 commits/day—43% increase from prior week's 58/day
  • Broad distribution: 24 contributors shows full team engaged
  • Concentrated repos: cesw (126) + supergraph (138) = 46% of all commits—suggests focused effort on platform

BU Activity:

  • CE: 126 commits (cesw) + 68 (Blake) + 90 (Emil) = 284 commits (50% of total)
  • Baker: 34 (baker-headless) + 18 (Nick backend) = 52 commits
  • ECMD: 8 (Lucian) = 8 commits
  • Gemaire: 0 captured = 0 commits

Concern: CE consuming 50% of all commits. Baker/ECMD/Gemaire getting <10% combined. This explains slow BU board progress.

Recommendation:

  1. Rebalance resources—shift 1-2 developers from CE to ECMD/Baker
  2. CE can absorb loss—at 67% complete with 284 commits/week, CE has excess capacity
  3. ECMD/Baker need boost—at 10%/12% with <60 commits/week, they're starved

Velocity Projection (Mermaid Gantt Chart) ​

mermaid
gantt
    title Projected Completion (based on current velocity)
    dateFormat YYYY-MM-DD
    todayMarker stroke-width:2px,stroke:#ef4444
    section Core
    SXSW (likely)              :active, 2026-07-21, 2026-11-24
    section Arrow
    Frontend (stalled)         :2026-07-21, 2026-08-15
    Infrastructure (likely)    :2026-07-21, 2026-08-18
    section Business Units
    CE Shopware (likely)       :2026-07-21, 2026-09-08
    Baker (stalled)            :2026-07-21, 2027-01-15
    ECMD (stalled)             :2026-07-21, 2027-05-01
    Gemaire (unknown)          :2026-07-21, 2026-12-31
    section Critical Path
    Data Migration (blocked)   :crit, 2026-07-21, 2026-12-31

Velocity Assumptions:

  • SXSW: 2.6 stories/day × 329 remaining = 126 days (November 24)
  • CE: +46/week × 224 remaining / 46 = 35 days (September 8)
  • Baker: +2/week × 210 remaining / 2 = 105 weeks (January 2027)
  • ECMD: +3/week × 314 remaining / 3 = 104 weeks (May 2027)
  • Data Migration: 0 velocity = blocked indefinitely

Critical Path: Data migration at 0 velocity blocks all BU launches. Even if SXSW/CE reach 100%, cannot go live without customer data.