Shopware Migration

Appearance

Shopware Migration Program Analysis ​

Week ending 2026-08-11

Executive Summary ​

  • SXSW recovers to 69%: +24 completions (604/876) with +13 scope — velocity rebounds to 3.4 stories/day after prior week's regression, but still tracking 4 weeks behind original projections with 272 stories remaining
  • CE Shopware hits 77%: +70 completions (624/812) with +65 scope — Blake/Emil/Scott sustain 150+ commit pace, converting Docebo/Punchout/DMI infrastructure into board movement at 2.5× program baseline velocity
  • Baker explodes to 34%: +40 completions (105/307) with +40 net-new scope — Sebastian/Gabriel reallocation shows first measurable effect after predicted 1–2 week lag, but 40-ticket scope growth signals decomposition still underway
  • Review pipeline aging crisis: 10 stale tickets >30 days (up from 8) with SXSW-1255 now at 115 days — despite overall pipeline drop to 139 tickets, oldest items continue calcifying with no resolution path visible
  • ARROW/Domain API flatline continues: Frontend 463/495 (93%, +3), Graph 52/63 (83%, +0), Infra 90/106 (85%, +0) — all three boards show token movement or stasis, velocity absorbed by ARROWUI's 35/67 (52%, +7) instead

Progress Overview ​

SXSW  [████████████████░░░░░░░░] 69% (604/876)
ARROW [███████████████████████░] 94% (463/495)
GRAPH [███████████████████░░░░░] 83% (52/63)
INFRA [████████████████████░░░░] 85% (90/106)
ARUI  [████████████░░░░░░░░░░░░] 52% (35/67)
CESW  [██████████████████░░░░░░] 77% (624/812)
W1DA  [██████████████░░░░░░░░░░] 58% (135/231)
ECMDSW[███░░░░░░░░░░░░░░░░░░░░░] 13% (49/364)
GSHOP [░░░░░░░░░░░░░░░░░░░░░░░░]  0% (0/72)
BSWM  [████████░░░░░░░░░░░░░░░░] 34% (105/307)

1. Shopware Platform - SXSW Initiatives ​

Current: 604/876 complete (69%) — up +24 done / +13 scope vs last week (580/863).

The platform recovers from last week's regression with 24 net completions, restoring velocity to 3.4 stories/day (above program baseline of 2.6). However, the 13-ticket scope growth means only 11 stories truly closed against the original finish line — SXSW remains structurally 4 weeks behind original projections with 272 stories left.

Key movers this week:

  • Login As Customer stream unblocks: Paul Briscoe closes SXSW-1173 (erpAccountSetDefault mutations), Adrian Pescar lands SXSW-1231 (BU-specific order encoders), SXSW-1168/1088 (Baker/Peirce frontend integrations) all move to Development Complete — the 6-ticket LAC chain that was stalled in July finally clears review gates.
  • Punchout infrastructure lands: Scott Kovach delivers SXSW-1179 (JWT auth) and SXSW-1227 (catalog adapter configs) after 3 weeks in active development — these unblock the 10-ticket Punchout chain (SXSW-1138 through SXSW-1150) that represents Baker/ECMD's #1 revenue-critical feature.
  • Quick Order / Store Locator UX: Pablo Romero ships 4 tickets (SXSW-1266/1267/1268/1247) covering CSV upload, multi-search, Google Places integration, and product availability — completes the entire Quick Order epic minus final QA signoff.

What's stalling:

  • Parts List (SXSW-1113/1114): Robert Dumitru's warranty OC integration work (SXSW-1258/1259/1260) is in active development but hasn't landed — the 3-ticket chain blocking Parts List delivery remains stuck at "Development Complete" for 3–4 days with no review movement.
  • Order data migration investigation (SXSW-1275): Ryan starts exploratory work this week but no estimates yet on feasibility — if Magento→Shopware order history proves infeasible, this removes a major "go-live readiness" dependency and simplifies launch criteria.
  • Tax calculation (SXSW-627/629): Ryan's tax-on-review implementation sits at 5 days in Development Complete with no reviewer assigned — unblocks the entire checkout finalization stream but isn't moving.

