Shopware Migration

Appearance

Executive Summary ​

  • SXSW breaks infrastructure stall, unblocking downstream environment work: Core platform advances +12 stories to 72% (680/939) after SXSW-1125 (EKS hosting) finally closed an 82-day Active Dev stall.
  • CE holds at 98% awaiting final deployment, not missing development: CE Shopware remains flat (662/679) with no board movement, but Emil's 84 commits ship real work (AHRI fixes, rewards checkout, performance profiling) — the final 17 stories are integration/deployment hurdles, not missing features.
  • ECMD delivers the week's biggest reversal: +41 stories to 37% (171/460) with Damir/Sebastian's 138 commits reversing prior month's collapse, though +12 net stories added signals scope is still growing.
  • Baker sustains post-reallocation momentum: +8 stories to 56% (213/382) with Gabriel's 110 commits maintaining steady progress.
  • Homans/Peirce show 0% in Jira (expected for new boards) but real progress is hidden in shared boilerplate: feature parity matrices reveal 41 Done features each, invisible until BU-specific decomposition completes.
  • Risk: CE's Deploying pipeline is aging (9 tickets, median 7 days) while production cutover looms; ECMD's +12 net scope growth outpaces +41 completion, expanding its backlog to 289 stories.

Progress Overview ​

SXSW  [████████████████████░░░░] 72% (680/939)
CESW  [█████████████████████████] 98% (662/679)
ECMDSW[█████████░░░░░░░░░░░░░░░] 37% (171/460)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/101)
BSWM  [█████████████░░░░░░░░░░░] 56% (213/382)
HMSW  [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/0)
PPSW  [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/16)

1. Shopware Platform - SXSW Initiatives ​

+12 stories to 72% (680/939), +5 net stories added. Week-over-week delta matches last analysis (+12 done / +5 net), sustaining ~12/week velocity observed since late July recovery. This represents 259 stories of progress remaining to hit Sep 30 Core Platform Complete milestone — requires sustained 19/week velocity (58% above recent average) if deadline holds, or backlog-tagging effort (flagged in prior note) dramatically reduces visible scope.

Infrastructure unblocked: SXSW-1125 (EKS hosting) closed after 82 days. This was the oldest ticket in Active Development and blocked downstream BU environment provisioning (Homans/Peirce/ECMD staging/production). Closure aligns with program_notes context: EKS staging delivered Aug 20, Conduit integration (SXSW milestone "EKS — Conduit Integration," target Sep 5) is the next concrete step, and frankly-acknowledged R&D on autoscaling/hardening is ongoing. CENA Production Live milestone (retitled "CENA Production Live — Beta Customer") moved from Aug 15 to week of Sep 21 explicitly due to this EKS maturity gap — that slip is infrastructure-attributed per program_notes, not a SXSW-side delay.

17 tickets in review/testing pipeline, oldest at 40 days (SXSW-1173). This In Review ticket (ERP account mutations) has aged since Aug 29 with no visible blocker — either needs escalation or is blocked by something outside the ticket's link graph. SXSW-1179 (Punchout JWT auth, 34 days Active Dev) and SXSW-629 (tax calculation, 6 days In Review) represent the next aging items. Pipeline velocity is healthy (12 In Review, 7 Development Complete) but the 40-day outlier suggests a coordination gap on the account-mutation work.

Velocity vs. Core Platform deadline: If "core" scope is genuinely the full 939-story backlog, Sep 30 is unachievable at current velocity (would require 19/week vs. observed 12/week). If "core" is a curated subset, the backlog-tagging effort called out in prior analysis (Sep 30 milestone note: "requires tagging all existing Jira tickets that belong to 'core'") must complete soon to make the real remaining scope visible. Watch for sudden scope reductions in the next 1-2 weeks as that tagging effort lands — if the board shrinks from 939 to something smaller, that's the deliberate curation finishing, not scope being secretly cut.

6. CE Shopware (CESW) ​

Flat at 98% (662/679), +0 done / +1 net story added. No board movement this week despite Emil's 84 commits (largest single contributor) and Blake's 20 commits driving real work: AHRI details fixes (CESW-1948/1949), rewards checkout (CESW-1749), performance profiling (CESW-1954), and Curb Adapter PDF downloader (CESW-1909) all shipped. This is the expected behavior flagged in prior analysis: CE is 98% complete, final 17 stories are integration/deployment hurdles (Deploying state: 9 tickets, median 7 days), not missing features. Board progress has effectively decoupled from commit activity at this stage.

