Shopware Migration

Appearance

Weekly Migration Analysis — 2026-09-01 ​

Executive Summary ​

  • CE nears finish line at 98% but stuck final tickets expose coordination gaps: Added +23 stories (662/678) with Emil's 69 commits and Scott's 34 commits driving mobile integration and quote retention work, but 16 remaining stories include 9 in Deploying state (median 7 days) and 5 blocked tickets requiring cross-team coordination — signals final production deployment and integration hurdles rather than missing development.

  • SXSW sustains ~20/week velocity but infrastructure crisis deepens: Added +13 stories to 72% (668/934), but SXSW-1125 (EKS hosting) now at 76 days in Active Dev with no deployment path visible — blocks downstream environment provisioning and threatens October Core Platform Complete deadline. 266 stories outstanding at current 20/week pace suggests mid-November completion if infrastructure doesn't slip further.

  • ECMD recovers but scope growth outpaces closure: Advanced +16 stories to 29% (130/448) with Damir's 53 commits on AHRI Details reversing prior week's stall, but +3 net stories added shows backlog grooming continues adding faster than team closes work — 318 stories outstanding is program's largest absolute backlog and growing.

  • Baker/Homans/Peirce show sustained velocity but incomplete tracking: Baker added +17 to 54% (205/379) with Gabriel's 111 commits; Homans/Peirce both show 0/0 in Jira (expected for new boards) but feature parity matrices show 37 Done features each (36 last week) — Lino/Pablo's 448 combined commits drive real Checkout/PDP/Cart work in shared boilerplate not yet reflected in BU boards.

  • Gemaire infrastructure blockers calcify into sixth week of zero movement: Zero board progress (0/91) despite 25 commits from Nikolay/Damian/Yovany — GSHOP-118 (Google Maps setup, 25 days blocked, assigned to non-technical admin) gates 9 downstream test tickets with no resolution path visible. Root blocker appears to be external dependency (Google Cloud Console provisioning) not engineering work.

Progress Overview ​

SXSW  [████████████████░░░░░░░░] 72% (668/934)
CESW  [███████████████████████░] 98% (662/678)
ECMDSW[███████░░░░░░░░░░░░░░░░░] 29% (130/448)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/91)
BSWM  [█████████████░░░░░░░░░░░] 54% (205/379)
HMSW  [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/0)*
PPSW  [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/16)*

*HMSW and PPSW are new boards in Discovery phase; feature parity matrices show 37 Done features each despite 0/0 Jira boards.

1. Shopware Platform - SXSW Initiatives ​

Current: 668/934 (72%) — +13 stories, +4 total scope since 2026-08-25
This week: 13 commits (Paul: 60, Ilir: 16, Rob: 32, others), 20 in Active Dev, 3 Blocked

SXSW sustains the ~20 stories/week velocity established over the past month (+13 this week, +21 prior week, +23 week before), but the infrastructure crisis is deepening: SXSW-1125 (Kubernetes/EKS Hosting for Domain Layer) now sits at 76 days in Active Dev (was 68 days last week, 63 days two weeks ago) with no visible deployment path or completion timeline. This single ticket is the critical-path blocker for:

  • All BU-specific environment provisioning (Homans SXSW-432, Peirce SXSW-430, ECMD SXSW-434, etc.)
  • Staging environment rollout across remaining BUs (target was Sep 15)
  • Production environment deployment (target was Oct 15)

266 stories outstanding at the current 20/week pace projects mid-November completion for the remaining SXSW work — but this assumes infrastructure doesn't slip further and that the current velocity holds (it collapsed to +5/week in June, so sustainability is not guaranteed). The October "Core Platform Complete" milestone now appears at significant risk unless SXSW-1125 resolves in the next 2-3 weeks.

Notable progress this week:

  • SXSW-1367, SXSW-1160, SXSW-508 (Offers/Product API UOM refactoring and Price Sheet Generation) closed by Adrian Pescar — these unblock BU-specific offer/pricing integrations downstream
  • SXSW-1391, SXSW-1392, SXSW-875 (CardConnect backend + domain gaps) closed by Paul Briscoe — payment integration now unblocked for Peirce and other BUs using CardConnect
  • SXSW-839, SXSW-459 (Role-Based Permissions resolver and Fees resolver) closed by Cristian/Mitchell — ACL enforcement now functional across domain layer