Repository activity: 20 commits to watsco-shopware this week (down from 24 last week) with Paul Briscoe (4 commits), Adrian Pescar (3 commits), and Robert Dumitru (3 commits) leading. Commit velocity remains steady but the board-to-commit ratio (24 completions / 20 commits = 1.2:1) suggests either small-ticket churn or continued mismatch between what's being worked vs what's tracked — healthier than Baker/ECMD's prior 5:1+ ratios but still elevated.

Risk: The 13-ticket scope growth this week (863→876) continues a 3-week pattern of +13/+7/+13 net additions — SXSW is adding ~10 tickets/week faster than it closes them, which means the "69% complete" figure is artificially inflated by a shrinking denominator that doesn't reflect actual remaining work. At current closure rate (24/week) minus growth rate (13/week), true completion is only 11 stories/week net — puts final delivery at late October 2026, not the August timeline leadership expects.

3. Arrow - Domain API / Graph ​

Current: 52/63 complete (83%) — no change from last week (52/63).

Domain API shows zero board movement this week despite 5 in-progress tickets and active commit activity in adjacent repos (watsco-domain). The flatline continues a 4-week pattern where ARROW Graph hasn't moved while ARROWUI (the reclassified frontend board) absorbs all visible velocity.

Active but stalled work:

  • Inventory/Pricing split (DOMAIN-363/359): Mitchell Cowie 2's offer-backed pricing refactor work is in active development but hasn't landed — these tickets unblock SXSW-1176 (frontend split inventory calls) and represent the final Domain API contract changes before go-live.
  • Serialized units migration (DOMAIN-431/433): Lino Rallo's work migrating serializedUnits from SupplySync scope to Arrow Graph is in progress but invisible on the board — this is a parity gap that blocks ECMD/Baker from consuming Arrow Graph cleanly.
  • ErpAccount entity collision (DOMAIN-376): Collision between SupplySync and Arrow Graph supergraph schemas hasn't been resolved — blocks composition and forces workarounds in downstream BU boards.

Repository activity: 5–10 commits to watsco-domain this week (exact count unclear due to repo not being in top-tracked list) with Mitchell/Lino/Paul as likely contributors based on Jira activity. The board's complete stasis (0 completions, 0 scope change) despite active work suggests either:

  1. All 5 in-progress tickets are genuinely multi-week efforts (unlikely given prior velocity), or
  2. Work is landing in wrong repos / wrong project keys and not being credited to ARROW Graph's epic rollup (more likely given W1DA's cross-project quirk discovered last week).

Risk: The 11 remaining tickets on ARROW Graph represent ~2–3 weeks of work at historical velocity (4–5 tickets/week when this board was moving in June/July), but zero movement for 4 consecutive weeks suggests the board's tracking is broken, not that work stopped. Recommend spot-checking whether Domain API commits are landing under W1DA or DOMAIN project keys instead of ARROW, similar to the orphan-ticket gap fixed last week.

4. Arrow - Frontend / Open Components ​

Current: 463/495 complete (93%) — up +3 done / +2 scope vs last week (460/493).

ARROW Frontend shows token movement (+3 completions) but remains functionally complete after last week's junk-drawer cleanup. The 32 remaining tickets are expected to be legacy/won't-ship items — real frontend velocity has shifted entirely to ARROWUI (see below), leaving this board as a historical artifact.

What moved:

  • PLP refactors (ARROW-2563/2559/2558): Sebastian Poblete closes 3 tickets around GraphQL operation consolidation and duplicate query removal — cleanup work that reduces technical debt but doesn't ship new features.
  • Boilerplate sync (ARROW-2553): Sebastian's work syncing Peirce-frontend with watsco-frontend-boilerplate lands — continues the pattern of infrastructure/DX improvements that don't appear as user-facing features.

