Comparison
Change failure ratevsDeployment frequency
Change failure rate
one deploy in six needed a fix or a rollback, and nobody had counted until someone asked.
The proportion of deployments causing a degradation that requires remediation. It is the stability half of the DORA pair, and it exists to catch the obvious objection to shipping frequently. A low rate combined with low frequency usually means the team is not shipping rather than that it is careful, which is why the four numbers are only meaningful together.
Full entry →Deployment frequency
the team ships eleven times a day and the other one ships every second Thursday.
How often changes reach production. It is a proxy for batch size and for how much friction sits between finished code and users, which is why it correlates with almost everything else. Raising it is not about deploying more for its own sake: it is about removing the fixed cost that made a big release rational in the first place.
Full entry →