Deploying pipeline ages but production cutover risk subsiding. 9 tickets in Deploying (median 7 days): CESW-1992 (credit card management, 4 days), CESW-2027 (payment method improvements, 0 days), CESW-1949 (AHRI fixes, 0 days), CESW-1909 (Curb Adapter PDF, 0 days), CESW-1647 (ERP account permissions, 4 days), CESW-1591 (cart refresh fix, 26 days — oldest outlier). The 26-day outlier needs escalation: cart bugs shipping to production after 26 days in Deploying suggests deployment coordination gaps rather than technical blockers. Overall, the pipeline is healthier than prior weeks (median down from 12 days last analysis) but the long tail persists.

Mobile integration and quote retention work progressing. Scott's 22 commits (CESW-2014/2015: PO/reference fields on cart, pro points balance) and Emil's rewards checkout work (CESW-1749) address mobile app coordination gaps flagged in prior reviews. CESW-1952 (retain ERP quote shipping address), CESW-1861 (quote freight charges), and CESW-1859 (ERP quote number not sent) all closed this week — these were the quote retention blockers identified in earlier sessions. CE is systematically addressing the "integration/deployment hurdles" remaining in the final 2%.

CE is the one board where ongoing SXSW completion isn't a structural blocker. Per program_notes context from Aug 18, CE already has platform work baked into its own board and is building BU-specific features independently. The other 5 active BU boards (ECMDSW, GSHOP, BSWM, HMSW, PPSW) are structurally gated by SXSW's 259 remaining stories — CE's 98% completion is decoupled from that constraint. This makes CE the cleanest path to production in the program, contingent only on resolving the Deploying pipeline aging above.

8. ECMD Shopware (ECMDSW) ​

Explosive recovery: +41 stories to 37% (171/460), but +12 net stories added signals scope still growing. Week's biggest turnaround after prior month's collapse (22/64 → 171/460 represents 149 stories of progress, but scope expanded from 64 to 460 in that same window — this week's +12 net is a microcosm of that pattern). Damir's 87 commits (67% ECMD-specific, 73% frontend) and Sebastian's 123 commits (29% ECMD, 86% frontend) drive the velocity: AHRI matchup/details work (ECMDSW-385/386), order approvals (ECMDSW-209), and orders list/detail pages (ECMDSW-200/468) all advanced materially. This is the intended effect of the Sebastian/Gabriel reallocation noted in prior program_notes (Jul 28) — Sebastian's 123 commits this week is highest output in the program, Gabriel's 159 commits split across Baker/ECMD sustains both boards.

289 stories outstanding, program's largest absolute backlog. Even after +41 stories done, ECMD remains furthest from completion in raw story count. Prior analysis flagged "331 stories outstanding" — scope grew +13 (289 now vs. 276 implied prior week) while 41 closed, netting +12. This isn't random churn: Damir's commits include "feat: ECMDSW-385" (AHRI list work) and "feat: ECMDSW-415" (promo codes) — both are net-new features being actively developed, not backlog grooming artifacts. ECMD is genuinely expanding scope mid-flight, which is sustainable only if velocity scales proportionally (this week's +41 vs. +12 net = 3.4x delivery rate, which is healthy, but unsustainable long-term if scope growth continues).

AHRI matchup/details work (ECMDSW-385/386) unblocked downstream by SXSW-1108. Damir's 87 commits include extensive AHRI UI work (outdoor lookup tab, unit selection logic, data fetching) — this was previously blocked by missing order requirements resolvers in the core platform. SXSW-1108 (order requirements resolver) shipped this week per Ilir's commits, unblocking ECMD's frontend. This is a concrete example of the SXSW-as-gating-dependency dynamic: ECMD's AHRI work was ready but couldn't land until the platform layer completed, illustrating why ECMD's 37% completion is still structurally slower than it appears in isolation.

Repository activity aligns with board progress for first time in weeks. Prior analyses flagged "commits landing in wrong repo" (Baker) and "board says nothing despite commits" (ECMD) as evidence of board-vs-reality gaps. This week, Damir's 87 commits + Sebastian's 123 = 210 total commits driving +41 stories done = 5.1 commits/story closed, which is within normal range for frontend-heavy work. The reallocation intervention (Sebastian/Gabriel moved to ECMD/Baker Jul 28) is showing the intended effect: board movement now reflects actual commit activity again.

