Pipeline as Code
The pipeline becomes reviewable, which is the point. It also becomes branch-specific, which is both the feature and the trap.
-
-
Secrets Management
Secrets need a tested lifecycle: creation, rotation, revocation, and expiration, including enforcement at the protected service.
-
Infrastructure as Code
Use reviewed code changes by default, and reconcile authorized emergency changes with the intended state.
-
Infrastructure and Configuration as Code
Your code says what should exist. The state file says what the tool believes exists. The cloud knows what actually exists. Three answers, one system.
-
Small Batches
Fixed release costs encourage batching, but delay and recovery risk matter too. Reduce repeated overhead while building decomposition and testing skills.
-
Value Stream Mapping
Bring together the people who perform and receive the work. Use their observations and flow measurements to identify delays and test improvements.
-
DORA Metrics
DORA uses five delivery metrics. Define event boundaries, distinguish failed-deployment recovery from all-cause MTTR, and interpret changes in context.
-
Software Delivery as a Flow
A fictional change takes two days to write and six weeks to reach a user. Trace its waits, work, and rework to decide what to improve.
-
DataOps
Treating analytics as code, versioned and tested. The practices are borrowed from DevOps; the hard part — who owns which number — is not a tooling problem.