Deployment throughput in You Build It You Run It
An on-call product team performs a production deployment when they have successfully completed product demos, automated functional testing, exploratory testing, security testing, and any other assurance checks.
On-call product team reviews change. If the deployment is a regular, low risk change then the product team chooses a pre-approved change request. If the deployment is irregular or high risk, they add a ticket into the change management queue, and fall back on a CAB meeting with the change management team. In ITIL v3, this is the difference between a standard change and a normal change.
On-call product team performs deployment. The product team uses a tool such as Jenkins or GitLab CI to orchestrate the deployment.On-call product team performs post-deployment validation. The product team does some post-deployment smoke testing, and continues to monitor live traffic.
On-call product team sends deployment notification. The deployment process ends with the automated addition of a ticket into the change management queue, notifying the change management team of the deployment and its result.
Deployment throughput costs in You Build It You Run It
| Cost Type | Frequency | Description | Impact | TCO % |
|---|---|---|---|---|
Setup cost | One-off | Launch costs incurred in
| Capex cost | High |
Opportunity cost | Per feature | Can be measured as the cost of delay between product feature readiness and launch. Potential revenue lost, missed customer opportunities due to
| Lost revenue | Low |
Run cost | Per deployment | Deployment costs incurred in completing a deployment
| Low | Low |
Deployment costs are incurred as capex, as they are performed by on-call product teams themselves.
Last updated
