DDEL · Project Check-in

DFD Delivery Matrix: Project Check-in

Report date: Thursday 16 July 2026

Client: Daylesford (DFD)

PM: Rebecca Ebdon-Roper · Tech Lead: Ian Rushton

Float project: Delivery Matrix (DFD-DM, 1 Apr – 31 Aug 2026, 516 hr budget)

Jira: DDEL board 695 · Brief: 2026 New Delivery Solution

🟡 Amber

🚀 The Delivery Matrix went LIVE on 15 July. The core delivery subsystem was deployed to production (three prod deploys) after a full QAT/UAT bug-fix push — the primary project goal is achieved, ~2 weeks after the desired end-June date. Two things keep it amber, not green: multishipping was deliberately disabled for launch (not UA-tested — needs its own UAT + relaunch plan), and spend is now 109% of the 516h Float (560.8h) with that relaunch, slot counting and post-launch support still ahead. A commercial reconciliation + a multishipping plan are the two open threads.

What's gone well since the previous report

🚀 Go-live achieved — 15 July. The core Delivery Matrix subsystem is now in production. #devops-daylesford shows the launch sequence: a final staging deploy that morning, then three production deploys (12:18, 14:12, 14:23 BST) on Wednesday 15 July. Rebecca's Go Live — Delivery Matrix runbook coordinated the launch, timed for Ian Rushton's return, with the client confirming it didn't need to be first thing.

Clean pre-launch bug sweep. A large batch of QAT/UAT fixes closed on 14 July — DDEL-86, -91, -93, -97, -99, -103, -106, -108, -109, -111, -121 plus DDEL-50 (manual test scenarios) — clearing the decks the day before launch. DDEL-128 closed on go-live day itself.

Sensible scope call on multishipping. Multishipping was deliberately disabled for go-live because it hadn't completed UA testing — rather than hold the whole launch or ship untested, the core delivery subsystem went live and multishipping is parked for its own UAT + relaunch. A pragmatic, risk-reducing decision.

Client stayed engaged through launch. Daylesford (Hazel, Zoe, Andy McGregor) were active in Jira and the UAT/go-live meetings right up to launch. The 14 July meeting confirmed the go-live window collaboratively.

Deploy cadence proves the pipeline. Beyond launch day, steady staging deploys ran 9, 13, 14 (×3), 15 July — the fix-test-promote loop is healthy and being used for post-launch tidy-ups.

Toggl reflects the launch push. Daylesford Delivery Matrix billable rose to ~49h in the week to 16 July (from ~31h the prior week) — the expected bump for a go-live sprint, then settling.

Issues, risks and watchpoints

Multishipping is built but not live — needs a relaunch plan

Per the Go Live runbook: "MULTI-SHIPPING must be DISABLED for go live. This has not been UA tested and will need a separate plan of action." A substantial, already-built feature (DDEL-55→64, ~10 tickets) is switched off in production. It needs its own UAT pass, a re-enable/deploy plan and a date — otherwise a chunk of paid-for work sits dormant and the "done" story is incomplete. This is now the single biggest open workstream.

Owner: Ian / Rebecca

Float overspent — 561h against 516h (109%)

Cumulative spend is now 560.8h — 109% of the 516h Float, at ~70% calendar, with multishipping relaunch, slot counting and post-launch support still to come. Flagged as over-budget last week and it has continued to climb. The overrun is largely genuine scope growth, but the commercial position is now unavoidable: a top-up or explicit descope must be agreed with Daylesford this week — the project cannot keep drawing on an exhausted budget without a decision.

Owner: Rebecca / Luke → Hazel & Andy

Post-launch stability window

The core subsystem is live but only days old. The first 1–2 weeks are the highest-risk period for a delivery/checkout change — keep a close watch on production for delivery-date, carrier-rate and order-conversion edge cases, and hold capacity for rapid hotfixes. No incidents flagged so far, which is the good news.

Owner: Ian / Zeinab

Six items Blocked; slot counting still unsized

6 tickets Blocked (up from 4). DDEL-66 (client capacity confirmation) still gates DDEL-65 Slot Counting, which remains unsized and outside the budget picture. With go-live behind us, this is the moment to decide slot counting's home — funded top-up or a separate Wave 3 — and to clear the blocked queue.

Owner: Ian / Rebecca → Hazel

