Skip to content

4 · AI-native delivery: workflow and planning

Across all three parts; the plan ready before 9 November, the read-out in late January as at 16 November 2026

40%

The POC is the first real use of the delivery method designed for the shopper programme, and it proves the method on the POC’s own work: Part 2’s designs and Part 3’s build are planned and delivered through it. The tooling exists: the delivery plugin was built and released in October. What the POC adds is live use and numbers, from two builders doing the work.

ItemStatusProgressOwnerDueMoved
Planning: from requirement to task brief in Azure DevOps In progress Overdue
50%
Sean 9 Nov 3 Nov
The delivery workflow on every POC repository In progress
50%
Pat none set 3 Nov
The roles at the accountable points Done
100%
Sean none set 3 Nov
The measured baseline Not started
0%
Sean 29 Jan 3 Nov
What still needs proving live Not started
0%
Pat none set 3 Nov
  • The plugin is on every POC repository from its profile, and a second person reproduces a working session from the repository alone.
  • Every Part 2 and Part 3 item was delivered from a task brief traced to a statement, and the coverage check ran as a required check.
  • The plan, the briefs and the cross-squad dependencies are visible in Azure DevOps, and each brief is linked to its pull request.
  • In the demo, a fresh brief becomes a merged pull request through the loop, on work nobody rehearsed.
  • The gates blocked at least one bad change during the POC, and the two live hook checks passed.
  • The read-out carries the measured baseline and says what the agents did well, where people stepped in, and what the Release 1 team should keep.