1 · Technology foundation
Part 1 gets the two builders working first, then gives the build somewhere to run, then the services it connects to and the data it runs on. It goes in that order because each step needs the one before it: nothing is deployed without a working desktop and an account with rights, and nothing connects without somewhere to run. A row closes on evidence that the access works (an app deployed, a record created and read back), never on a ticket marked granted.
Rows 1.1 are where the builders work, 1.2 where the build runs, 1.3 what it connects to, 1.4 the data it runs on. Every external SaaS runs on its sandbox or a test account; free accounts are opened under a Metcash address, hold synthetic data only, and have their limits checked before the demo.
| Item | Status | Progress | Owner | Due | Moved |
|---|---|---|---|---|---|
| Developer desktop (AVD) | Blocked | End-user computing and the cloud team | none set | 3 Nov | |
| Developer standard | In progress | Security with end-user computing | none set | 3 Nov | |
| Administrator accounts | Not started | The cloud platform team | none set | 3 Nov | |
| GitHub and the AI tooling policy | In progress | The GitHub enterprise owner with security | none set | 3 Nov | |
| Azure DevOps | Done | The delivery lead | none set | 3 Nov | |
| Azure sandbox resource group | In progress | The cloud platform team | none set | 3 Nov | |
| API Management (two Consumption gateways) | Not started | The shopper technology team | none set | 3 Nov | |
| Vercel and the edge | In progress Moved this week | The shopper technology team | none set | 16 Nov | |
| commercetools development project | In progress Moved this week | The programme lead with the vendor | none set | 16 Nov | |
| Coveo | In progress | Sean | none set | 3 Nov | |
| Auth0 | In progress | Sean | none set | 3 Nov | |
| CyberSource sandbox | Done | Corporate payments | none set | 3 Nov | |
| Talon.One test tenant | In progress | The loyalty lead | none set | 3 Nov | |
| Segment and Braze (optional) | In progress | The martech lead | none set | 3 Nov | |
| Catalogue data (Thirsty Camel extract) | In progress Moved this week | The Liquor product owner | none set | 16 Nov |
Not needed for the POC. No iOS app is built, so no Mac and no Apple developer account. A phone or handheld cannot connect to a virtual desktop, so the store leg installs the pick-and-pack app from the pipeline and tests it on the device over the network.
Part 1 closes when
Section titled “Part 1 closes when”- Each builder works on the developer image with the full toolchain and no per-tool exceptions.
- Every row shows working evidence, or names its stand-in and the date the stand-in was accepted.
- The developer standard is agreed: the baseline on the image, the fast-track for a new tool, the onboarding profile.
- A new developer reaches a running local stack and a deployed preview on day one, on the image, from the README alone.