Feature-parity matrix: 4 rows corrected from Done/In Progress back to Not Started. The 2026-09-08 feature-parity.csv re-download reverted ECMD's Customer Portal Dashboard, Customer Navigation, and Order History (List/Details View) to Not Started, flipping the Feature Migration matrix's ECMD / Order Queue-Place category from WIP to NYS. Per NOTES.md, this is a spreadsheet status correction, not new dev regression — these rows were previously marked prematurely, and Homans/Peirce advanced on several of the same rows in the same update. Do not read this as ECMD losing ground this week; the board-side numbers above (+41 stories) are the accurate signal for actual ECMD velocity.

9. Gemaire Shopware (GSHOP) ​

Flat at 0% (0/101), +10 net stories added, but real frontend work invisible in Jira. Board grew from 91 to 101 stories (all unstarted) while Damian's 31 commits and Yovany's 28 commits drive actual PDP/Search/Warranty work in gem-headless repo. This is the expected state flagged in prior analysis: GSHOP is a planning/discovery artifact, not a delivery tracker. Commit activity (59 total this week, all frontend) is the real progress signal — the board lags because frontend work hasn't been decomposed into trackable Jira stories yet.

Commit breakdown: PDP (GSHOP-63, GSHOP-87/88/89), Search (GSHOP-161), Warranty (GSHOP-53). Damian's 31 commits include "feat: GSHOP-161" (search PLP visual fixes) and Yovany's 28 commits include "feat: GSHOP-87" (addons backend-agnostic components) — all targeting large parent epics (GSHOP-63: PDP, 42 days in progress) that won't close until all child work completes. This creates the illusion of stasis on the board (0/101 unchanged for weeks) while real work ships continuously. The board will stay 0% until either (a) child stories are created and closed incrementally, or (b) the 13 large epics close atomically when fully complete.

Blocker graph stable: GSHOP-118 (Google Maps config) still blocks 3 tickets (32 days). This external dependency (Mike D'Ottavio assigned, waiting on Google Cloud Console setup) gates branch finder testing (GSHOP-133/132/44). No change from prior week — escalate to unblock the branch finder test suite, as this is a known external bottleneck flagged in prior sessions.

Feature parity matrices show stasis (0 Done features) but aren't updated weekly. Gemaire status_counts (46 Done, 137 Not Started) are identical to prior analysis, suggesting the manually-maintained CSV wasn't refreshed this week. Until that updates, commit activity remains the only real-time progress signal for GSHOP. Board progress will remain invisible until frontend work migrates from gem-headless into Jira epics.

10. Baker Shopware (BSWM) ​

Sustained +8 stories to 56% (213/382), +3 net stories added. Third consecutive week of single-digit velocity gains after reallocation intervention (Jul 28 program_notes: Sebastian/Gabriel moved to Baker/ECMD to fix board-vs-reality gap). Gabriel's 159 commits split 28% Baker-specific (49 commits in baker-headless), Sebastian's 123 commits split 29% Baker (35 commits), and Tyler's 21 commits 86% Baker (18 commits) = 102 Baker-specific commits this week driving +8 stories closed. This is the cleanest example in the program of reallocation working as intended: board movement now aligns with commit activity, velocity sustains week-over-week.

Orders integration work dominates commit activity. Sebastian's 35 Baker commits include "feat(BSWM-200): Orders list and order detail pages" (order sync fixes, invoice tab, print view), Tyler's 18 Baker commits target "feature/BSWM-189-ERP-Quote-Updates" (quote domain module), and Gabriel's 49 Baker commits include "feat: BSWM-475" (credit card selection in checkout) and "feat: BSWM-476" (checkout credit card form reuse). All three contributors are actively building full-stack order/checkout flows rather than isolated features — this is mature, integrated work, not scaffolding.

169 stories outstanding, on track for Q4 completion at current velocity. +8/week velocity × 21 weeks remaining in Q4 = 168 stories deliverable, which almost exactly matches the 169 outstanding. If velocity sustains (and Sebastian/Gabriel remain allocated), Baker could hit near-100% completion by year-end. This is the rosiest projection in the program outside of CE (already 98%) — Baker is the second-most mature BU board by a significant margin.

Cleo's ERP Quote domain module (BSWM-289) unblocks quote-to-cart flows. Cleo's 9 commits this week include "BSWM-289 Merge origin/main" (ERP Quote domain module integration) — this was a long-standing gap where Baker's frontend quote work couldn't wire to backend until the domain layer existed. That gap is now closed, unblocking Gabriel's checkout work (BSWM-475/476) flagged above. Baker is systematically resolving cross-layer dependencies rather than accumulating technical debt.

12. Homans Shopware (HMSW) ​

Still 0/0 in Jira (expected for brand-new board added Aug 18), but feature parity shows 41 Done features vs. 65 Not Started. Board remains empty because discovery phase hasn't completed yet — all 31 epics (HMSW-1 through HMSW-31) are in Discovery status with 0 child stories. This is the intended state per prior program_notes: Jira gap is expected for new boards until decomposition finishes, feature parity matrix is the real progress signal. Homans' 41 Done features include PLP, PDP, Cart, Checkout (all "Done"), Account Dashboard (In Progress), and User Management (In Progress) — this is real work, just not yet reflected in board progress.

Pablo/Lino's 140 combined commits drive shared boilerplate work benefiting both Homans and Peirce. Pablo's 395 commits this week split 27% Homans (107 commits in homans-next-frontend), Lino's 79 commits split 18% Homans (14 commits) — both target shared Checkout/PDP/Cart features visible in watsco-frontend-boilerplate repo. This work is BU-agnostic until customization happens, so it benefits Homans, Peirce, and Baker simultaneously. The board won't reflect this until BU-specific stories are created — until then, feature parity matrices and commit activity are the only progress signals.

Homans' feature parity status_counts (41 Done, 65 Not Started, 30 In Progress, 34 Feature Not Needed) align with Peirce exactly. Both BUs show identical completion on shared boilerplate features (PLP, PDP, Cart, Checkout, Auth, Branch Management all "Done") — this confirms the shared-work dynamic above. Divergence will appear only when BU-specific customizations start (Homans' unique integrations: Salesforce, Rudderstack, Moblico, Live Chat, Mobile App all "Not Started" — these are the future differentiation points).

