development has long delivered value in big chunks. Many teams make the problem worse by tending to respond to stress by making the chunks of value bigger, from deploying software less frequently to integrating less often.
are reducing the amount of complexity that has to be dealt with at any one time by the people working on the batch. Break down large releases into small units of deployment 2012: Damon Edwards http://dev2ops.org/2012/03/devops-lessons-from-lean-small-batches-improve-ﬂow/ * published March 2012
number of changes per deployment, which is an inherent beneﬁt of continuous delivery and helps mitigate risk by making it easier to identify and triage problems if things go south during a deployment. https://medium.com/netﬂix-techblog/deploying-the-netﬂix-api-79b6176cc3f0 2013: Netﬂix * published August 2013
a day. And there's good reason for that: it's safer overall. Incremental deploys are easier to understand and ﬁx than one gigantic deploy once a year. https://zachholman.com/talk/move-fast-break-nothing/ 2014: Github * published October 2014