JAS · Project Check-in

Jasun Envirocare: Project Check-in

Report date: Thursday 7 May 2026
Client: Jasun Envirocare Plc — Colin Hitch (MD)
AM: Holly Grace  ·  Tech Lead: Nathan McBride  ·  Dev: Umair Ayub  ·  Design: Kathryn Coulter-Patel  ·  Pod: 2
Replatform: jfilters.com → jasunfiltration.com on Magento 2 + Hyvä
Float project: Jasun Envirocare (1 May – 31 Dec 2026, budget not yet set)
Jira: JAS board  ·  Confluence: Jasun Envirocare client space  ·  Onboarding: Onboarding doc
🟡 Amber
Pre-kickoff. Toggl project live ("JAS - Jasun Envirocare New Site Build") and Slack channel #client-jasun confirmed — two onboarding items resolved. Remaining gates before Green: contract sign-off (deposit paid only), Float budget hours, and ticket scoping/assignment.
What's gone well since project start

The project went from a signed proposal to a fully populated planning environment in two working days. The Jira project (JAS) was created on 6 May; on 7 May Holly stood up seven epics covering the full delivery arc — Mobilisation & Onboarding, Technical Foundation, Discovery Workshops, UX Research & Strategy, UI Design & Sign-off, ERP & Integration Discovery, and Data & Migration Planning.

The Technical Foundation epic (JAS-4) has been broken out into eight specific tasks ready for sequencing — Typesense provisioning and module install (both High priority), Yireo DataLayer (High), local dev tooling, Mage-OS Blog, cookie consent, reCAPTCHA, and the GitHub Actions CI/CD pipeline. That's the right level of granularity for the team to start estimating against.

Documentation is unusually solid for week 1. Kathryn has authored a full onboarding page in Develo Internal covering project context, what we're building, current-site analysis, an onboarding checklist (22 items), 7 discovery sessions, 26 kickoff questions, and a 13-item technical access request. Holly has set up the dedicated JE Confluence space for the client. The team and stack are confirmed: Pod 2 (Holly / Nathan / Umair / Kathryn) on Magento 2 + Hyvä (Tailwind + Alpine), Typesense for search, Cart2Quote for the quote workflow, Business Central via Commerce 365 for ERP.

Issues, risks and watchpoints
Contract not yet signed — gates full kickoff
Per the onboarding doc: deposit paid, contract pending. Until it lands, kickoff calendar invites, recurring sprint planning, server access requests and the Discovery Workshop block all carry commercial exposure. This is the single biggest reason the report is Amber rather than Green.
Owner: Holly Grace (AM)
✅ Toggl project live; Slack channel confirmed
Toggl project created: "JAS - Jasun Envirocare New Site Build". Slack channel confirmed as #client-jasun. Time tracking can begin as soon as the contract is signed. Float budget hours still need to be entered so future reports can show burn against budget.
Float budget not yet set
Float has the Jasun Envirocare project active on the calendar (1 May – 31 Dec) but with no budget hours defined. Toggl is now wired up — Float is the last piece needed so future reports can quote burn against budget. Lift the figures from the Technical Scope & Estimate.
Owner: Holly Grace + finance
Every JAS issue is unassigned, unestimated and "Scoping Required"
All 18 issues — 7 epics + 8 foundation tasks + 2 test tickets — share the same status (Scoping Required), have no assignee, no original estimate, and no due date. That's expected for day 1, but it means the board can't yet drive a sprint. Foundation tasks marked High (Typesense provisioning, Typesense M2 module, Yireo DataLayer) are the natural first targets to scope and assign so technical work can run in parallel with discovery.
Owner: Nathan McBride (Tech Lead)
ERP integration is the highest-risk workstream — and untouched
The onboarding doc explicitly flags Commerce 365 / Business Central integration as the top risk and notes that "dedicated discovery workshop essential before dev begins". JAS-8 (ERP & Integration Discovery) is a stub epic only — no scoping, no client IT contact named, no workshop scheduled. The product-data-quality assumption ("ERP data is clean") is unverified and needs early validation.
Two test tickets in the project
JAS-1 ("test") and JAS-2 ("test 2"), created 6 May, are still on the board. Minor housekeeping but worth closing before clients are invited into Jira so the board reads cleanly.
Numbers at a glance
MetricValueNotes
Float budgetNot setProject active 1 May – 31 Dec on the calendar; hours figure to be lifted from the Technical Scope & Estimate
Calendar window1 May – 31 Dec 2026 (245 days)~5 month build per onboarding doc
Hours logged to date0 hrsNo Toggl project; Jira timeSpent is null on every ticket
Issues by status18 Scoping Required · 0 In Progress · 0 DoneIncludes 2 test tickets (JAS-1, JAS-2)
Epics7Mobilisation, Tech Foundation, Discovery, UX, UI, ERP, Data Migration
Tasks broken out8 (all under JAS-4)3 High priority: Typesense provisioning + module, Yireo DataLayer
Original estimates totalled0 hrsNothing estimated yet
Active contributors0 (no assignees)Pod 2 named in onboarding doc but not yet attached to tickets
Confluence pages live2Onboarding (Develo Internal) + JE client space overview
Where each workstream stands today
WorkstreamStatus
Commercial sign-off (contract)❌ Pending — deposit paid only
Jira project structure (epics + foundation tasks)✅ In place — 7 epics, 8 tasks under JAS-4
Confluence — internal onboarding doc✅ Authored, dated 6 May
Confluence — JE client space✅ Created, awaiting population
Team / pod allocation✅ Pod 2 confirmed (Holly / Nathan / Umair / Kathryn)
Float budget hours❓ Project on calendar, hours not entered
Toggl project✅ Live — "JAS - Jasun Envirocare New Site Build"
Slack channel✅ #client-jasun confirmed
Kickoff & recurring sprint planning❓ Scheduling blocked on contract
Discovery workshops (7 needed)❓ Listed, not scheduled
Server / hosting access (13 items)❌ All 'To request'
Sansec security scanning + OhDear monitoring❓ On checklist
Ticket assignees / estimates❌ Zero of 18 issues assigned or estimated
Recommended actions before next check-in
1.Get the contract signed. This unblocks kickoff scheduling, server access requests and the discovery workshop calendar. Until it lands the project remains Amber.
2.Lift the budget hours from the Technical Scope & Estimate into Float, and create the Toggl project under client "Jasun Envirocare" so future reports can quote burn against budget.
3.Scope and assign the three High-priority foundation tasks first — JAS-11 (Typesense provisioning), JAS-12 (Typesense M2 module), JAS-13 (Yireo DataLayer). These have no design dependency and can run in parallel with discovery.
4.Schedule the ERP/Commerce 365 discovery workshop and name a client IT counterpart, given the onboarding doc flags this as the highest-risk workstream and the assumption that "ERP data is clean" is unverified.
5.Close JAS-1 and JAS-2 (test tickets) before the client is invited to the Jira board.
Sources