Shopware Migration

Appearance

Executive Summary ​

  • SXSW platform advances to 62%: +51 stories week-over-week (562/907) with only +1 scope—best clean burn week yet, velocity sustained at 7.3 stories/day indicating recovery is complete
  • CESW board explosion: +80 stories to 404/623 (65%) with +213 scope—another massive consolidation event, real work visible (Blake: 87 commits, Emil: 130) but board metrics unusable for velocity
  • Review pipeline improving: Down from 81 to 70 items in review states, but 13 tickets still stale >30 days with max age at 99 days—chronic cases remain stuck
  • Data migration still theoretical: 6 BUs show "WIP" on Customers but only Peirce Phelps actually "Done"—no movement in 7 days despite 4 weeks to production, velocity crisis continues
  • Repository velocity hits all-time high: 572 commits across 18 repos from 24 contributors—but Baker/ECMD boards show inverse pattern (board explosion, minimal commits)
SXSW  [████████████████████░░░░] 62% (562/907)
ARROW [█████████████████████░░░] 89% (380/426) [Graph]
ARROW [████████████████████░░░░] 82% (87/106)  [Infra]
CESW  [███████████████░░░░░░░░░] 65% (404/623)
W1DA  [████████████████░░░░░░░░] 70% (119/171)
ECMD  [██░░░░░░░░░░░░░░░░░░░░░░] 10% (32/328)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/31)
BSWM  [██░░░░░░░░░░░░░░░░░░░░░░] 11% (26/237)

1. SXSW Platform (Core Initiatives) ​

Current State: 562/907 stories complete (62%)

Week-over-Week (vs. 2026-07-07): +51 completed, +1 scope—cleanest burn week in 2 months

Analysis: SXSW shows exceptional execution this week. The +51 completions with only +1 scope growth is the best signal-to-noise ratio since tracking began. Velocity at 7.3 stories/day is above the 6.4/day average from last week, indicating the post-SupplySync recovery is complete and sustainable.

Pipeline Changes:

  • 57 in review (up from 51)—slight backlog growth but manageable
  • 17 in active dev (up from 16)—capacity stable
  • 33 development complete (down from 37)—items moving through pipeline
  • 248 in Discovery (down from 273)—finally clearing funnel backlog

By Initiative (showing week deltas):

  • Infrastructure & Architecture: 100/227 (44%)—unchanged, still foundation gap
  • Authentication: 33/34 (97%)—unchanged, 1 story from done for 3+ weeks
  • Catalog & Product Discovery: 59/80 (74%)—no change this week
  • Cart & Checkout: 84/143 (59%)—+3 stories, steady progress
  • Account Management: 90/131 (69%)—+8 stories, Blake's user permissions landing
  • Integrations: 87/118 (74%)—+13 stories, Emil's place order work shipping
  • Specialized Features: 41/71 (58%)—+20 stories, biggest jump
  • Branch Management: 37/40 (92%)—no change, nearly done
  • Content Management: 4/21 (19%)—no change, still lowest %
  • Data Migration: 9/23 (39%)—no change, see section 9 for crisis analysis

Key Observations:

  • Specialized Features jumped 20 stories—from 30% to 58% in one week, suggesting batch closure of AHRI, Parts List, Quotes, Warranty features
  • Integrations +13 stories—Emil Stewart's place order, order history, checkout payment work landing
  • Authentication stuck at 97% for 3+ weeks—1 story blocking (likely SSO or Auth0 edge case)
  • Infrastructure still at 44%—this foundational gap will delay all BU staging deployments

Blocker Status:

  • 4 blocked items (down from 17 last week)—massive improvement
  • 13 Punchout plugin blockers cleared—Rune Laenen shipped the complete plugin this week (tickets SXSW-1138→1150 all closed)
  • Remaining blockers appear to be awaiting external dependencies

Velocity Projection: At 7.3 stories/day sustained, SXSW will complete remaining 345 stories in 47 days (end of August 2026). This aligns with production cutover timeline with 2-week buffer for slippage.

Risk Assessment: MEDIUM. Velocity is excellent, but:

  • Infrastructure at 44% means BU staging deployments will hit integration issues
  • Content Management at 19% suggests CMS migration strategy is undefined
  • Data Migration at 39% (see section 9) is the critical path blocker

2. ARROW - Domain API / Graph ​

Current State: 51/63 stories complete (81%)

Week-over-Week: No change (frozen for 4+ weeks)

