DDEL · Project Check-in

DFD Delivery Matrix: Project Check-in

Report date: Wednesday 8 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

UAT is running well — but the Float budget is now spent. Delivery is healthy: UAT went live on schedule (1 July), Daylesford (Zoe, Andy McGregor) are actively logging feedback, QAT/UAT bugs are being fixed and deployed daily. The amber has shifted from timeline to commercial: cumulative spend has crossed the 516h Float budget — 547h logged (106%) at ~65% calendar — with UAT fixes, slot counting and go-live still ahead. This needs a budget top-up / re-scope conversation now. (Note: this is the first report reading the full 114-ticket set — prior weeks were capped at 100 and understated spend.)

What's gone well since the previous report

UAT went live on schedule. The 1 July handover happened as planned, and the Delivery Matrix UAT feedback page is now actively in use — updated within the last few hours with client-logged observations against the customer journeys. This is exactly the controlled test gate the 30 June report set up.

Client is hands-on in UAT. Daylesford's Andy McGregor now appears as a Jira assignee alongside Zoe Colegrave's UAT feedback entries — the client is directly testing and raising items rather than waiting for a hand-back. Strong engagement at the acceptance stage.

Defect loop is fast and healthy. QAT/UAT bugs are being raised, fixed and deployed in a tight cycle. Only 5 bugs are open (DDEL-94, -104, -105, -108, -116) with the rest cleared same-week — issues are being found and closed in real time, not stockpiled.

Heavy staging-deploy cadence for fixes. #devops-daylesford shows a busy fix-and-promote rhythm: staging deploys on 1, 3, 6 (×3) and 7 (×4) July. The team is turning UAT feedback around quickly.

Dev burn has naturally tapered. With the build done, the Toggl weekly billable on Daylesford Delivery Matrix dropped to ~31h 34m (week to 8 July) from 232h at peak — the expected shift from build to lighter UAT/bugfix load.

QAT checklist maturing. Zeinab's QAT Checklist now carries explicit desktop + mobile test columns per journey — the test script is being kept live alongside UAT rather than treated as a one-off.

Issues, risks and watchpoints

Float budget crossed — 547h spent against 516h (106%)

Cumulative spend has now exceeded the 516h Float budget — 547h logged at ~65% of the calendar window, with UAT fixes, slot counting (DDEL-65) and go-live still ahead. Most of the overrun is genuine scope growth (multishipping, slot counting and the QAT/UAT bug stream were never in the original 177h baseline), so this is a re-scope story, not runaway inefficiency — but the commercial position must be addressed now: agree a budget top-up or an explicit descope with Daylesford before more hours are committed. Transparency note: earlier reports were capped at 100 Jira issues and understated spend; this reads the full 114-ticket set.

Owner: Rebecca / Luke → Hazel & Andy (commercial)

Go-live date still not formally re-set

The end-of-June target became a 1 July UAT handover as planned, and no production deploy has happened since 24 June — so the project is not yet live. A revised go-live (post-UAT sign-off) still needs to be pinned with the client and communicated, so UAT doesn't drift without a target date to converge on.

Owner: Rebecca (client date)

Four items Blocked; UAT adding client-dependent work

Four tickets remain Blocked — DDEL-66 (client capacity confirmation) still gates DDEL-65 Slot Counting, and DDEL-56 (multi-address UX) is still open. Meanwhile UAT is generating new To Do items (21 now, up from 17). Keep the blocked + UAT-feedback queues visible so they don't become the long pole to launch.

Owner: Rebecca → Hazel / Zoe / Andy

Slot Counting (DDEL-65) still unsized and outside the budget picture

Still no movement — gated on DDEL-66 client sign-off. With Float already exhausted, this can't be absorbed silently: it must be explicitly sized and either funded as part of a top-up or deferred to a separate Wave 3 budget. Decide which this week.

Owner: Ian / Rebecca

Older completed tasks resolved more than 2 weeks ago 57 Done · 297.9 hrs

