Academy · DevOps
DevOps foundations for regulated delivery
Pipeline, environment and release practice for teams that have to produce evidence as well as software. [Draft copy]
Who it is for
Engineers and engineering managers delivering into an environment with audit, change-control or regulatory obligations. No prior pipeline ownership assumed, but participants should have shipped software in a team.
What you will be able to do
- Design a build and release pipeline whose output is auditable without extra work.
- Separate environments and access in a way a change-control process can accept.
- Write and enforce a deployment standard your team will follow.
- Produce release evidence automatically rather than assembling it per audit.
[Draft copy]
Outline
Delivery as a controlled process
Half day · Why change control and speed are not opposites.
Pipelines that produce evidence
Full day · Build, test, artefact provenance, approval gates.
Environments, access and segregation
Half day · Least privilege that survives an audit.
Release, rollback and the evidence pack
Full day · Hands-on, on your own toolchain where possible.
[Draft copy — final outline to be confirmed with the trainer]
Prerequisites
A laptop with an editor and a Git client. Familiarity with one CI tool is useful but not required. No certification is a prerequisite.
Your trainer
Next dates
- Scheduled dates
- [Client to supply — course dates]
- Format
- 3 days, in-person. In-house delivery available.
- Location
- [Client to supply — venue]
- Price per seat
- RM [To supply]
- HRDF
- Claimable. How claims work
Booking is by enquiry while the Academy scheduling system is being set up. [Draft copy]
We hand over the keys.
The Academy exists to transfer capability, not to create dependency. Tell us what your team needs to be able to do.
Start a conversation