# Deployment throughput in You Build It You Run It

![](https://2244764212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXqoxcw7vw1rB7kpYNU%2Fuploads%2Fgit-blob-686a95cca136fe692cb67d1e2956c65b6fb13821%2Fyou-build-it-you-run-it-deployment-throughput.png?alt=media\&token=afe4b2f9-00a5-4ff4-9b62-c7d2d6495632)

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        | <p>Launch costs incurred in</p><ul><li>Deployment pipeline setup</li><li>Change management team time for setup</li></ul>                                                                                                                        | Capex cost   | High  |
| Opportunity cost | Per feature    | <p>Can be measured as the cost of delay between product feature readiness and launch. Potential revenue lost, missed customer opportunities due to</p><ul><li>Delay waiting for a CAB meeting (irregular, high risk deployments only)</li></ul> | Lost revenue | Low   |
| Run cost         | Per deployment | <p>Deployment costs incurred in completing a deployment</p><ul><li>Time for performing deployments, and rolling back deployments minimised due to no handovers</li></ul>                                                                        | Low          | Low   |

![](https://2244764212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXqoxcw7vw1rB7kpYNU%2Fuploads%2Fgit-blob-fa8bc93b3f0dc07a065d343451c3547d436f4a7a%2Fyou-build-it-you-run-it-deployment-throughput-costs.png?alt=media\&token=8985ce87-d66a-4b43-8a24-bafbea9bfe1c)

Deployment costs are incurred as capex, as they are performed by on-call product teams themselves.