AI Project & Programme Delivery
Getting an AI programme from approved to adopted, across teams that do not report to you.
Who this is for
Project, programme, and delivery managers running AI rollouts in an enterprise.
What you should be able to do
Run a delivery plan with named risks, a decision log, and an adoption measure that is not a launch date.
Career ladder
The titles this track maps onto. Levels differ between companies — the useful part is the direction, and what each step adds to the one before it.
- Project Coordinator
- Project Manager
- Senior Project Manager
- Programme Manager
- Director of Delivery
Tech stack
What the work is actually done with. Grouped by the job each tool does, so the list reads as a system rather than a pile of names.
- Method
- AgileScrumKanbanStage gates
- Planning
- RoadmapsDependency mappingCritical path
- Control
- RAID logChange controlSteering cadence
- Adoption
- EnablementTrainingSuccess criteria
The delivery flow
The order the work actually happens in. Each step is where a decision gets made and written down, not a chapter heading.
- Scope + success criteria
- Stakeholder map
- Dependency plan
- Risk register
- Delivery cadence
- Change control
- Enablement
- Adoption review
Reference repository structure
A starting layout for this track. The directories are the ones that get added late and hurt — decisions, evals, policy, lineage — promoted to the top level where they are visible.
programme/ ├── charter.md # what done looks like, agreed before start ├── stakeholders/ │ └── raci.md ├── plan/ │ ├── milestones.md │ └── dependencies.md # the ones outside your control, named ├── raid/ │ ├── risks.csv # with owners and review dates │ └── decisions.md # what was decided, by whom, and why ├── enablement/ # training, docs, champions └── adoption/ # measured after launch, not at it
Reference implementations
Citadel’s open-source repositories for this track — Terraform modules, MCP servers, and reference architectures you can read, fork, and run. Apache/MIT licensed; check each repository for its terms.
Primary sources
The standards, framework documents, and vendor references this track is built against. Go here when you need the authoritative wording rather than a summary — in a security review or an audit, the source is what counts.