Open now · Engineering
ADLC bootcamp
4 daysClassroom, at your site. AI in the engineering delivery lifecycle.
For engineering teams in regulated institutions.
- Bootcamp
- Twelve outcomes
- Verification evidence
- Prerequisite: none
- Open now
Course catalogue · Available soon
Every practitioner starts with GovKit Core: how to deliver AI with governance built into the work. Then each person takes the track for their sector. Leaders can join each track through a half-day executive briefing.
Same core, then your own regulator and frameworks.
Start here
Sector tracks
Finish
01 · Catalogue
The ADLC bootcamp is open now. Four more courses are open for registration of interest.
No course runs longer than four days. Each course has a practitioner bootcamp. Each sector track also has a half-day executive briefing. We publish cohort dates when a course is released.
Open now · Engineering
Classroom, at your site. AI in the engineering delivery lifecycle.
For engineering teams in regulated institutions.
Start here · Core
Or 6 online half-days.
For architects, engineers, delivery and risk leads.
Track G
3 days + 1-day capstone.
For government entities and GovTech teams.
Track B
3 days + 1-day capstone.
For banks, finance houses and their technology teams.
Track T
3 days + 1-day capstone.
For operators and their network and IT teams.
Planned outlines. Modules, lengths and dates can change before release. Classroom, online and hybrid delivery for each course.
Core · all sectors
Deliver AI features with governance built into the work, not added after it. Specs, architecture contracts, evaluation gates and evidence live in the same repository as the code.
| No. | Module | After this module you can |
|---|---|---|
| C1 | Why governance belongs in delivery | Explain how a control framework (ISO/IEC 42001, NIST AI RMF, EU AI Act) becomes checks in a delivery pipeline. |
| C2 | Architecture contracts | Write layer rules and an ArchiMate view that an AI coding agent must follow. Record decisions as ADRs. |
| C3 | Specs before code | Write acceptance criteria in Gherkin, non-functional requirements and evaluation criteria for one AI feature. |
| C4 | Evaluation gates for LLM features | Set evaluation thresholds and connect them to a CI quality gate that blocks a failed release. |
| C5 | Approval and evidence | Configure named approvers for ADRs. Export evidence that an auditor can trace from requirement to release. |
| C6 | Run it in your organisation | Choose a maturity level and a rollout plan. Assign the roles that own each gate. |
Graded lab
Govern one AI feature from spec to release.
In a sandbox repository with synthetic data, you write the spec and the evaluation criteria, pass the quality gate, and get your ADR approved by a named reviewer. A deterministic grader checks the result.
Labs use the open-source govkit toolkit (Apache 2.0) for governed AI delivery with Claude Code, Copilot or Codex. The course teaches the method, so the controls apply with other tools too.
Track G · Government
Design and release AI services that citizens can trust. Keep data sovereign, decisions explainable and people accountable for each decision.
| No. | Module | After this module you can |
|---|---|---|
| G1 | Public value and citizen trust | Select AI use cases by public value. Write the transparency notice a citizen sees. |
| G2 | Data sharing and sovereignty | Classify data and apply GCC data-protection laws, for example the UAE and Saudi PDPL, to a data-sharing case. |
| G3 | Architecture for shared platforms | Model a cross-entity capability map in ArchiMate. Use the TOGAF ADM to plan a shared AI platform. |
| G4 | Procure and assure AI | Write AI requirements for a tender. Evaluate vendor models with model cards and acceptance tests. |
| G5 | Agentic services with human decisions | Separate process, decision and case work with BPMN, DMN and CMMN. Place the human decision in DMN. |
#1 Capstone
Teams add an AI agent to the steps of a real public service, with a decision model, a data-sharing agreement and a governed release plan. A panel reviews each plan.
#2 Executive briefing · half day
For directors-general and executive directors. A Wardley map of the service landscape and three decisions to take.
Track B · Banking
Take AI use cases from idea to production under model-risk and supervisory rules. Map each use case to BIAN, so architecture, risk and business speak one language.
| No. | Module | After this module you can |
|---|---|---|
| B1 | BIAN for AI use cases | Map an AI use case to BIAN service domains and their control records. |
| B2 | Model risk management | Build a model inventory entry, a validation plan and a monitoring plan against supervisory standards such as the CBUAE Model Management Standards. |
| B3 | Credit, fraud and financial-crime models | Test a model for explainability and fairness. Write the reason codes a customer receives. |
| B4 | Conversational and agentic banking | Define bounded agency for an agent: mandate, consent, limits and a revocation path. |
| B5 | Resilience, cloud and third parties | Assess cloud and AI-vendor risk with outsourcing rules, using DORA as a reference model. |
#1 Capstone
Teams take one AI use case from its BIAN mapping to a dossier that a model-risk committee can approve. Labs use synthetic banking data only.
#2 Executive briefing · half day
For ExCo and board members. Model risk appetite, the regulator's view and the questions to ask management.
Track T · Telco
Put AI into network, service and customer operations with TM Forum ODA, and keep the legacy Frameworx map that most operators still run on.
| No. | Module | After this module you can |
|---|---|---|
| T1 | ODA components and Open APIs | Place an AI capability in an ODA component and name the Open APIs it exposes and uses. |
| T2 | eTOM, SID and TAM | Show which processes, data entities and applications an AI use case changes. |
| T3 | AIOps and autonomous networks | Assess a network domain against the TM Forum Autonomous Networks levels. Plan the next level. |
| T4 | Customer AI | Design a care agent or next-best-action model that respects consent and complaint rules. |
| T5 | Data, sovereignty and regulators | Apply residency and lawful-access rules from regulators such as TDRA and CST to an AI data flow. |
#1 Capstone
Teams specify one AI component with its ODA placement, SID data, eTOM process change and governance gates. A panel reviews each design.
#2 Executive briefing · half day
For CTO, CIO and CXO teams. Where AI pays back in operations, and the risks to accept or refuse.
02 · Register interest
Tell us which course and how many people. We confirm dates when the course is released. Private cohorts for one organisation are also possible.