Board will remain 0% until discovery completes and stories migrate from boilerplate into BU-specific epics. This is by design, not a failure signal. Watch for sudden board population (0 → 50+ stories) in the next 2-3 weeks as discovery finishes — that's the expected transition from "planning artifact" to "delivery tracker."

13. Peirce Phelps Shopware (PPSW) ​

Grew from 0 to 16 stories (still 0 Done) as discovery starts. Prior analysis noted PPSW had "zero epics and zero issues of any kind — the Jira project exists but work hasn't started." This week added PPSW-1 through PPSW-9 (all in Discovery status) covering Authentication & SSO (6 stories), Company & Account Management (3 stories), Pricing (1 story), Branches (0 stories — epic exists but no child stories yet), PLP (2 stories), Checkout (2 stories), CMS Migrations (0 stories), Integrations (1 story), and Frontend Utilities (1 story). This is the first actual epic assignment — board transitioned from "project exists but empty" to "discovery in progress" this week.

Feature parity shows 41 Done features (identical to Homans), but status_counts reveal shared boilerplate dependency. Peirce's 41 Done features (PLP, PDP, Cart, Checkout, Auth, Branch Management) match Homans exactly, confirming both BUs benefit from the same shared boilerplate work (Pablo's 104 peirce-frontend commits + Lino's 14 peirce-frontend commits = 118 Peirce-specific commits this week, all targeting shared features). Peirce diverges from Homans on unique integrations: Card Connect (Not Started — Homans uses Authorize.net), Punchout (Not Started), and Submit Quote from Checkout (In Progress — unique to Peirce per SXSW-1361/1364 work flagged in commit activity).

Artem's 16 commits target SXSW-1361/1364 (Submit Quote from Checkout). These commits include "SXSW-1361-SXSW-1364: add placeQuoteRequest mutation resolver with QuoteRequestDataSource" — this is Peirce-specific domain work (quote submission) that will eventually surface as PPSW board progress, but currently tracked as SXSW platform work because it's being built in the ecommerce-supergraph repo, not peirce-shopware or peirce-frontend. This is a concrete example of why PPSW shows 0 Done stories despite 118 commits — the work is real, but tracked elsewhere until BU-specific decomposition completes.

Board will remain 0% until discovery completes, similar to Homans. The 16 stories added this week (vs. 0 prior) signal discovery is underway, but all 9 epics remain in Discovery status with no child stories closed yet. Watch for board population (16 → 50+ stories) and first story closures in the next 2-3 weeks as discovery finishes.

Review Pipeline Aging ​

110 tickets in review/testing pipeline, median age 5 days. Down from 116 prior week, suggesting pipeline velocity improved. Breakdown by status:

  • Active Development: 19 tickets, median 4 days, max 82 days (SXSW-1125 — now closed, no longer in pipeline)
  • Code Review: 17 tickets, median 5 days, max 6 days (healthy)
  • In Review: 12 tickets, median 5 days, max 40 days (SXSW-1173 — outlier needs escalation)
  • In QA: 21 tickets, median 11 days, max 26 days (CESW-1280/1646 — 26/21 days, both CE-specific)
  • Development Complete: 15 tickets, median 11 days, max 20 days (SXSW-1093/543/449 — all 20 days, awaiting final deployment)