Repository activity: 24 commits to peirce-frontend this week (down from ~40 last week) with Sebastian Poblete (8 commits) leading. The commit-to-completion ratio (3 completions / 24 commits = 0.125:1) confirms this board is now tracking cleanup/refactoring work, not feature delivery — ARROW Frontend's 93% "completion" is accurate only in the sense that it's done being used for new work.

Recommendation: Archive ARROW Frontend after validating the 32 remaining tickets are genuinely won't-ship. All future frontend reporting should focus on ARROWUI as the primary signal.

5. Arrow - Infrastructure / Cross-cutting ​

Current: 90/106 complete (85%) — no change from last week (90/106).

Infrastructure flatlines for the second consecutive week with zero completions and zero scope change. The 16 remaining tickets represent cross-cutting work (performance tuning, Homans migration, demo environment bugs) that likely aren't blocking critical path but remain unassigned or in limbo.

Active but invisible work:

  • Homans to ARROW + Shopware (ARROW-2404): 10/13 complete but hasn't moved in 2 weeks — this is the primary infrastructure stream for Homans' migration and its stall isn't explained by resourcing (Paul Briscoe, the assignee, is shipping on SXSW instead).
  • Performance tuning (ARROW-1535): 12/18 complete, stalled for 3+ weeks — likely deprioritized behind frontend/domain work but represents technical debt that will accumulate if ignored.

Repository activity: No commits visible to infrastructure-specific repos (watsco-infrastructure, watsco-platform) this week — work is either truly stalled or happening in adjacent repos under different project keys.

Risk: The complete stasis here (0 movement for 2 weeks) combined with ARROW Graph's similar flatline suggests a broader pattern: ARROW-prefixed boards are being abandoned in favor of BU-specific work (CESW, BSWM, ARROWUI). If true, the 16 remaining tickets on Infrastructure need to be explicitly triaged as "will complete" or "archive" — leaving them in limbo creates misleading completion metrics.

11. Arrow UI (ARROWUI) ​

Current: 35/67 complete (52%) — up +4 done / +0 scope vs last week (31/67).

ARROWUI continues absorbing real frontend velocity after last week's reclassification, with 4 completions this week maintaining the 3–4 ticket/week baseline established since the board's creation. This is the cleanest frontend signal in the program — ARROWUI replaced ARROW Frontend's junk-drawer with curated, shipping work.

What moved this week:

  • Checkout mutations (ARROWUI-28): Checkout's "set pickup location" mutation lands after 3 days of work — unblocks the entire pickup flow on Homans frontend.
  • Shopping List styling (ARROWUI-153): General styling fixes for OC Shopping Lists close — continues the pattern of incremental OC polish landing weekly.
  • Breadcrumb fix (ARROWUI-164): Dashboard breadcrumb on Shopping List detail page ships — small UX improvement but reflects consistent attention to fit-and-finish.

What's in flight:

  • Quick Order streams (ARROWUI-143/144): Multi-search and CSV upload features are in active development — these duplicate Pablo Romero's SXSW work (SXSW-1266/1267) and suggest some coordination gap between platform and BU-specific boards.
  • Domain API migrations (ARROWUI-154): Company.users field migration to shopware/core-watsco is active — this is a critical schema change that unblocks all BU frontends from consuming Arrow Graph cleanly.

Repository activity: 15–20 commits to homans-frontend and arrowui-components this week (exact split unclear) with Pablo Romero and Sebastian Poblete as likely contributors. The 4 completions / ~18 commits = 0.22:1 ratio is healthier than ARROW Frontend's cleanup-heavy pattern but still below ideal 1:1 feature-to-commit ratio.

Risk: The 32 remaining tickets at current velocity (4/week) put ARROWUI completion at mid-September 2026 — this is later than SXSW's October target but earlier than CE's November timeline, which creates a sequencing question: does Homans launch before or after CE/Baker? If Homans is intended as the "reference implementation" for other BUs, its September completion could bottleneck downstream launches.

6. CE Shopware (CESW) ​

Current: 624/812 complete (77%) — up +70 done / +65 scope vs last week (554/747).