Older completed tasks resolved more than 2 weeks ago 66 Done · 365.9 hrs

All Done work resolved >14 days ago — 66 tickets, 365.9h. Spans the Epic 1 discovery wave (15 Apr), the Epic 2 blueprint wave (Apr), the Wave 1 build cluster DDEL-28→40 (28 May), DDEL-42 (5 Jun), the early-June cleanup, and the multishipping features + QAT bug fixes (mid–late Jun). The most significant are listed below; full set in Jira.

Ticket	Summary	Est (hrs)	Spent (hrs)	Resolved
DDEL-42	Ensure all code meets standards and is merged	12.0	20.7	5 Jun 2026
DDEL-36	Admin management of delivery rules and blocked dates on the new model	12.0	17.5	28 May 2026
DDEL-34	Rebuild the customer-facing checkout delivery flow on the new services	18.0	15.3	28 May 2026
DDEL-35	Strip the old Hyvä/Magewire components out of the live checkout flow	6.0	8.1	28 May 2026
DDEL-29	Add one shared place to read and write delivery data	7.0	8.1	28 May 2026
DDEL-37	Get delivery dates working properly in admin order create	10.0	7.6	28 May 2026
DDEL-31	Move quote-level delivery writes into the new shared store	9.0	7.3	28 May 2026
DDEL-33	Stop old static/session code overwriting saved delivery data	6.0	6.5	28 May 2026
DDEL-30	Make the old validation and submit code use the new shared services	7.0	5.8	28 May 2026
DDEL-28	Set up the new delivery module and pull validation into one shared service	8.0	4.6	28 May 2026
DDEL-32	Carrier reads delivery dates from saved data, not static/session	8.0	3.6	28 May 2026
DDEL-39	Clean up the old delivery files the new flow has replaced	4.0	4.3	28 May 2026
DDEL-38	Check downstream exports, C&C and order fields still get what they need	5.0	2.0	28 May 2026
DDEL-40	Check the new setup won't block multi-shipping later	3.0	1.4	28 May 2026
DDEL-27	Add temporary logging to see what the legacy delivery code is still doing	4.0	3.7	21 May 2026
DDEL-46	Fix up and Resync Development environment for DDEL	—	7.5	19 May 2026
DDEL-41	Develo_DeliverySchedule to use Core Validation service check	—	2.5	28 Apr 2026
DDEL-26	Produce implementation blueprint and handoff for build Epics	6.0	6.2	24 Apr 2026
DDEL-25	Define migration and decommissioning strategy for old delivery logic	4.0	2.9	24 Apr 2026
DDEL-24	Define the delivery data, validation and interaction model	4.0	3.5	23 Apr 2026
DDEL-23	Map current code impact: preserve, replace, retire, leave temporarily	4.0	4.5	23 Apr 2026
DDEL-22	Define the target module structure and ownership boundaries	3.0	3.5	23 Apr 2026
DDEL-21	Confirm and document the technical guardrails for the build	3.0	3.6	21 Apr 2026
DDEL-1	Discovery, disablement strategy and impact validation (Epic)	—	1.6	20 Apr 2026
DDEL-19	Internal discovery summary and scope alignment	3.0	2.2	20 Apr 2026
DDEL-12	Validate current customer checkout delivery flows in staging	6.0	11.9	17 Apr 2026
DDEL-16	Validate ERP/export dependency on delivery data	3.0	3.3	17 Apr 2026
DDEL-13	Validate Click & Collect compatibility boundaries	3.0	5.0	17 Apr 2026
DDEL-15	Validate persistence, order conversion and admin visibility of delivery data	4.0	4.0	16 Apr 2026
DDEL-11	Review current module landscape and dependency map	4.0	6.8	16 Apr 2026
DDEL-14	Validate admin / assisted-shop order creation behaviour	4.0	3.9	16 Apr 2026
DDEL-18	Produce disablement impact assessment and migration constraints report	4.0	3.8	15 Apr 2026
DDEL-17	Confirm current exclusions, cutoff and schedule edge-case behaviour	3.0	2.7	15 Apr 2026

Numbers at a glance

