DDEL · Project Check-in

DFD Delivery Matrix: Project Check-in

Report date: Thursday 18 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

Build is essentially complete — but go-live is tight. The multishipping feature set (DDEL-55→64) is shipped and DDEL-42 closed, so the heavy build lift is done. The amber rating is about the end-of-June go-live: the 8-journey QAT suite (DDEL-73→81) was only just created and hasn't started, two items are Blocked (DDEL-56 UX, DDEL-66 client capacity), and two active tickets (DDEL-67, DDEL-70) are running ~2× estimate. Burn is now ~73% of Float against ~52% calendar — a +21pp gap, widening. Delivery quality is strong; the risk is timeline and unstarted QA against a ~12-day runway.

What's gone well since the previous report

The multishipping feature set is done. Of the 11-ticket cluster (DDEL-55→64), 10 are now Done — all seven features (F1–F7: per-shipment context, persistence, delivery dates, rule engine, carrier read path, rate refresh, service contracts/docs) plus spikes S1 and S3. Only the S2 UX design spike (DDEL-56) remains, and it's Blocked. This was the bulk of Wave 2 and it has landed in two weeks.

DDEL-42 finally closed. The standards/merge ticket that was flagged red for two consecutive check-ins resolved on 5 June at 20.7h vs 12h estimate. The overrun is locked in but the blocker is cleared.

