jargon

Architecture & practice·Delivery, flow and technical debt

the team ships eleven times a day and the other one ships every second Thursday.

Deployment frequency

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.

Commonly confused with