Oldest outliers: SXSW-1173 (In Review, 40 days — ERP account mutations, no visible blocker), GSHOP-139/136/123/108 (QA, 34 days each — all Nikolay-assigned, batch-blocked by upstream dependencies per prior analysis), CESW-1344 (Under Code Review, 33 days — punchout auth token, Scott-assigned). The 40-day SXSW ticket is the most concerning — either escalate or mark as blocked if dependencies exist outside the ticket graph.

Stale >30 days: 9 tickets, up from 4 prior week. The increase is entirely due to GSHOP batch (4 tickets all aged together from 27 → 34 days) — not a velocity regression, just natural aging of a known blocker cluster. SXSW-1173 (40 days) is the new oldest outlier after SXSW-1125 (82 days) closed this week.

Repository Activity & Team Velocity ​

1,787 commits this week across 25 contributors, up from ~1,200 prior week. Top contributors:

  1. Pablo Romero: 395 commits (22% of total), 27% Homans, 26% Peirce, 24% Watsco boilerplate — drives shared Checkout/PDP work
  2. German Berselli: 183 commits (10%), 31% Watsco, 23% each Baker/Peirce/Homans — FBT carousel, salesperson notes, reference-only UI
  3. Gabriel Guzmán: 159 commits (9%), 47% Watsco, 18% each Baker/Peirce/Homans — checkout credit card forms, mutation cache writes
  4. Damir Korpar: 87 commits (5%), 55% Watsco, 15% each Baker/Peirce/Homans — AHRI matchup/details, promo codes
  5. Emil Stewart: 84 commits (5%), 62% CE, 38% Watsco — AHRI fixes, rewards checkout, performance profiling

Team velocity by layer:

  • Frontend: 1,487 commits (83%) — Pablo/German/Gabriel dominate, all targeting Checkout/PDP/Cart
  • Graph: 234 commits (13%) — Emil/Adrian/Blake/Paul drive domain API work
  • Shopware: 155 commits (9%) — Nathan/Emil/Blake/Paul/Nick drive plugin updates

Homans/Peirce commit activity (247 total) confirms feature parity progress. Both BUs show 0% board completion but 41 Done features in parity matrix — the 247 commits (107 Homans + 140 Peirce-specific) targeting shared boilerplate work explain the parity-vs-board gap. Board decomposition lag is intentional per prior program_notes, not a tracking failure.

ECMD velocity (210 commits, +41 stories) validates reallocation success. Sebastian's 123 commits + Damir's 87 = 210 total, driving +41 stories closed = 5.1 commits/story (normal range for frontend work). This is the intended effect of Jul 28 reallocation (Sebastian/Gabriel moved to ECMD/Baker to fix board-vs-reality gap) — board movement now reflects commit activity again.

mermaid
gantt
    title Projected Completion (based on current velocity)
    dateFormat YYYY-MM-DD
    todayMarker stroke-width:2px,stroke:#ef4444
    section Core Platform
    SXSW (Sep 30 target)   :crit, 2026-09-08, 2026-11-24
    section Business Units
    CE Shopware (final 2%) :active, 2026-09-08, 2026-09-22
    Baker Shopware         :2026-09-08, 2026-12-30
    ECMD Shopware          :2026-09-08, 2027-03-15
    Gemaire Shopware       :milestone, 2026-09-08, 2027-06-01
    Homans Shopware        :milestone, 2026-09-08, 2027-06-01
    Peirce Shopware        :milestone, 2026-09-08, 2027-06-01

Projection notes:

  • SXSW: 259 stories ÷ 12/week = 21.6 weeks → Nov 24 completion (misses Sep 30 target by 8 weeks unless velocity scales or scope reduces via backlog tagging)
  • CE: 17 stories ÷ 1.2/week (recent velocity) = 14 days → Sep 22 completion (assumes Deploying pipeline clears)
  • Baker: 169 stories ÷ 8/week = 21 weeks → Dec 30 completion (on track for Q4)
  • ECMD: 289 stories ÷ 5.9/week (recent velocity) = 49 weeks → Mar 15, 2027 (scope growth risk: +12 net this week)
  • Gemaire/Homans/Peirce: No measurable velocity yet (board decomposition incomplete) — Jun 2027 is placeholder based on ECMD's velocity as upper bound, but could accelerate dramatically once discovery completes and shared boilerplate work becomes visible in board progress