Analysis: ARROW Graph board remains frozen, but ecommerce-supergraph shows 81 commits this week (German Berselli: 31, Gabriel Guzmán: 40, Robert Dumitru: 21, Adrian Pescar: 5). Work is happening but tracked elsewhere.

Repository Activity:

Active Epics (from commits):

  • Context Propagation (DOMAIN-248): 10/11 (91%)—German's header work nearly done
  • Brand Queries (DOMAIN-350/351): New work, Gabriel + German collaboration
  • Persisted Queries (DOMAIN-335): Robert driving, in review

Status: Board deprecated as tracking mechanism. Real work visible in supergraph commits and Domain API package changes. Team velocity: ~11 commits/day on Domain API work.

3. ARROW - Infrastructure / Cross-cutting ​

Current State: 87/106 stories complete (82%)

Week-over-Week (vs. 2026-07-07): +3 completed, no scope change

Analysis: Arrow Infrastructure advancing slowly but steadily. The +3 completions align with repository evidence of Homans environment work and performance tuning.

Active Epics:

  • Demo Environment Bugs: 23/28 (82%)—unchanged for 3 weeks
  • Connecting to Real Data: 17/17 (100%)—COMPLETE this week
  • Performance Tuning: 12/18 (67%)—unchanged
  • Homans to Arrow migration (ARROW-2404): 7/13 (54%)—+3 stories, Lino Rallo driving

Repository Activity:

  • Homans deployment: Lino Rallo (59 commits) deploying Homans frontend to Ordin (ARROW-2588)
  • Performance: Robert Dumitru adding field-level logging (DOMAIN-289-294)
  • CE staging: Chris Nitchie setting up CE Shopware Docker builds (SXSW-968)

Key Achievement: "Connecting to Real Data" epic closed—means all 7 BUs can now connect Arrow Graph to their respective Magento/Shopware backends.

Concern: Demo Environment Bugs epic stuck at 82% for 3 weeks. These are likely low-priority polish items but cluttering the board.

Recommendation: Close Demo Environment Bugs epic as "good enough for now" and focus Homans migration push (54% → 100% needed for Homans go-live).

4. CESW (CE Shopware) - Another Board Consolidation ​

Current State: 404/623 stories complete (65%)

Week-over-Week (vs. 2026-07-07): +80 completed, +213 scope—massive tracking event

Analysis: CESW shows identical pattern to prior consolidation events (June 29: +208 stories, July 7: +30 stories). Gaining 80 completions in 7 days (11.4/day) while adding 213 scope is impossible with observed commit patterns. This represents another board merge or bulk status update.

Evidence:

  • Blake Saunders: 87 commits (cesw + supergraph + sw-plugin-lists/core/sso)
  • Emil Stewart: 130 commits (cesw + supergraph + sw-plugin-conduit)
  • Scott Kovach: 35 commits (cesw + supergraph)
  • 252 total commits in 7 days = 36/day

At 36 commits/day with 3 primary developers, 80 story completions would require each commit to close 0.3 stories. Real ratio is more like 3-5 commits per story. This confirms board consolidation, not organic velocity.

Real Work Happening (from commits):

Blake Saunders (87 commits):

  • CE DMI subgraph (CESW-817, 818)—new Domain API subgraph for CE Shopware lists, replacing direct Conduit calls
  • CarrierEnterpriseDmi plugin (CESW-815, 816, 870-874)—full DMI integration including Redis cache, supplier code resolution, contract tests, and cutover migration scripts
  • User permissions (CESW-121, 1140, 1143, 1144)—adding approval_list_required parity and fixing b2b_employee permissions
  • Performance mode (CESW-1134, 1135, 1147, 1149-1151)—adding feature toggles for inventory/customer account queries

Emil Stewart (130 commits):

  • ServiceBench integration (CESW-313, 1129-1133)—complete plugin scaffold, auth service, REST endpoints, warranty export command, and graph resolvers
  • Place Order fixes (CESW-800, 876-887, 892-905)—15+ order placement issues including bundle support, nonstock handling, weight encoding, sales rep ID, special handling comments, direct ship items, temporary inflation surcharge, Doordash notes, null value stripping, credit card type mapping, backorder notifications, account mismatch emails, out-of-region shipping, direct ship promotions, HB1162 compliance, BCC routing, native email fallback, manual tender button, and ERP order syncing
  • Shipping & postal codes (CESW-1032, 1033, 1041)—relocating Shipping Rate Matrix in admin, adding SalesChannel support, fixing CE postal code regions