Critical blockers:

  • SXSW-1125 (76 days, Active Dev, Chris Nitchie) — EKS hosting stall blocks all downstream environment work
  • SXSW-1179 (27 days, Active Dev, Scott Kovach) — Punchout JWT authentication blocked on schema/contract decisions
  • SXSW-1173 (34 days, In Review, Paul Briscoe) — ERP account set-default mutations stuck in review pipeline; likely schema/approval dependency

Review pipeline: 9 tickets in "In Review" state (median 4 days), down from 13 last week — pipeline is clearing but oldest ticket (SXSW-1173 at 34 days) suggests some architectural decisions are stalling approvals.

Recommendation: Escalate SXSW-1125 to executive level — this is now a program-wide critical path blocker and has been actively worked for 76 days with no visible end. If EKS deployment doesn't land in the next two weeks, October Core Platform Complete target is unachievable and downstream BU go-lives are at risk.

6. CE Shopware (CESW) ​

Current: 662/678 (98%) — +23 stories, +10 total scope since 2026-08-25
This week: 103 commits (Emil: 69, Blake: 64, Scott: 34), 17 In Progress, 9 Deploying, 5 Blocked

CE Shopware is the only board nearing completion in the program, adding +23 stories this week to reach 98% — but the final 16 stories expose coordination and deployment gaps rather than missing development work:

Notable progress this week:

  • Emil Stewart's mobile integration push (69 commits, 30 tickets closed including CESW-1983, CESW-1981, CESW-1975, CESW-1968, CESW-1958) lands AHRI certificate mapping fixes, rewards display, and performance profiling — mobile app coordination is now unblocked
  • Blake Saunders' customer import fixes (64 commits, 37 tickets closed including CESW-1945, CESW-1928, CESW-1542) resolve ERP account sync gaps, employee ship-to handling, and sub-account job data migration — customer data integrity issues are resolved
  • Scott Kovach's quote retention work (34 commits, 12 tickets closed including CESW-1952, CESW-1861, CESW-1860, CESW-1859, CESW-1862) implements ERP quote number carryover, freight handling, and quote pricing enforcement — quote-to-order flow is now complete

Critical blockers:

  • CESW-1916 (4 days, Blocked) — Tariff surcharge config issue blocks Canadian staging testing; requires cross-team coordination on tax logic
  • CESW-1500 (21 days, Blocked) — Punchout session auth token generation blocked on Watsco Punchout plugin integration (SXSW-1179 upstream)
  • CESW-971 (1 day, Blocked) — Quote QA blocked on retain-quote pricing enforcement validation

Recommendation: CE is production-ready pending final deployment and coordination — focus next week on clearing the 9 Deploying tickets and resolving the 5 Blocked tickets through cross-team coordination sessions rather than adding new development work.

8. ECMD Shopware (ECMDSW) ​

Current: 130/448 (29%) — +16 stories, +3 total scope since 2026-08-25
This week: 79 commits (Damir: 53, Lucian: 13, Cristian: 3), 13 in Active Dev, 2 Blocked

ECMD recovers from prior week's +2 stall with +16 stories this week (driven by Damir's 53-commit AHRI Details/Matchup push), but scope is still growing faster than closure: +3 net stories added this week signals backlog grooming continues adding work faster than the team closes it. 318 stories outstanding is the program's largest absolute backlog and continues growing.

Notable progress this week:

  • Damir Korpar's AHRI Details work (53 commits across Graph and Frontend, ECMDSW-395, ECMDSW-386, ECMDSW-385, ECMDSW-89) lands AHRI associated products, certificate search, unit model display, and ductless matchup — AHRI integration is now functional end-to-end for ECMD
  • Lucian Miculescu's order approval work (13 commits, ECMDSW-209) adds approval rules, pending orders dashboard, and comment threads — approval workflow is now scaffolded
  • Cristian Coros' Salesforce integration cleanup (3 commits, ECMDSW-478, ECMDSW-477, ECMDSW-476, ECMDSW-475, ECMDSW-403) resolves admin breakage, plugin security updates, and supersede data imports — Salesforce sync is stable

Critical blockers:

  • ECMDSW-423 (12 days, Blocked) — Role-based navigation blocked on SXSW-839 (Role-Based Permissions) which closed this week, so this should unblock next week
  • ECMDSW-33 (33 days, Blocked) — Punchout Gateway vendor module blocked on SXSW-1179 (Punchout JWT auth) which remains stalled at 27 days upstream