All Done work resolved >14 days ago — 57 tickets, 297.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 standards/merge (5 Jun), the early-June cleanup batch, and the multishipping features DDEL-67/-70 + early 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
Float budget	516 hrs → exceeded	547h logged = 106% of budget
Jira timeSpent to date	547.3 hrs (≈106%)	Full 114-ticket set; prior reports capped at 100 & understated
Calendar elapsed	99 / 153 days (≈65%)	Of the Float window to 31 Aug
Original estimates totalled	242 hrs	Across 114 issues; spend ~305h over estimate (scope growth)
Go-live	Not yet live	UAT handover 1 Jul (on plan); no prod deploy since 24 Jun; revised date TBC
Issues by status	66 Done · 5 Ready for Staging · 5 QAT · 2 UAT · 4 Code Review · 7 In Progress · 4 Blocked · 21 To Do	UAT active; To Do up (+4) as UAT raises items
Open bugs	5	DDEL-94, -104, -105, -108, -116; fast fix loop
Active (non-Done) unassigned	12 / 48 (25%)	Mostly newly-raised UAT/To Do items awaiting triage
Toggl billable this week	~31h 34m	Down from 232h peak — build done, UAT/bugfix load

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

Commitment / risk in last update	Status today
Pin and communicate the revised go-live date	❌ Still not set. UAT handed over 1 Jul as planned, but no revised go-live date pinned.
Run UAT tightly from Wednesday	✅ UAT live; client (Zoe, Andy) logging feedback; fast fix-and-deploy loop.
Re-baseline Float — now urgent	❌ Not done — and Float has now been crossed (106%). Escalated below.
Unblock DDEL-66, then size DDEL-65 Slot Counting	❌ Both still blocked/unsized.
Keep the blocked queue visible	⚠️ Still 4 Blocked; UAT adding new To Do items.
Clear long-running admin (DDEL-3 / Toggl)	⚠️ Unchanged — low priority behind the budget issue.

Recommended actions before next check-in

1.Hold the commercial conversation this week — top priority. Float is spent (547h/516h). Luke/Rebecca to take a clear position to Hazel & Andy: what the extra hours bought (multishipping + slot counting were beyond the original scope), and agree either a budget top-up or a firm descope. Do this before committing more UAT-fix hours.

2.Pin the go-live date. Still unset. Agree an explicit post-UAT go-live with the client and a production-deploy window, so UAT has a target to converge on rather than drifting.

3.Decide Slot Counting's home. Unblock DDEL-66 (client capacity sign-off), size DDEL-65, then explicitly place it — inside a topped-up budget or a separate Wave 3. It cannot stay off the books now the budget is exhausted.

4.Keep the UAT fix loop tight. It's working well — maintain daily triage of the UAT feedback page and the 5 open bugs so acceptance converges quickly and cost-controlled.

5.Reconcile reporting to the full ticket set. This week revealed prior spend figures were capped at 100 Jira issues. Worth confirming the Float/Toggl reconciliation uses the complete DDEL set so the commercial conversation rests on accurate numbers.

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 114-ticket set read via JQL project = DDEL (2 pages), 8 July 2026. Prior reports capped at 100 and understated cumulative spend.
Float project DFD-DM (Delivery Matrix Project, Daylesford) — 516 hr budget, 1 Apr – 31 Aug 2026, active
ToggleReportsSlack weekly digests 6–8 July: Daylesford Delivery Matrix 10h → 24h → 31h 34m billable — sharp drop from the 232h build peak
Confluence Delivery Matrix UAT feedback page — Rebecca/Zoe, updated 8 July 2026 (active UAT logging)
Confluence DFD - Delivery Matrix QAT Checklist — Zeinab, updated 8 July 2026 (desktop + mobile columns)
Confluence "Meeting Updates" (Daylesford space) — latest 30 June (UAT handover)
Slack #devops-daylesford — staging deploys 1, 3, 6 (×3), 7 (×4) July; no production deploy since 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.