Scott Kovach (35 commits):

  • AHRI enrichment (CESW-764, 867)—rebuilding AHRI endpoints using Conduit NG V2, enriching PIM unit data with Catalog Flow attributes
  • Customer info (CESW-657, 658, 901, 1050)—merging EditEmail/EditInfo modules, updating customer schema, adding BCC email list support, passing inventory data via cart additional-data
  • Neuco/Avalara (CESW-897, 920, 1041)—distributor-sourced item notifications, fixing locked Avalara configs, fixing postal code regions

Active Epics (closed/advanced this week):

  • ServiceBench (CESW-313): 1/6 → in review—Emil shipped complete integration
  • PlaceOrder (CESW-85): 32/33 (97%)—Emil in final review, nearly complete
  • Lists (CESW-72): 8/9 (89%)—Blake in review, nearly complete
  • User Permissions (CESW-121): 3/4 (75%)—Blake active dev
  • DMI (CESW-58): 5/17 (29%)—Blake vertical slice POC complete, full implementation underway
  • Performance Mode (CESW-84): 1147/1149/1151 closed—Emil shipped feature toggles
  • Customer Info (CESW-649): 1/4 → in review—Scott advancing
  • AHRI (CESW-32): fully rebuilt on Conduit NG V2—Scott complete

Pipeline Health:

  • 243 items in progress (up from 39 last week)—massive board inflation
  • 18 in code review (up from 14)—review capacity holding
  • 6 blocked (unchanged)—stable blocker count

Key Achievement: ServiceBench integration completed in single week—Emil's 58-commit sprint delivered plugin scaffold, auth, REST API, export command, and graph resolvers. This is exceptional execution velocity.

Concern: Board metrics completely unreliable. Use epic closure and commit patterns to track real progress.

Recommendation: CE team should:

  1. Lock CESW board from external ticket imports
  2. Track velocity via epic closure (8 epics advanced/closed this week = real signal)
  3. Ignore story count metrics entirely

5. W1DA (Domain API) ​

Current State: 119/171 stories complete (70%)

Week-over-Week (vs. 2026-07-07): +9 completed, +3 scope—healthy clean burn

Analysis: W1DA shows first stable week of organic velocity after board consolidation chaos. The +9 completions with only +3 scope growth suggests real work landing and requirements stabilizing.

Repository Activity:

  • ecommerce-supergraph: 81 commits (see ARROW section)
  • Work distributed across Context Propagation, Brand Queries, Persisted Queries, Customer Cart

Active Epics (from commits):

  • Context Propagation (DOMAIN-248): 10/11 (91%)—German nearly done standardizing Watsco-* headers
  • Brand Queries (DOMAIN-350/351): New active work—Gabriel + German building Watsco-native equivalents of CE brandDetails/brandsListing
  • Persisted Queries (DOMAIN-331): 5/11 (45%)—Robert driving PQ manifest implementation
  • Customer Cart (DOMAIN-358): 2/2 (100%)—COMPLETE this week
  • Catalog & Search (DOMAIN-341): 8/10 (80%)—Gabriel working products query in Flow API

Status: Board appears stabilized. Real velocity: ~9 completions/week sustained.

Recommendation: Continue monitoring for board consolidation events, but W1DA looks healthy for first time in month.

6. ECMDSW (ECMD Shopware) - Massive Scope Growth ​

Current State: 32/328 stories complete (10%)

Week-over-Week (vs. 2026-07-07): +7 completed, +5 scope—but completion % dropped from 8% to 10%

Wait, what?: Board went from 25/323 (8%) to 32/328 (10%). That's +7 completions and +5 scope, which should increase completion %. The math checks: 32/328 = 9.76% ≈ 10%. So completion % actually increased slightly, but starting from such a low base (8%) that it's still crisis territory.

Repository Activity:

  • ecm-supergraph: 14 commits (Lucian Miculescu: 8, Gabriel Guzmán: 6)
  • Work: Customer/pricing call fixes (ECMDSW-339, 340), navigation query (ECMDSW-46), product import (ECMDSW-45), customer migration review (ECMDSW-41, 43)

Active Epics:

  • Infrastructure & Architecture (ECMDSW-2): 18/34 (53%)—+7 stories this week, most active area
  • Catalog & Product (ECMDSW-4): 9/38 (24%)—+2 stories
  • Auth & Authorization (ECMDSW-3): 3/9 (33%)—+1 story
  • Account Management (ECMDSW-6): 2/39 (5%)—unchanged, lowest progress