Wave 1 cleanup fully shipped. The whole post-Wave-1 queue closed out 9–11 June: DDEL-20 (brief review), DDEL-43 + DDEL-49 (Playwright testing, 12.7h + 22.9h — Sebastian Tracz's scaffolding), DDEL-48 (client tech-spec review), DDEL-51, DDEL-53, DDEL-54, plus DDEL-44 (onboarding). The Code Review queue that was building on 4 June has drained.

Split-order payment path under active build. DDEL-67 ("Plugin for Develo DeliveryCore to route multishipping quotes into split order creation (Adyen)", Yaroslav) and DDEL-70 ("Get the multi-address journey (frontend UI) working end-to-end", Shahbaz) are both In Progress — the last substantive feature work before QA. Both are overrunning (see risks).

QAT structure is now defined. A full 8-journey QAT suite was created 16 June: DDEL-73 ("QAT: DDEL-3 delivery subsystem — key user journeys") with sub-tasks DDEL-74→81 covering standard delivery, fresh-item future date, split delivery, consolidated delivery, Click & Collect, admin/assisted-shop order creation, date-blocking and order data integrity. Clear test plan; execution not yet started.

Branch hygiene confirmed. DDEL-71 and DDEL-72 (verify DDEL-3 code merged into the DDEL-4 epic branch, and staging running the latest) both closed 16 June — good discipline keeping the two epic branches reconciled before QA.

Toggl activity at project peak. The 18 June ToggleReportsSlack weekly digest shows 107h 17m billable + 7h 52m unbillable on Daylesford Delivery Matrix — the highest weekly total of the project, reflecting the multishipping push. (Still aggregating as "No ticket assigned" at project level in the bot view — see risks.)

Deploys steady. #devops-daylesford shows staging deploys 8, 12, 15, 16 (×2), 17 June. Regular cadence into staging as features complete.

Issues, risks and watchpoints

QAT not started against an end-of-June go-live

Daylesford's desired go-live is end of June (~12 days out). The 8-journey QAT suite (DDEL-73 + DDEL-74→81) was only created 16 June and is entirely To Do — no journey has been executed. With two feature tickets still In Progress and overrunning, the QA window is compressing fast. This is the central go-live risk: either testing starts this week in parallel with the last feature work, or the end-June date needs an explicit conversation with the client. The +2-month Float buffer (to 31 Aug) means launch slippage isn't a budget crisis, but the date expectation needs managing now.

Owner: Zeinab (QA) / Rebecca (client date)

Two active tickets running ~2× estimate

DDEL-67 (Adyen split-order plugin, Yaroslav) is at 19.4h vs 10h (+94%); DDEL-70 (multi-address frontend journey, Shahbaz) is at 23.6h vs 12h (+97%). Both are the final substantive feature work and both gate QA. The split-order/payment integration and the end-to-end frontend journey are genuinely the hardest parts of multishipping, so overrun isn't surprising — but at ~2× they need a check that they're converging, not open-ended.

Owner: Ian / Yaroslav / Shahbaz

Two items Blocked — both need client input

DDEL-66 ("Client confirmation: delivery capacity requirements") is Blocked awaiting Daylesford sign-off — and it gates the DDEL-65 Slot Counting mini-epic, which has had no movement since 4 June. DDEL-56 (S2 multi-address UX design) is also Blocked. Both need unblocking to avoid becoming the long pole after the core build lands.

Owner: Rebecca → Hazel / Zoe

Burn gap to calendar parity now +21pp

73% of Float spent (379h of 516) against ~52% calendar elapsed — the gap has widened from +16pp to +21pp. Total spend is now 379h vs 233h original estimate, ~146h over — beyond the 60–90 hr contingency line. The scope genuinely grew (multishipping + slot counting were not in the original 177h), so this is partly re-scoping rather than pure overrun, but it means the original estimate no longer describes the project. Worth a re-baseline conversation: confirm the 516h Float still covers the expanded scope to 31 Aug.

Owner: Rebecca / Ian

DDEL-3 Epic STILL "To Do" despite 23.4h logged

Carried over fourth week running — now with 23.4h logged at epic level (up from 18.3h) while nearly all children are Done. Pure admin, but its persistence suggests epic-level rollups aren't being owned. As QAT (DDEL-73) becomes the live workstream, accurate epic status matters more for the burndown view.

Owner: Ian (admin)

Toggl still logging at project level, not ticket level

Carried over. The 18 June digest shows 107h 17m as "No ticket assigned" at project level. Detailed reports do resolve to specific DDEL tickets (DDEL-67, -70, -55, -49 etc.), so the data exists — but the bot view the team reads each morning still can't attribute hours to tickets. Easy team-level fix; long-running.

Owner: Mike / each developer

Older completed tasks resolved more than 2 weeks ago 18 Done · 79.3 hrs

Historical Done work resolved >14 days ago — the Epic 1 discovery wave (DDEL-11 to DDEL-19), Epic 2 blueprint wave (DDEL-20 to DDEL-26, DDEL-41), and the early Wave 1 prep (DDEL-46). Resolution dates range 15 Apr – 19 May 2026.

Ticket	Summary	Est (hrs)	Spent (hrs)	Resolved
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	~12 days out; +2 mo Float buffer to 31 Aug behind it
Calendar elapsed	79 / 153 days (≈52%)	Of the full Float window
Jira timeSpent to date	379.2 hrs (≈73%)	+81.7 hrs since 4 June; burn-to-calendar gap now +21pp (was +16pp)
Original estimates totalled	233 hrs	Across 75 issues (+15 since 4 June — QAT journeys, split-order, slot counting)
Issues by status	55 Done · 2 In Progress · 2 Blocked · 16 To Do	+23 Done since 4 June; Code Review queue fully drained
QAT journey suite	0 / 8 started	DDEL-74→81 all To Do — execution not begun
Epics by status	1 Done · 5 To Do	DDEL-3 still "To Do" despite 23.4h logged and all build children Done
Active (non-Done) unassigned	16 / 20 (80%)	High — but 8 are the just-created QAT sub-tasks awaiting assignment
Toggl billable this week	107h 17m	Project peak (+7h 52m unbillable). Was ~55h on 4 June — multishipping push.

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

Commitment / risk in last update	Status today
Resolve DDEL-42 (escalated to Rebecca)	✅ Closed 5 June at 20.7h / 12h. Overrun locked in but blocker cleared.
Schedule the Wave 1 Findings Review meeting	⚠️ Not visibly scheduled. Build progressed regardless; review still worth doing before go-live.
Triage the 6-ticket Code Review queue	✅ Fully drained — all 6 resolved 9–11 June.
Confirm DDEL-66 capacity reqs with Hazel	❌ Now Blocked awaiting client. Still gating DDEL-65 Slot Counting.
Assign DDEL-43 and DDEL-50	✅ DDEL-43 done. DDEL-50 superseded by the structured DDEL-73 QAT suite.
Admin-tidy DDEL-3 Epic	❌ Still "To Do" — now 23.4h. Fourth week carried over.
Log the DDEL-12 contingency decision	❌ Still no comment — carried from April

Recommended actions before next check-in

1.Start QAT now — don't wait for the last features. Begin executing the journeys that don't depend on split-order/multi-address (Journey 1 standard delivery, Journey 2 fresh future-date, Journey 5 C&C) while DDEL-67/-70 finish. Zeinab to own DDEL-73 and assign the 8 sub-tasks. This is the single highest-leverage move for the go-live date.

2.Have the end-of-June go-live conversation with Daylesford. Rebecca to confirm with Hazel/Zoe whether end-June is firm or flexible. With QAT unstarted and two features at ~2× estimate, a realistic date (or a phased go-live — core delivery now, multishipping/slot-counting after) should be agreed this week. The 31 Aug Float buffer gives room.

3.Confirm DDEL-67 and DDEL-70 are converging. Both ~2× estimate. Ian to check with Yaroslav (Adyen split orders) and Shahbaz (frontend journey) that these have a definite finish line this week, not open-ended — they gate QA.

4.Unblock DDEL-66 (client capacity) and DDEL-56 (UX). DDEL-66 needs Hazel's sign-off and is holding up the DDEL-65 Slot Counting epic. Get the async confirmation thread moving so slot counting can be sized before the build team frees up.

5.Re-baseline scope vs Float. Spend is 379h vs 233h estimate (~146h over) — beyond the original contingency, driven by genuine scope growth (multishipping + slot counting). Rebecca/Ian to confirm the 516h Float still covers the expanded scope to 31 Aug, and update the estimate baseline so future burn reads true.

6.Admin-tidy DDEL-3 Epic. Carried over FOUR times. Move to In Progress or Done so the burndown is accurate as QAT becomes the live workstream.

7.Log the DDEL-12 contingency decision. Still carried over from April. One-line ticket comment.

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 — 75 issues read via JQL project = DDEL, 18 June 2026
Float project DFD-DM (Delivery Matrix Project, Daylesford) — 516 hr budget, 1 Apr – 31 Aug 2026, active
Toggl summary report 4–18 June 2026 — entries across DDEL-67, -70, -55, -49, -52, -68, -69, -71, -72, -4 plus epic-level lines
ToggleReportsSlack weekly digests 16, 17, 18 June: Daylesford Delivery Matrix 82h → 93h → 107h 17m billable (+7h 52m unbillable) — project peak
Slack #devops-daylesford — staging deploys 8, 12, 15, 16 (×2), 17 June
Confluence Delivery Matrix main client page — Rebecca, updated 16 June (Go-live: End of June 2026)
Confluence "Meeting Updates" (Daylesford space) — 16 June: Hazel, Zoe, Erin & Rebecca
Confluence DDEL Slot Counting — Scoping Note v2 — Ian, 3 June 2026
Confluence DDEL-3 Wave 1 Findings Review and Decision Agenda — Ian, 29 May 2026
Channel access note: Jira / Confluence / Float / Toggl / #devops-daylesford / #develo-project-updates all returned data. #client-daylesford and broad Slack date-filtered global searches returned no DDEL hits — likely a Slack search quirk, not an outage.