CourseForward Deployed Engineer: The Complete Course · Module 11: Delivery Management · part 64 of 85
Part 64 · Module 11: Delivery Management

Lab: Run the engagement's delivery machinery end to end

22 min read·13 Oct 2026
Module 11 · Lab · About 70 minutes · Needs: lessons 1 and 2 of this module (the plan, the logs, change requests, the readiness check, adoption)

What you are building

16 MARCH TO 6 JULY, KEPT AS DATA plan working days RAID log as events change requests with slip steering pack built from data handover gate 1 and 4 Jun adoption 6 Jul delivery/ 7 JSON files 6 checks run each Thursday
Seven pieces of delivery work (blue, your system) are kept as data in the repository, and six checks (green, passed) rerun them every Thursday.

The lessons each looked at one moment: kickoff, a Thursday review, the Monday of week 12, the check on 6 July. This lab runs the whole engagement through one set of files, from Monday 16 March to Monday 6 July. You keep the plan in working days, a RAID and decision log that replays every change, the change requests, a steering pack built from those files, a handover gate, and the one-month review against the target.

Each piece ends in a check written in plain Python, and the last step saves the lot to harbourline-claims/delivery/. There is no model call: every step is bookkeeping that is easy to get wrong on a busy Thursday and easy to check in code. Everything at Harbourline is simulated.

The rest of this course is yours to keep

This course is bought on its own, once, and stays readable afterwards, including the parts added to it later.