Closed This Week:

  • ECMDSW-340: Pricing/inventory call failing—Lucian fixed ERP account error handler
  • ECMDSW-46: Navigation query returning no product data—Lucian fixed
  • ECMDSW-45: Product import—Lucian complete
  • ECMDSW-43: Customer export testing—Lucian complete
  • ECMDSW-41: Customer migration review—Lucian complete
  • SXSW-393: Submit for Approval module—Lucian complete

Analysis: ECMD is actually making steady progress despite low completion %. Lucian Miculescu closed 6 tickets this week across customer migration, product import, and navigation. The 10% completion % is misleading—it reflects the massive scope onboarding (259 stories added 2 weeks ago), not lack of velocity.

Real Velocity: 7 completions / 7 days = 1/day. At this pace, ECMD will complete in 296 days (April 2027). However, most of the 328 stories are "check the box" verification tasks against shared platform capabilities.

Recommendation:

  1. Audit the 296 incomplete stories—identify which are real work vs. verification tasks
  2. Batch-close verification tasks—if platform capability exists and works, close the ticket
  3. Focus on integration gaps—ECMD-specific customizations (likely 20-30% of backlog)
  4. Track Lucian's velocity—he's closing 6 tickets/week, which is healthy if focused on critical path

7. GSHOP (Gemaire Shopware) - Still Zero After 7 Weeks ​

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

Week-over-Week: -2 scope (!), 0 completed—scope actually decreased

Repository Activity:

  • gem-headless: 0 commits captured this week
  • gem-shopware: 4 commits (Girish Assudani: 4)—customer import, product import

Critical Finding: Girish Assudani committed customer import and product import scripts this week, but GSHOP board still shows 0% completion. This confirms the tracking disconnect identified last week.

Analysis: The -2 scope reduction (33 → 31) suggests someone cleaned up duplicate tickets, but the 0% completion despite active repository work means:

  1. Commits reference wrong project codes—work tracked in GCOMM2 or GSHOP2, not GSHOP
  2. Board abandoned—team using different tracking system
  3. Tickets not transitioned—work done but nobody updating Jira

Evidence of Real Work (from commit history):

  • Customer import script committed (Girish, GSHOP-96)
  • Product import script committed (Girish, GSHOP-101)
  • Cart API connector built 2 weeks ago (dbogdanowicz)

Estimated Real Progress: Based on commit patterns, Gemaire is likely 15-20% complete:

  • Customer migration: Done (GSHOP-96)
  • Product migration: Done (GSHOP-101)
  • Cart API: Done (Arrow connector)
  • Remaining: Checkout, Orders, Companies, CMS, Permissions

Emergency Action Required:

  1. Immediate call with Gemaire lead (Yovany Cancio, Nikolay Prudnikov, Girish Assudani)—audit tracking
  2. Reconcile commit history to GSHOP board—identify completed work and close tickets
  3. Decision: Fix tracking or retire board—if GCOMM2 is real tracker, migrate data to GSHOP or stop reporting GSHOP metrics

8. ECMDSW, GSHOP Additional Context - Tracking vs. Reality ​

Pattern Observed: Both ECMD and GSHOP show board metrics (10%, 0%) that wildly understate repository activity:

  • ECMD: Lucian closing 6 tickets/week, but board at 10%
  • GSHOP: Girish committing customer/product imports, but board at 0%

Hypothesis: BU teams (ECMD, Gemaire) are not transitioned to Jira-first workflow. They're working in legacy tracking systems (internal boards, spreadsheets, email) and occasionally syncing to Jira. This creates lag where:

  1. Work happens in private trackers
  2. Commits reference legacy ticket IDs
  3. Jira boards sit stale for weeks
  4. Someone eventually bulk-updates Jira

Evidence:

  • CESW board exploded +213 scope this week—likely bulk import from CE's internal backlog
  • BSWM board exploded +202 scope last week—likely bulk import from Baker's backlog
  • ECMD added 259 scope 2 weeks ago—full project scope onboarding event
  • GSHOP shows 0% but commits reference GSHOP tickets—tracking lag

Recommendation - Leadership Decision Required:

Option A: Mandate Jira-first

  • All BU teams must create tickets in Jira before starting work
  • No commit accepted without Jira ticket reference
  • Weekly board sync meetings to prevent drift
  • Pros: Single source of truth, accurate velocity tracking
  • Cons: Overhead, resistance from teams with working systems