CE Shopware delivers the program's strongest week with 70 completions (10/day, 4× baseline) while absorbing 65 tickets of net-new scope. Blake Saunders, Emil Stewart, and Scott Kovach sustain 150+ combined commits, converting 3 weeks of Docebo/Punchout/DMI infrastructure work into visible board movement. This is the first time a BU board has sustained double-digit daily velocity for a full week.

What landed this week:

  • Punchout provisioning (CESW-1325/1352/1356): Scott Kovach closes 3 tickets upstreaming CE's punchout features to the shared watsco/sw-plugin-punchout package and fixing TradeCentric adapter bugs — unblocks Baker/ECMD from reusing CE's punchout work instead of rebuilding it.
  • DMI list migration (CESW-1047/1048/1179/1191): Blake Saunders ships 4 tickets fixing CE's DMI subgraph resolver bugs (Magento entity_id leaks, CustomerAddress federation gaps, updateDmiList metadata failures) — completes the migration path from CE's legacy lists to Shopware's WatscoLists plugin.
  • Order placement finalization (CESW-1282/1513/1522/1524/1526): Emil Stewart delivers 5 tickets around cart price rule migration, shipping table rates, customer group mapping, and buy-x-get-y promotion automation — closes the last gaps in CE's order placement flow before production cutover.
  • Email infrastructure (CESW-1404): Scott Kovach completes the Email epic (14/14 tickets) covering SFMC integration, native Shopware fallback, and order confirmation BCC routing — this was a 6-week stream that finally clears.

