DDEL · Project Check-in

DFD Delivery Matrix: Project Check-in

Report date: Tuesday 30 June 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

Into UAT — the build is done, the date has moved. Both 18 June red risks cleared: the two ~2× features (DDEL-67 Adyen split orders, DDEL-70 multi-address frontend) both shipped, QAT is live (5 journeys in QAT, Zeinab's QAT Checklist published today) and UAT handover is set for Wednesday 1 July. The amber is now about the slip: the desired end-of-June go-live is being met as a UAT hand-off, not a launch — realistic go-live is now post-UAT, early–mid July. Burn at ~80% of Float against ~59% calendar (+21pp). 4 items Blocked, 5 QAT bugs open. Controlled, not in trouble — but the date has formally moved.

What's gone well since the previous report

The two red-flagged features both shipped. DDEL-67 (Adyen split-order routing) closed 19 June at 19.4h, and DDEL-70 (multi-address frontend journey) closed 25 June at 27.1h. These were the two ~2× overruns gating QA on 18 June — both are now done, which is what unlocked the move into testing.

QAT is live. Five journeys are in QAT status and Zeinab published the DFD - Delivery Matrix QAT Checklist today (30 June) — a detailed customer-journey test script (standard delivery, fresh future-date, split/consolidated delivery, C&C, admin order creation, date-blocking, data integrity). The "QAT not started" risk that drove the 18 June amber is resolved.

UAT handover scheduled for Wednesday 1 July. Per the 30 June client meeting note (Zoe, Hazel, Erin, Rebecca): "Delivery Project: handing over for UAT on Wednesday. Will share UAT document alongside test scenarios." Rebecca has stood up a Delivery Matrix UAT feedback page, already capturing multi-shipping observations with priorities and ticket links.

QAT/UAT defect loop is working. Bug tickets are being raised and closed quickly — DDEL-82, -83, -87, -92, -95, -98 (QAT fixes) all resolved 24–25 June, 3–10h each. Five bugs are currently open and in-flight rather than piling up: a healthy sign the test pass is finding and clearing issues in real time.

Team scaled up on QA. Sebastian Tracz now holds 6 tickets (Playwright + QAT), Ian 17, Shahbaz 5. The bench widened exactly as the work shifted from build to test.

Toggl activity at sustained peak. The Daylesford Delivery Matrix project logged 232h 48m billable in the week to 30 June (running total across the digest: 164h → 182h → 199h → 215h → 232h across 23–30 June) — the heaviest fortnight of the project as the build-to-UAT push landed.

Deploys steady. #devops-daylesford shows staging deploys 22 June and 30 June (×2), production deploys 23 and 24 June — regular promotion as QAT fixes land.

Issues, risks and watchpoints

Go-live date has effectively moved past end of June

Daylesford's desired go-live was end of June — i.e. today. It is being met as a UAT handover (Wed 1 July), not a live launch. That's a controlled, sensible gate, not a failure — but the original date is missed and a revised go-live (post-UAT, realistically early–mid July depending on UAT findings) needs to be explicitly agreed and communicated to the client. The +2-month Float buffer to 31 Aug means there's room; the risk is expectation management, not capacity.

Owner: Rebecca (client date) / Ian

Four items Blocked — UAT could surface more

Four tickets are Blocked (up from two). DDEL-66 (client capacity confirmation) still gates the DDEL-65 Slot Counting epic; DDEL-56 (multi-address UX) remains blocked. As UAT opens Wednesday, expect more client-dependent items — keep the blocked queue visible so it doesn't quietly become the long pole into go-live.

Owner: Rebecca → Hazel / Zoe

Burn at 80% of Float; estimate no longer describes the project

415h of 516h Float spent (80%) against ~59% calendar elapsed — gap steady at +21pp. Spend is now 415h vs 218h original estimate (~197h over). The overrun is mostly genuine scope growth (multishipping, slot counting, the QAT/UAT bug stream — none in the original 177h baseline), not slippage, but at 80% burn with UAT + bugfix + slot counting still ahead, the remaining ~100h of Float to 31 Aug is now the real constraint. A re-baseline / top-up conversation should happen this week, before slot counting (DDEL-65) is sized.

Owner: Rebecca / Ian

Slot Counting (DDEL-65) still not sized — and gated

The slot-counting mini-epic has had no real movement since early June because it's waiting on DDEL-66 client capacity sign-off. It's a known piece of remaining scope sitting outside the burn picture. If it's in for this phase, it needs sizing against the remaining Float now; if it's a Wave 3 / separate budget, say so explicitly.

Owner: Ian / Rebecca

Carried-over admin: DDEL-3 epic status & Toggl tagging

Two long-running items persist. The Jira epic count has collapsed to 1 (consolidation) but epic-level status hygiene is still loose. And the Toggl weekly digest still books the full project total (232h 48m this week) as "No ticket assigned" at project level — detailed reports resolve to tickets, but the morning bot view can't attribute. Both are low-effort, low-urgency, but have outlived several check-ins.

Owner: Ian (epic) / Mike (Toggl)

Older completed tasks resolved more than 2 weeks ago 45 Done · 233.4 hrs

All Done work resolved >14 days ago — 45 tickets, 233.4h. 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 standards/merge (5 Jun), and the early-June cleanup batch (DDEL-20, -44, -48, -51, -53, -54, resolved 9–11 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
Desired go-live	End of June 2026 (today)	Being met as UAT handover, not launch; revised go-live early–mid July
UAT handover	Wednesday 1 July	Per 30 June client meeting; UAT doc + scenarios to be shared
Calendar elapsed	91 / 153 days (≈59%)	Of the full Float window to 31 Aug
Jira timeSpent to date	415.0 hrs (≈80%)	+35.8 hrs since 18 June; ~100h Float remaining; gap +21pp
Original estimates totalled	218 hrs	Across 100 tracked issues (+25 since 18 June — QAT/UAT bugs)
Issues by status	59 Done · 5 Ready for Staging · 5 QAT · 2 UAT · 4 Code Review · 4 In Progress · 4 Blocked · 17 To Do	QAT + UAT both now live (was 0 QAT on 18 June)
QAT / UAT	5 in QAT · 2 in UAT	QAT Checklist published 30 Jun; UAT opens 1 Jul
Open bugs	5	QAT/UAT defect stream; 6 bug fixes already closed 24–25 Jun
Active (non-Done) unassigned	8 / 41 (20%)	Healthy — most active work has named owners
Toggl billable this week	232h 48m	Project peak (+4h 43m unbillable); heaviest fortnight of the project

Compared with the previous check-in (18 June 2026)

Commitment / risk in last update	Status today
Start QAT now — don't wait for the last features	✅ QAT live (5 journeys in QAT); Checklist published 30 Jun; UAT opens 1 Jul.
Have the end-of-June go-live conversation with Daylesford	⚠️ Handover to UAT agreed for 1 Jul. Revised go-live date (post-UAT) still to be pinned.
Confirm DDEL-67 / DDEL-70 are converging	✅ Both shipped — DDEL-67 (19 Jun, 19.4h), DDEL-70 (25 Jun, 27.1h).
Unblock DDEL-66 (capacity) and DDEL-56 (UX)	❌ Both still Blocked; DDEL-66 still gating DDEL-65 Slot Counting.
Re-baseline scope vs Float	⚠️ Not visibly done — now more urgent at 80% burn with ~100h left.
Admin-tidy DDEL-3 Epic / Toggl tagging	⚠️ Epics consolidated to 1; Toggl still "No ticket assigned" at project level.

Recommended actions before next check-in

1.Pin and communicate the revised go-live date. End-of-June is being met as a UAT handover, not a launch. Rebecca to agree an explicit post-UAT go-live with Hazel/Zoe (realistically early–mid July, dependent on UAT findings) and confirm it in writing so the slip is managed, not assumed.

2.Run UAT tightly from Wednesday. Share the UAT doc + scenarios on handover, give Daylesford a clear feedback route (the UAT page is already started), and triage findings daily so defects don't batch up against the go-live date.

3.Re-baseline Float — now urgent. 80% spent with UAT, bugfix and slot counting still ahead and only ~100h left to 31 Aug. Rebecca/Ian to confirm whether the remaining scope fits the 516h or needs a top-up, before sizing DDEL-65.

4.Unblock DDEL-66, then size DDEL-65 Slot Counting. Get Hazel's capacity sign-off so slot counting can be estimated and slotted — either into this phase's remaining Float or explicitly deferred to a Wave 3 / separate budget.

5.Keep the blocked queue visible. Four items Blocked and UAT will likely add client-dependent ones. A standing "blocked" line in the daily standup stops them becoming the silent long pole into launch.

6.Clear the long-running admin. DDEL-3 epic status and Toggl ticket-level tagging have outlived several check-ins — low effort, worth closing so reporting reads true through UAT.

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 — 100 tracked via JQL project = DDEL, 30 June 2026 (query cap; total may be marginally higher)
Float project DFD-DM (Delivery Matrix Project, Daylesford) — 516 hr budget, 1 Apr – 31 Aug 2026, active
ToggleReportsSlack weekly digests 23–30 June: Daylesford Delivery Matrix 164h → 182h → 199h → 215h → 232h 48m billable (+4h 43m unbillable) — project peak
Confluence DFD - Delivery Matrix QAT Checklist — Zeinab, published 30 June 2026
Confluence Delivery Matrix UAT feedback page — Rebecca, 29 June 2026
Confluence "Meeting Updates" (Daylesford space) — 30 June: Zoe, Hazel, Erin & Rebecca ("handing over for UAT on Wednesday")
Confluence Delivery Matrix main client page — Rebecca, updated 26 June (Go-live: End of June 2026)
Slack #devops-daylesford — staging deploys 22, 30 (×2) June; production deploys 23, 24 June
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.