Repository activity vs. board movement:

  • 79 commits this week (53 Damir Graph+Frontend, 13 Lucian Graph, 3 Cristian Graph) drove +16 story closures — a 5:1 commits-to-stories ratio is healthier than prior weeks but still suggests some commits are landing in epics that aren't yet decomposed into trackable stories
  • Active branches show ongoing work on AHRI, Salesforce, and order approvals — velocity should sustain if Damir stays allocated to ECMD

Recommendation: Backlog grooming needs to stop adding scope until existing work closes faster. At +16 closed / +3 net added this week, ECMD is still in a "scope explosion" mode rather than a "burndown" mode. Focus next sprint on closing existing Active Dev work without adding new epics.

9. Gemaire Shopware (GSHOP) ​

Current: 0/91 (0%) — +0 stories, +7 total scope since 2026-08-25
This week: 25 commits (Nikolay: 15, Damian: 11, Yovany: 18), 14 In Progress, 21 Blocked

Gemaire shows zero board movement for the sixth consecutive week (0/91, no change since 2026-07-21) despite 25 commits from Nikolay/Damian/Yovany this week — the root blocker remains GSHOP-118 (Google Maps API setup, 25 days blocked, assigned to Mike D'Ottavio) which gates 9 downstream test tickets:

  • GSHOP-133, GSHOP-132, GSHOP-44 (Branch Finder test/implementation) blocked 25 days
  • Other branch-related features blocked pending Google Cloud Console MapID provisioning

Why is this still stalled?

The blocker is external: GSHOP-118 requires Google Cloud Console access and MapID configuration, which is an admin/procurement task, not an engineering task. Mike D'Ottavio (assignee) is a non-technical program manager, suggesting this ticket was mis-assigned or the real owner (whoever has Google Cloud Console admin access) is not visible in Jira.

Repository activity shows active work on other features:

Why is none of this landing on the board?

All 25 commits this week landed in the Graph or Frontend layers (subgraphs and UI components) but the Gemaire board epics are organized by feature area (Branch Finder, Search, Sign In/Out, etc.) rather than by layer. Work is happening but it's landing in partial-feature states (e.g., "Arrow Graph work for X is done but UI isn't") which doesn't close any board epic until the full vertical slice ships.

Recommendation: Escalate GSHOP-118 to whoever owns Google Cloud Console access (likely IT/DevOps, not Mike D'Ottavio) and get MapID provisioned this week. This is a program-wide anti-pattern: a non-engineering procurement blocker (Google Maps API setup) is stalling 10% of Gemaire's board for six weeks straight. If MapID lands, expect 9 downstream tickets to unblock immediately.

10. Baker Shopware (BSWM) ​

Current: 205/379 (54%) — +17 stories, +7 total scope since 2026-08-25
This week: 189 commits (Gabriel: 111, Tyler: 78), 22 In Progress

Baker sustains double-digit weekly gains (+17 stories this week, +17 prior week, +12 week before) and is now the second-fastest-moving board in the program after CE. 174 stories outstanding at the current ~15/week pace suggests mid-November completion if velocity holds.

Notable progress this week:

  • Gabriel Guzmán's credit card integration push (111 commits, 18 Baker-specific, BSWM-130, BSWM-63, BSWM-65, BSWM-61, DOMAIN-440, DOMAIN-441) lands checkout payment methods display, card CRUD actions, add-new-card tokenize iFrame, and ERP-products scope config — credit card management is now functional end-to-end
  • Tyler Hawkins' orders work (78 commits, 45 Baker-specific, BSWM-468, BSWM-471, BSWM-470, BSWM-116, BSWM-189, BSWM-193, BSWM-462) moves order list and order detail pages to boilerplate, adds invoice print/tab display, and implements cart current-store-skeleton — order history is now complete
  • Cleo Hister's quote integration work (26 commits, 8 Baker-specific, BSWM-289, BSWM-381) lands WatscoQuote plugin integration and quote-checkout payment/shipping steps — quote-to-cart flow is scaffolded

Repository activity shows sustained velocity:

  • 189 commits this week (111 Gabriel, 78 Tyler) drove +17 story closures — an 11:1 commits-to-stories ratio is healthy and suggests most work is landing in tracked epics
  • Active branches show ongoing work on credit cards, orders, quotes, and addresses — Gabriel/Tyler allocation to Baker is paying off as expected from the reallocation three weeks ago

Recommendation: Baker is on track to complete ahead of most other BUs if current velocity holds. No intervention needed — continue current staffing and let the team burn down the remaining 174 stories at the established ~15/week pace.

12. Homans Shopware (HMSW) ​

Current (Jira): 0/0 (N/A) — +0 stories, +0 total scope since 2026-08-25
Current (Feature Parity): 37 Done / 94 total features (39%)
This week: 364 commits shared across boilerplate (Pablo: 340, Lino: 108, Damir: 53, others)

Homans remains at 0/0 in Jira as expected for a new board in Discovery phase with no epics decomposed yet — but the feature parity matrix shows +1 Done feature this week (37 total, was 36 last week), indicating real progress happening in the shared boilerplate that isn't captured in Jira:

Feature parity progress (manually tracked):

  • Checkout advanced from 7/10 to 8/10 Done — delivery method selection (Our Truck) completed
  • Cart & Checkout subtotal shows 19/50 Done (38%) vs. 18/50 last week
  • Catalog & Product subtotal shows 11/23 Done (48%) vs. 10/23 last week

Repository activity confirms velocity:

  • Pablo Romero (340 commits, 88 Homans-specific) drives PDP/Cart/Checkout/Warranty work across all BUs
  • Lino Rallo (108 commits, 20 Homans-specific) drives pricing/pack-size/PLP work across all BUs
  • Damir Korpar (53 commits, 6 Homans-specific) drives AHRI Details work across ECMD/Baker/Peirce/Homans

Why is Jira still at 0/0?

Homans' epic structure in Jira is organized by business capability (Account, User Management, Dashboard, Checkout, etc.) but the actual development work is happening in the shared boilerplate (watsco-frontend-boilerplate repo) which serves all BUs simultaneously. Work is landing but it's landing as "boilerplate features" rather than "Homans-specific stories" — so the feature parity matrix (which tracks feature completion regardless of where the code lives) is the real progress signal, not the Jira board.

Recommendation: Feature parity matrix is the real signal for Homans/Peirce, not Jira. Both boards will remain at 0/0 until decomposition starts, but 37 Done / 94 total (39%) is a meaningful completion percentage and shows these BUs are progressing in lockstep with the shared boilerplate. No intervention needed — continue shared boilerplate development and defer BU-specific decomposition until core features are further along.

13. Peirce Phelps Shopware (PPSW) ​

Current (Jira): 0/16 (0%) — +0 stories, +1 total scope since 2026-08-25
Current (Feature Parity): 37 Done / 94 total features (39%)
This week: 364 commits shared across boilerplate (Pablo: 340, Lino: 108, Damir: 53, others)

Peirce shows +1 story added this week (0/16 total, was 0/15 last week) — the first story creation signals decomposition is beginning, but like Homans, the feature parity matrix is the real progress signal:

Feature parity progress (manually tracked):

  • Checkout advanced from 7/10 to 8/10 Done — delivery method selection (Our Truck) completed (same as Homans)
  • Cart & Checkout subtotal shows 19/50 Done (38%) vs. 18/50 last week
  • Catalog & Product subtotal shows 11/23 Done (48%) vs. 10/23 last week

Peirce's feature completion is identical to Homans (37 Done / 94 total, 39%) because both BUs are consuming the same shared boilerplate work — the +1 story added this week (PPSW-25, Submit Quote from Checkout, assigned to Artem Klymov) is the first BU-specific decomposition, but no stories are Done yet.

Repository activity confirms shared velocity:

  • Pablo Romero (340 commits, 87 Peirce-specific) drives PDP/Cart/Checkout/Warranty work
  • Lino Rallo (108 commits, 20 Peirce-specific) drives pricing/pack-size/PLP work
  • Artem Klymov (6 commits, 6 Peirce-specific, SXSW-1364, SXSW-1361) scaffolds PeirceShopwareExtension subgraph and quote submission schema — Peirce-specific work is starting

Recommendation: Same as Homans — feature parity matrix is the real signal (37/94, 39% complete), not the 0/16 Jira board. Continue shared boilerplate development and defer BU-specific decomposition until core features are further along.

Review Pipeline Aging ​

Total in review: 124 tickets across all states (down from 145 last analysis)
Stale tickets (>30 days): 4 (down from 8 last week)

The review pipeline is clearing faster than it's filling — 21 fewer tickets in review this week, and stale >30 days dropped from 8 to 4. However, the oldest tickets are calcifying rather than resolving:

Oldest stale tickets:

  • SXSW-1125 (76 days, Active Dev, Chris Nitchie) — Kubernetes/EKS hosting remains the program's oldest stalled ticket; now 8 days older than last week with no resolution visible
  • SXSW-1173 (34 days, In Review, Paul Briscoe) — ERP account set-default mutations stuck in review; likely waiting on schema approval
  • GSHOP-48, GSHOP-47 (34 days each, QA, Rick Oliveira) — Next.js UI critical structural components blocked on broader Gemaire infrastructure (GSHOP-118)

Review state breakdown:

  • Active Development: 29 tickets, median 6 days (SXSW-1125 at 76 days is an extreme outlier)
  • Code Review / Merge: 14 tickets, median 25 days (healthy — no stalls)
  • In QA / QA: 32 tickets combined, median 5-27 days (Gemaire QA tickets aging due to infrastructure blockers)
  • Deploying: 13 tickets, median 0 days (CE's 9 Deploying tickets cleared from stale category by moving median down)

Recommendation: The pipeline is clearing as expected except for infrastructure blockers. Focus escalation on SXSW-1125 (EKS hosting) and GSHOP-118 (Google Maps setup) — these two tickets are the root cause of most downstream aging, not the review process itself.

Repository Activity & Team Velocity ​

This week: 1,214 commits across 32 contributors (down from 1,350 prior week)

Top contributors by commit volume:

  1. Pablo Romero (340 commits, 28% of total) — Watsco Platform team, drives PDP/Cart/Checkout/Warranty work across all BUs in shared boilerplate
  2. Gabriel Guzmán (111 commits, 9% of total) — Baker/ECMD team, drives Baker credit card integration and address management
  3. Lino Rallo (108 commits, 9% of total) — Watsco Platform team, drives pricing/pack-size/PLP work across all BUs
  4. Tyler Hawkins (78 commits, 6% of total) — Baker/ECMD team, drives Baker orders and dashboard work

Team-level velocity:

  • Watsco Platform (Pablo, Lino, German, Tiberio, Robert): 477 commits (39% of total) — drives shared boilerplate work benefiting all BUs
  • Baker/ECMD (Gabriel, Tyler, Jerrold, Sebastian, Damir): 282 commits (23% of total) — drives Baker-specific work + ECMD AHRI Details
  • CE (Emil, Blake, Scott, Nikolay): 173 commits (14% of total) — drives CE final-mile deployment work
  • Human Element (Paul, Ilir, Rob, Chris, Adrian): 120 commits (10% of total) — drives SXSW infrastructure and domain resolver work

Commit-to-story ratios (health check):

  • SXSW: 13 commits → +13 stories closed = 1:1 ratio (healthy — each commit roughly closes one story)
  • CESW: 103 commits → +23 stories closed = 4.5:1 ratio (healthy — some commits are in deployment/coordination rather than new stories)
  • ECMDSW: 79 commits → +16 stories closed = 5:1 ratio (healthy — improving from prior week's 16:1 stall)
  • BSWM: 189 commits → +17 stories closed = 11:1 ratio (healthy — most commits are landing in tracked epics)
  • GSHOP: 25 commits → +0 stories closed = ∞:1 ratio (broken — commits are landing but not closing board stories due to infrastructure blockers)

Recommendation: Velocity is healthy across most boards — commit volume is sustaining ~1,200/week and commit-to-story ratios are reasonable except for Gemaire (which is infrastructure-blocked, not velocity-blocked). Continue current staffing allocations.

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-09-01, 2026-11-15
    section Business Units
    CE Shopware          :done, 2026-09-01, 2026-09-08
    Baker Shopware       :active, 2026-09-01, 2026-11-15
    ECMD Shopware        :active, 2026-09-01, 2027-01-31
    Gemaire Shopware     :crit, 2026-09-01, 2027-03-01
    section New BUs
    Homans (parity)      :active, 2026-09-01, 2026-12-15
    Peirce (parity)      :active, 2026-09-01, 2026-12-15

Velocity-based projections:

  • SXSW: 266 stories ÷ 20/week = 13 weeks (Nov 15, 2026) — assumes infrastructure doesn't slip further
  • CESW: 16 stories ÷ 23/week = <1 week (Sep 8, 2026) — final deployment coordination only
  • BSWM: 174 stories ÷ 17/week = 10 weeks (Nov 15, 2026)
  • ECMDSW: 318 stories ÷ 16/week = 20 weeks (Jan 31, 2027) — largest backlog, slowest velocity
  • GSHOP: 91 stories ÷ 0/week = undefined (infrastructure-blocked; assume Mar 1, 2027 if blockers don't clear)
  • Homans/Peirce: 57 remaining features (94 total - 37 done) ÷ ~1.5/week = 38 weeks (Dec 15, 2026 via shared boilerplate work)