Comparison
DeploymentvsDeployment frequency
Deployment
you put the new build on the servers, which is a completely separate event from anybody actually using the new behaviour.
Moving a build into an environment. It is a technical act, reversible and low-drama when the code is deployed dark. Conflating it with release is what makes shipping scary, because it forces every change to be exposed the moment it lands.
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 →