Metric	Value	Notes
Float budget	516 hrs	DFD-DM, 1 Apr – 31 Aug, status active
Go-live	LIVE — 15 July 2026	Core subsystem in production; multishipping disabled pending relaunch
Float budget	516 hrs → overspent	560.8h logged = 109% of budget
Jira timeSpent to date	560.8 hrs (≈109%)	Full 123-ticket set; +13.5h since 8 Jul
Calendar elapsed	107 / 153 days (≈70%)	Of the Float window to 31 Aug
Original estimates totalled	242 hrs	Across 123 issues; scope grew well beyond the original 177h baseline
Issues by status	79 Done · 6 In Progress · 4 UAT · 3 QAT · 1 Code Review · 6 Blocked · 24 To Do	+13 Done since 8 Jul (pre-launch bug sweep)
Open bugs	5	DDEL-94, -104, -105, -116 (To Do), -125 (QAT); DDEL-108 fixed
Multishipping	Built, disabled at launch	DDEL-55→64 — needs UAT + relaunch plan
Toggl billable this week	~49h	Up from ~31h — go-live push

Compared with the previous check-in (8 July 2026)

Commitment / risk in last update	Status today
Hold the commercial conversation (budget top-up/descope)	❌ No visible resolution; spend climbed to 109%. Still the top open thread.
Pin the go-live date	✅ Went live 15 July — core subsystem in production.
Decide Slot Counting's home (top-up vs Wave 3)	❌ Still unsized; DDEL-66 still blocked.
Keep the UAT fix loop tight	✅ Clean pre-launch bug sweep — 12 fixes closed 14 Jul.
Reconcile reporting to the full ticket set	✅ Reading full 123-ticket set (2 pages); figures reconciled.
(New) Multishipping deferred at launch	⚠️ Disabled for go-live — needs its own UAT + relaunch plan.

Recommended actions before next check-in

1.Build the multishipping relaunch plan. It's the biggest open workstream — a built feature switched off in production. Ian/Rebecca to scope the remaining UAT, a re-enable/deploy approach and a target date, so the parked work converts to live value rather than sitting dormant.

2.Close out the commercial position — now overdue. Spend is 109% of Float and climbing. Luke/Rebecca to agree a top-up or firm descope with Hazel & Andy this week, covering the multishipping relaunch and slot counting explicitly. This has been the top open thread for two check-ins.

3.Watch production closely for the first two weeks. Delivery/checkout changes carry the most risk immediately post-launch. Hold hotfix capacity and monitor delivery-date, carrier-rate and order-conversion behaviour on live traffic.

4.Decide Slot Counting's home. Unblock DDEL-66 (client capacity sign-off), size DDEL-65, and place it — topped-up budget or separate Wave 3. It can't stay unsized and off the books.

5.Run a short go-live retro. Capture why multishipping missed the UAT window and how the ~2-week slip / budget overrun built up — useful input for the commercial conversation and for scoping the next phase.

Sources

Daylesford Delivery Matrix Technical Specification (Rebecca, 8 May 2026)
DDEL-34 — Build the new checkout delivery flow using the shared delivery services (Jamie, 29 Apr 2026)
DDEL — Delivery Matrix AI Prompt (Ian; latest comment by Yaroslav 14 May 2026)
Project Brief: 2026 New Delivery Solution
Pod To Do List (DI space, updated 1 May 2026)
DDEL Jira issues — full 123-ticket set read via JQL project = DDEL (2 pages), 16 July 2026
Float project DFD-DM (Delivery Matrix Project, Daylesford) — 516 hr budget, 1 Apr – 31 Aug 2026, active
Confluence Go Live — Delivery Matrix runbook — Rebecca, 14 July 2026 (multishipping disabled; launch 15 July)
Confluence "Meeting Updates" (Daylesford space) — 14 July: Hazel, Erin & Rebecca ("Go live on Wednesday")
Confluence Delivery Matrix UAT feedback page — updated 10 July 2026
Confluence Weekly Delivery Report — Week 28 — Sarah Collymore, 16 July 2026
ToggleReportsSlack weekly digests 14–16 July: Daylesford Delivery Matrix 40h → 46h → 49h billable
Slack #devops-daylesford — 3 production deploys 15 July (go-live) + staging deploys 9, 13, 14 (×3), 15 July
Channel access note: Jira / Confluence / Float / Toggl / #devops-daylesford / #develo-project-updates all returned data. Broad Slack date-filtered global searches still return no DDEL hits — channel-scoped queries work; treat as a Slack search quirk, not an outage.