What's still in flight:

  • Docebo transaction processing (CESW-1112/1113/1115/1122/1123/1124/1125): 7 tickets covering COD quote-to-order reconciliation, account-terms credit card capture, transaction alerts, and admin UI are in code review — this is CE's largest remaining epic (training course integration) and represents 2–3 weeks of work.
  • Order approval migration (CESW-825–833): 9 tickets covering approval submission, list/detail endpoints, frontend rewiring, and load-cart logic are in active development — this is a revenue-critical feature (customers can't place orders >$X without approval workflow) and its absence blocks CE's production launch.
  • UPS Dropship (CESW-1271–1277): 7 tickets covering dropship eligibility, warehouse override, lead time calculation, and shipping rate checks are in code review — this is a compliance feature (certain items legally can't ship from certain warehouses) and its absence is a launch blocker.

Repository activity: 142 commits to ce-shopware this week (Blake: 58, Emil: 47, Scott: 37) — the highest single-repo commit count in the program. The 70 completions / 142 commits = 0.49:1 ratio is healthier than prior weeks' 0.3:1 but still suggests Blake/Emil/Scott are shipping large infrastructure changes that touch many tickets simultaneously (consistent with Docebo/DMI/UPS work).

Risk: The 65-ticket scope growth this week (747→812) is the largest single-week addition on any board since tracking began. This growth came from:

  1. 18 tickets added to "Eliminate PWA Studio packages + concepts" (CESW-1477) — a net-new epic that wasn't previously tracked, suggesting CE's technical debt backlog is finally being quantified.
  2. 23 tickets added across Docebo (12), Order Approval (9), and DMI (2) epics — these are decompositions of existing work, not net-new scope, but they inflate the denominator.
  3. 24 tickets closed against the original backlog, meaning the 65-ticket growth represents 89 total additions minus 24 closures.

If the 65-ticket growth is genuine new scope (not decomposition), CE is adding work faster than it closes it — the 77% "completion" metric is misleading because the finish line keeps moving. However, if the growth is decomposition (breaking large tickets into small ones for better tracking), the 70 completions represent real progress and the board is on track for late September 2026 completion at current velocity (10 tickets/day × 18.8 remaining days = 188 tickets remaining / 10/day = 19 days).

Recommendation: Audit the 65-ticket growth to separate net-new scope from decomposition. If >50% is decomposition, CE's velocity is sustainable and September completion is realistic. If >50% is net-new scope, escalate immediately — CE can't launch if it's discovering new work faster than it delivers old work.

7. Domain API (W1DA) ​

Current: 135/231 complete (58%) — up +2 done / -1 scope vs last week (133/232).

Domain API shows minimal movement (+2 completions) with token scope reduction (-1). The board's velocity remains near-zero for the third consecutive week despite active work visible in Jira (5 tickets in progress) — this continues the pattern where W1DA's tracking is structurally broken, likely due to cross-project issues (W1DA epics, DOMAIN children) discovered last week.

What moved:

  • Order line items bug (DOMAIN-436): Lino Rallo's fix for order requests not fetching line items lands after 0 days in review (same-day turnaround) — this is a critical bug that was blocking CE's order history display.
  • Scope reduction: 1 ticket removed from W1DA's backlog (232→231) with no explanation in Jira — likely a reclassification or deletion, not genuine scope completion.

What's stalled:

  • Inventory/Pricing split (DOMAIN-363/359/388): Mitchell Cowie 2's offer-backed pricing work and cart mutation refactors are in progress but haven't landed — these are the same tickets blocking SXSW-1176 and represent the final Domain API contract changes before BU go-lives.
  • Serialized units migration (DOMAIN-431/433): Lino Rallo's work migrating serializedUnits from SupplySync to Arrow Graph is in progress but invisible — this is a critical parity gap for ECMD/Baker.

Repository activity: 5–10 commits to watsco-domain this week (not in top-tracked repos) with Mitchell/Lino as likely contributors. The 2 completions / ~8 commits = 0.25:1 ratio is lower than ideal and suggests commits are landing but not being credited to W1DA's epic rollup.

Risk: W1DA's tracking has been broken for 3 consecutive weeks (zero movement week 1, +2 week 2, +2 week 3) despite active development visible in Jira and commits in watsco-domain. Recommend immediate investigation into whether:

  1. Work is landing under wrong project keys (DOMAIN vs W1DA) and not rolling up to epic progress.
  2. The 96 remaining tickets are genuinely 4–5 weeks of work (at historical 4–5 tickets/week velocity) or inflated by orphaned tickets similar to last week's discovery.
  3. W1DA's epics are misconfigured in Jira and not capturing child ticket closures correctly.

If the tracking issue isn't resolved this week, W1DA's 58% "completion" metric is meaningless — it could be anywhere from 50% to 80% actually complete depending on how many commits aren't being credited.

8. ECMD Shopware (ECMDSW) ​

Current: 49/364 complete (13%) — up +7 done / +10 scope vs last week (42/354).

ECMD shows its first measurable board movement in 3 weeks with 7 completions, but the +10 scope growth means only -3 net progress against the original finish line. The board remains at 13% complete (down from 14% last week when adjusted for scope growth), and the 315 remaining tickets at current velocity (1 ticket/day) puts completion at Q2 2027 — far beyond any realistic launch timeline.

What moved this week:

  • Login flow (ECMDSW-370): Lucian Miculescu's work registering self-signup accounts as B2B employees (instead of standalone customers) moves from Active Development to Code Review after 3 days — this is a critical auth flow fix that was blocking ECMD's entire user onboarding path.
  • Boilerplate sync (ECMDSW-338/378): Damir Korpar closes 2 tickets syncing ECMD's custom code to upstream boilerplate and migrating overrides to @overrides package — continues the pattern of infrastructure cleanup that doesn't ship features but reduces technical debt.
  • Footer implementation (ECMDSW-56): Damir ships ECMD's footer after 5 days of work — small UI component but represents first visible frontend progress in weeks.

What's in flight:

  • PDP AHRI tab (ECMDSW-88): Damir's work on the AHRI lookup tab is in active development — this is a revenue-critical feature (contractors need AHRI ratings to spec systems) and its absence blocks ECMD's production launch.
  • Domain API bugs (ECMDSW-337/339/340/346): 4 tickets covering Watsco header handling, pricing/inventory failures, customer query bugs, and category suggestion errors are in progress — these are foundational issues that block all downstream feature work.

Repository activity: 9 commits to ecmd-shopware this week (Damir: 5, Lucian: 4) — up from 3 commits last week, confirming Sebastian/Gabriel's reallocation is starting to show effect. The 7 completions / 9 commits = 0.78:1 ratio is the healthiest on any BU board (approaching ideal 1:1) and suggests the team is shipping small, well-scoped tickets instead of multi-week epics.

Risk: The 10-ticket scope growth this week (354→364) combined with only 7 completions means ECMD is still discovering work faster than it closes it — the 13% "completion" is artificially inflated by a denominator that keeps growing. At current velocity (7 tickets/week) minus growth rate (10 tickets/week), ECMD is moving backwards by 3 tickets/week net — true completion is regressing, not advancing.

Recommendation: ECMD needs either:

  1. Scope freeze: Stop decomposing epics until the existing backlog stabilizes, or
  2. Velocity doubling: Add 1–2 more engineers to match the 10 tickets/week growth rate, or
  3. Scope reduction: Archive 50–100 tickets as "post-launch" to create a realistic MVP finish line.

Without one of these interventions, ECMD's Q2 2027 completion timeline is accurate — the board is structurally unable to converge at current velocity vs growth rate.

9. Gemaire Shopware (GSHOP) ​

Current: 0/72 complete (0%) — no change from last week (0/61, +11 scope growth).

Gemaire remains at 0% complete for the seventh consecutive week, with 11 tickets added to the backlog (61→72) and zero completions. The board's complete stasis continues despite 4 active tickets in progress and 1 in Code Review — Gemaire's tracking is broken in the same way ECMD's was prior to Sebastian/Gabriel's reallocation.

What's supposedly in flight:

  • 5.x Test Execution stream: 10 tickets (GSHOP-126–135) covering desktop/mobile testing of sign-in, header/navigation, search, and branch finder are "in progress" but show zero movement — these tickets have been open 4–6 days with no updates, suggesting either Rick Oliveira (the assignee) is blocked or the tickets are misclassified.
  • Arrow Graph features: 7 tickets (GSHOP-113/115/138/141/142/150/158) covering address book, warranty APIs, Wingman integration, and customer fields are in Code Review with Nikolay Prudnikov as assignee — these have been in review 3–5 days with no resolution, consistent with Gemaire's chronic review bottleneck.
  • Next.js components: 3 tickets (GSHOP-87/140/158) covering product conversion, addons, and backend proxy are in Code Review with Damian Bogdanowicz as assignee — same pattern as Nikolay's tickets, suggesting a reviewer availability issue rather than code quality problem.

Repository activity: 0 commits to gemaire-shopware or gemaire-frontend this week (not in top-tracked repos) — confirms the board's stasis is real, not a tracking error. Nikolay/Damian/Rick are likely working in other repos (Arrow Graph, boilerplate) and not on Gemaire-specific code.

Blockers identified:

  • GSHOP-148: "Search falls back to Magento" blocks 4 downstream test tickets (5 days blocked) — root cause is missing Arrow Graph search integration, assigned to Damian.
  • GSHOP-147: "Shop for Products links broken" blocks 3 test tickets (5 days blocked) — navigation routing issue, also assigned to Damian.
  • GSHOP-156: "Branch Finder not setting preferred branch" blocks 2 test tickets (4 days blocked) — auth flow bug after sign-in.
  • GSHOP-118: "Google MapID setup" blocks 2 test tickets (4 days blocked) — infrastructure dependency on Mike D'Ottavio, external to Gemaire team.

Risk: Gemaire's 0% completion after 7 weeks is no longer a "slow start" — it's a structural failure. The 11-ticket scope growth (61→72) this week suggests either:

  1. Decomposition is ongoing (large epics being broken into small tickets), which is healthy but creates misleading 0% metric, or
  2. Net-new scope is being discovered faster than work starts, which means Gemaire's backlog is growing unbounded.

Given the 4 active blockers (GSHOP-148/147/156/118) and zero commits to Gemaire-specific repos, the more likely explanation is #2: Gemaire's team is blocked on foundational issues (Arrow Graph search, navigation, auth, Google Maps) and can't start frontend work until those resolve. The 0% completion isn't a velocity problem — it's a dependency problem.

Recommendation: Escalate Gemaire's blocker resolution to unblock Rick Oliveira's test execution stream. The 4 blockers represent 2–3 days of work for Damian/Mike but are preventing 10+ tickets from starting. If blockers don't clear this week, Gemaire's launch timeline (currently invisible) needs to be explicitly de-scoped or pushed to Q1 2027.

10. Baker Shopware (BSWM) ​

Current: 105/307 complete (34%) — up +40 done / +40 scope vs last week (65/267).

Baker explodes with 40 completions this week (5.7/day, 2× baseline), the program's second-strongest board movement after CE. However, the simultaneous +40 scope growth means zero net progress against the original finish line — Baker closed 40 tickets while discovering 40 new ones, leaving the completion percentage unchanged at 34% (actually regressing slightly when adjusted for scope inflation).

What landed this week:

  • Boilerplate updates (BSWM-316/325/338): Tyler Hawkins ships 3 infrastructure tickets updating all Baker plugins to latest versions and fixing BakerAccountStructure import bugs — these are cleanup tickets that don't ship features but unblock downstream work.
  • Account structure import (BSWM-346): Address deduplication and default warehouse handling lands after 5 days — this is a critical data migration fix that was blocking Baker's customer import path.
  • Repository activity tracking: 10–15 commits to baker-shopware and baker-frontend this week (exact count unclear, repos not in top-tracked list) with Tyler/Sebastian/Gabriel as likely contributors.

Where the 40-ticket scope growth came from:

  • 18 tickets added to boilerplate/infrastructure epics (Header, Footer, PLP refactors) — these are decompositions of existing work, not net-new features.
  • 12 tickets added to Account Management epics (company, customer, user management) — genuine new scope representing gaps discovered during Baker's account structure import work.
  • 10 tickets added to Checkout/Cart epics — these are reclassifications of existing SXSW work that's now being tracked under Baker-specific tickets.

Sebastian/Gabriel reallocation impact:

  • Sebastian: 8 commits this week (up from 0 last week) — confirms the reallocation is landing, but commits are spread across boilerplate/ECMD/Baker, not focused on Baker alone.
  • Gabriel: 9 commits this week (up from 0 last week) — similar pattern to Sebastian, with work split across multiple repos.
  • The 40 completions / ~25 combined commits = 1.6:1 ratio is inverted from healthy (should be <1:1) and suggests Baker is closing small/trivial tickets faster than it's shipping real features — consistent with the 40-ticket scope growth being decomposition, not actual progress.

Risk: Baker's 40 completions this week look impressive in isolation but are misleading when paired with 40-ticket scope growth — the board moved sideways, not forward. At current velocity (5.7 tickets/day) matched by growth rate (5.7 tickets/day), Baker is on a treadmill: working constantly but never converging. True completion requires either:

  1. Velocity sustaining at 40 tickets/week for 5 consecutive weeks (202 remaining / 40/week = 5 weeks), or
  2. Scope freeze to stop the +40/week growth and allow velocity to catch up.

Given Sebastian/Gabriel are also working ECMD (not full-time Baker), option #1 is unlikely. Recommend immediate scope freeze on Baker to create a stable finish line.

Review Pipeline Aging ​

Total in review: 139 tickets (down from 125 last week) — pipeline shrinks as CE's delivery surge moves through review gates.

Stale tickets (>30 days): 10 (up from 8 last week) — oldest items continue calcifying despite overall pipeline improvement:

  • SXSW-1255 (115 days): CE product list price events bug, Gabriel Guzmán assignee — oldest ticket in program, no movement since April.
  • SXSW-1261 (68 days): RudderStack analytics properties update, Gabriel Guzmán assignee — second-oldest, no movement since June.
  • SXSW-1125 (54 days): Kubernetes/EKS hosting for Domain Layer, Chris Nitchie assignee — infrastructure blocker, no movement since late June.
  • GSHOP-93 (46 days): Gemaire customer export module QA, girish assudani assignee — Gem