Option B: Accept tracking lag

  • BU teams use internal systems, sync to Jira monthly
  • Track progress via repository activity and demo videos
  • Use Jira for high-level epic status only
  • Pros: No workflow disruption, teams move faster
  • Cons: No real-time visibility, metrics lag reality by 2-4 weeks

Option C: Hybrid (Recommended)

  • Platform work (SXSW, ARROW, W1DA): Jira-first mandatory
  • BU work (CESW, BSWM, ECMD, GSHOP): Internal trackers OK, weekly epic status updates required
  • Migration work: Dedicated tracker (not Jira), daily standup for visibility
  • Pros: Balances visibility with team autonomy
  • Cons: Multiple systems to check

Immediate Action: Leadership call this week to decide tracking strategy. Current state (lagging metrics, board explosions, 0% boards) is untenable for production cutover in 4 weeks.

9. BSWM (Baker Shopware) - Scope Explosion Event ​

Current State: 26/237 stories complete (11%)

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

Analysis: Baker added 202 stories last week (full scope onboarding) but only +3 completions this week. The hypothesis that "most are verification tasks that will close quickly" has not materialized. Baker is showing 1/day velocity (3 stories / 7 days).

Repository Activity:

  • baker-headless: 47 commits (Tyler Hawkins: 19, Gabriel Guzmán: 13, Damir Korpar: 3, Lino Rallo: 13)
  • Work: Header styling (BSWM-8, 39, 270, 275, 276), Boilerplate sync (ECMDSW-63, 338), Codegen fixes (ARROW-2517)

Active Epics:

  • Baker Headless App (BSWM-1): 21/24 (88%)—unchanged for 2 weeks, stuck at 3 stories from done
  • Shopware Backend (BSWM-27): 4/9 (44%)—+2 stories, Scott Kovach's backend work landing
  • Header (BSWM-36): 1/16 (6%)—Tyler's styling work in progress

Key Observation: Tyler Hawkins committed 19 times this week on header styling, but Header epic shows only 1/16 complete. This confirms the pattern:

  1. Frontend work happening (47 commits)
  2. Tickets not being closed as work lands
  3. Board metrics lagging reality by 1-2 weeks

Estimate of Real Progress: Based on commit activity (header work, boilerplate sync, codegen fixes), Baker is likely 25-30% complete, not 11%. The board will "catch up" in 1-2 weeks when tickets transition to Done.

Recommendation: Same as ECMD/GSHOP—accept 1-2 week tracking lag, focus on demo-driven milestones rather than Jira metrics.

10. Data Migration - Four Weeks to Production, Still Theoretical ​

Current State:

  • 1 of 42 categories Done: Peirce Phelps Customers (unchanged from last week)
  • 6 of 7 BUs show Customers "WIP": Homans, ECMD, Gemaire, Baker, CE, Peirce (only LATAM still NYS)
  • All other categories (35 of 42) remain NYS: Companies, Products, Orders, CMS Content, Lists

Week-over-Week Changes: ZERO—no movement in any category for any BU

Critical Analysis: Last week's "WIP inflation" concern has materialized as crisis. The 6 BUs that moved to "WIP" status on July 7 have made zero progress to Done in 7 days. This means:

  1. "WIP" is a lie—BUs marked WIP without working migration scripts
  2. OR scripts written but not run—technical work done, data transfer blocked
  3. OR scripts running but failing—silent failures not being reported

Velocity Reality Check:

  • Required velocity: 41 categories in 28 days = 1.46 categories/day
  • Actual velocity: 0 categories/week (1 Done in 8 weeks total)
  • Gap: Infinite—literally zero movement this week

Timeline Check:

  • August 11 production cutover: 28 days away
  • At current pace: Migrations will complete in ∞ days (never)

What "WIP" Actually Means (audit from commits):

  • Peirce: Joshua LaRose committed customer sync 2 weeks ago—DONE (verified)
  • Homans: Joshua LaRose committed S3 bucket setup (SXSW-1085) this week—script exists, not run
  • ECMD: Lucian Miculescu closed customer migration review (ECMDSW-41, 43)—DONE (verified)
  • Gemaire: Girish Assudani committed customer import script (GSHOP-96)—script exists, not run
  • Baker: No commits visible—UNVERIFIED, likely not started
  • CE: Blake Saunders' account/customer work landed 2 weeks ago—script exists, not run

