Release size and risk.
THE INTUITION
Fewer, larger releases feel safer.
WHY THAT IS WRONG
A large release contains many changes.
When it fails, you do not know which caused it.
WHAT SMALL RELEASES GIVE YOU
An obvious cause when something breaks Easy reversal Less to verify each time Faster feedback
WHAT FREQUENT RELEASES REQUIRE
Automated deployment Automated testing The ability to revert
WHAT THEY PRODUCE
Confidence, because the process is exercised constantly.
WHY THAT MATTERS
A deployment process used once a quarter is unfamiliar and frightening.
One used weekly is routine.
WHAT TO AVOID
Accumulating changes until a large release becomes necessary Releasing at the end of a week, with nobody available afterwards
WHAT TO PREFER
Releasing early in the day, early in the week.
WHAT TO MEASURE
How often you release How long a change takes to reach production How often a release causes a problem