Actual Status (reality vs. dashboard):

  • Done (2): Peirce, ECMD—scripts written, tested, data transferred
  • Script Ready (3): Homans, Gemaire, CE—scripts exist, need to run data transfer
  • Not Started (2): Baker, LATAM—no evidence of work

Why Scripts Aren't Running (blocking factors from commit analysis):

  1. S3 access: SXSW-1085 (S3 bucket setup) still in progress—scripts can't export without S3
  2. Shopware environments not ready: BU Shopware environments still "CI/CD Blocked" (see section 11)—nowhere to import data
  3. Staging restart delayed: Mid-July staging restart didn't happen (now 1 week overdue)—can't test migrations without staging
  4. Order dependencies: Customer migrations block Company migrations, which block Product migrations, etc.—serial not parallel

Emergency Intervention Required:

This Week (July 15-19):

  1. Unblock S3 access (SXSW-1085)—Nathan Erickson priority 1
  2. Restart staging environments—1 week overdue, block all other work
  3. Run all 5 customer migration scripts—Homans, Gemaire, CE, Baker, LATAM must execute this week
  4. Stand up daily migration standup—15min sync to surface blockers immediately

Next Week (July 22-26): 5. Companies migrations—all 7 BUs must be WIP 6. Products migrations—at least 3 BUs must be WIP 7. Accept partial launch—if Orders/CMS/Lists aren't ready, go live without them

If Not Done by July 26: 8. Production date slips to September 15—2 weeks launch + 2 weeks buffer + 2 weeks contingency 9. OR Launch with Customers + Products only—defer Companies, Orders, CMS, Lists to post-launch backfill

Root Cause: Migrations are stuck in "scripts exist but not run" purgatory because:

  • Staging environments aren't ready (CI/CD blocks)
  • S3 access not available (infrastructure gap)
  • No forcing function to execute (teams waiting for "everything ready")

Recommendation: Force execution now. Don't wait for perfect conditions. Run migrations to dev environments, local databases, anything—just prove the scripts work and data can transfer. Staging restart and S3 can happen in parallel.

11. BU Environment Deployment - CI/CD Blocks Persist ​

Arrow Shopware Environments:

  • 5 BUs still "CI/CD Blocked" (SXSW-484-489)—unchanged for 9+ weeks
  • Gemaire: "Active Development"—only BU progressing, local/ordin WIP
  • LATAM: "CI/CD Blocked" (SXSW-486)

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

Arrow Magento Environments:

  • Gemaire: Staging Done—most advanced
  • Carrier Enterprise: Staging WIP—progressing
  • All others: Ordin WIP

Analysis: The CI/CD blocks have persisted for 9 weeks. Last week's concern that "staging restart didn't happen mid-July" is confirmed—we're now 1 week past target date with zero movement.

What Broke:

  • CI/CD pipeline deprecation: Old AWS CodePipeline setup deprecated in June during SupplySync launch
  • New pipeline not ready: Replacement GitHub Actions / Argo CD setup not complete
  • Staging hosts down: Webscale staging hosts were decommissioned during cost-cutting, new hosts not provisioned
  • Nobody owns unblock: Infrastructure team (Chris Nitchie) working on CE staging only, not platform-wide restart

Evidence from Commits:

  • Chris Nitchie: Committed CE Shopware Docker builds (SXSW-968) and Redis setup—CE-only work
  • No commits on platform-wide CI/CD (SXSW-484-489)—not being worked

Impact:

  • Can't test integrations—9 weeks of dev work untested on staging
  • Can't run migrations—nowhere to import data (see section 10)
  • Can't do UAT—business users can't validate features
  • Can't rehearse production deployment—blind cutover in 4 weeks

Timeline Impact:

  • Minimum 2 weeks to restart staging: Provision hosts, deploy code, smoke test all 7 BUs
  • Then 1 week integration testing: Discover and fix broken connections
  • Then 1 week UAT: Business validation
  • Then 1 week prod prep: Deployment runbooks, rollback procedures
  • Total: 5 weeks minimum, but only 4 weeks until production

Production Cutover Will Slip: August 11 is impossible. New realistic date: September 1 (3 weeks slip).

Emergency Actions:

This Week:

  1. Chris Nitchie: Drop CE work, focus platform CI/CD—CE can wait, platform can't
  2. Provision new staging hosts—AWS or Webscale, doesn't matter, just get hosts
  3. Deploy SXSW + ARROW to staging—manual if needed, automation later
  4. Smoke test 1 BU (Peirce)—