1999: Kent Beck * first edition, published October 1999 We need to control the development of software by making many small adjustments, not by making a few large adjustments, kind of like driving a car.
1999: Kent Beck * first edition, published October 1999 Big changes made all at once just don't work. Any problem is solved with a series of the smallest changes that make a difference.
2003: Poppendieck * book published May 2003 Remember the rule of small batches: If you integrate changes in small batches, it will be infinitely easier to detect and fix problems.
2004: Kent Beck * second edition, published November 2004 Software 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.
2004: Kent Beck * second edition, published November 2004 The more things are deferred, the larger the chunk, the higher the risk. In contrast, the principle of flow suggests that for improvement, deploy smaller increments of value ever more frequently.
2004: Kent Beck * second edition, published November 2004 It's always tempting to make big changes in big steps. Momentous change taken all at once is dangerous.
2004: Kent Beck * second edition, published November 2004 Baby steps acknowledge that the overhead of small steps is much less than when a team wastefully recoils from aborted big changes.
2004: Kent Beck * second edition, published November 2004 Baby steps are expressed in practices like test-first programming, which proceeds one test at a time, and continuous integration, which integrates and tests a few hours' worth of changes at a time.
2004: Kent Beck * second edition, published November 2004 Daily Deployment Put new software into production every night. Any gap between what is on a programmer's desk and what is in production is a risk.
2004: Kent Beck * second edition, published November 2004 The deployment tools must be automated, including the ability to roll out incrementally and roll back in case of failure.
2004: Kent Beck * second edition, published November 2004 There are many barriers to deploying frequently. Some are psychological or social, like a deployment process so stressful that people don't want to go through it twice as often.
2004: Kent Beck * second edition, published November 2004 Whatever the barrier, working to remove it and then letting more frequent deployment come as a natural consequence will help you improve development.
2007: Michael Nygard * first edition, published March 2007 One solution — the easy but harmful one — is to slow down the release calendar. Like going to the dentist less frequently because it hurts, this response to the problem can only exacerbate the issue.
2007: Michael Nygard * first edition, published March 2007 The right response is to reduce the effort needed, remove people from the process, and make the whole thing more automated and standardized.
http://www.startuplessonslearned.com/2009/02/work-in-small-batches.html software should be designed, written, and deployed in small batches 2009: Eric Ries * February 2009
https://omniti.com/seeds/online-application-deployment-reducing-risk.html 2010: Theo Schlossnagle * published March 2010 micro-releases: releases must never get too large instead amortize risk with small, controlled releases
2010: Facebook * Velocity Conference, June 2010 a culture of making very frequent small changes if you've only changed one thing at a time, it is really easy to figure out what broke the site https://www.youtube.com/watch?v=nEmJ_5UHs1g Robert Johnson
* book published August 2010 2010: Continuous Delivery Imagine that you released frequently, so the delta between what is currently in production and the new release is small. If that were true, the risk of release would be greatly diminished
Work in small batches. With a small batch size, you 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-flow/ * published March 2012
https://www.joelonsoftware.com/2012/07/09/software-inventory/ * published July 2012 2012: Joel Spolsky If you’re already shipping monthly, figure out how to ship weekly. Keep pushing the bar on more and more frequent deployment of smaller and smaller changes.
How long would it take your organization to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis? * October 2012 2012: Jez Humble https://www.youtube.com/watch?v=skLJuksCRTw
And deploying smaller sets of features more frequently reduces the number of changes per deployment, which is an inherent benefit 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/netflix-techblog/deploying-the-netflix-api-79b6176cc3f0 2013: Netflix * published August 2013
2013: gilt.com continuous delivery is critical Every release is small. You know what's changed in production. If it doesn't work, rollback is simple * Surge conference, September 2013 https://www.youtube.com/watch?v=8-6azNVq2X0
We love to deploy new code incrementally hundreds of times a day. And there's good reason for that: it's safer overall. Incremental deploys are easier to understand and fix than one gigantic deploy once a year. https://zachholman.com/talk/move-fast-break-nothing/ 2014: Github * published October 2014
https://codeascraft.com/2015/02/20/re-introducing-deployinator-now-as-a-gem/ 2015: Etsy We deploy code about 40 times per day. This allows us to push smaller changes we are confident about and experiment at a fast rate. Jayson Paul * published February 2015
in practice, large-impact, high- risk deployments end up happening infrequently due to understandable fear unfortunately, this means that our changes build up between releases 2015: Building Microservices * book published February 2015
throughout the book, I promote the need to make small, incremental changes one of the key drivers is to understand the impact of each alteration * book published February 2015 2015: Building Microservices
2015: gilt.com * QCon London, July 2015 simpler and easier deployments and rollbacks Yoni Goldberg teams can decide when they want to deploy deploy multiple times per day
2015: gilt.com * QCon London, July 2015 database schema changes are required to be incremental Yoni Goldberg database schema changes are released separately from service code
It is much easier to measure and understand the impact of a single change rather than a batch of changes released simultaneously. 2016: Google * book published April 2016
If the release is performed in smaller batches, we can move faster with more confidence because each code change can be understood in isolation in the larger system. 2016: Google * book published April 2016
2016: Uber * published June 2016 https://eng.uber.com/micro-deploy/ Engineers write code, review it, test it, and put it into production the same day. Each week in 2016, thousands of engineers push to prod several thousand service builds
* book published June 2016 2016: Microservice Architecture reducing the size of the deployment unit a notion we call “batch size reduction” reducing the size or scope of the problem
make regular, small, incremental changes 2016: AWS re:Invent * Las Vegas - December 1, 2016 Tim DiLauro AWS Solutions Architect https://www.youtube.com/watch?v=8e2zCHx-K3M which allows you to ultimately move faster
2017: Uber * SRECon, March 2017 Sebastian Yates https://www.youtube.com/watch?v=4A4SLk1PRvg [service owners are] able to deploy at any schedule they like they can do 40 deploys a day
an architecture that allows small, incremental changes is easier to evolve because developers have a smaller scope of change 2017: Building Evolutionary Architectures * book published September 2017
* second edition, published January 2018 to be successful, your software will be deployed early and often smaller, easier deployments mean you can make big changes over a series of small steps 2018: Release It!
2018: Michele Titolo Microservice deployments should be small. If you have small services, you are probably making small changes. * QCon New York, June 2018
2018: Charity Majors https://charity.wtf/2018/08/19/shipping-software-should-not-be-scary/ * published August 2018 suffice it to say that we now know that smaller and more frequent changes are much safer than larger and less frequent changes ship early, ship often, ship smaller change sets
2019: Charity Majors * published May 1, 2019 https://charity.wtf/2019/05/01/friday-deploy-freezes-are-exactly-like-murdering-puppies/ Fear of deploys is the ultimate technical debt Do not batch up multiple people’s commits into a deploy Good teams ship often
2019: Adrian Cockcroft * CraftConf, May 9 2019 https://www.youtube.com/watch?v=rnygCAvVBj8 Number of meetings per deploy: drive to zero You don’t have time to have 10 meetings a day for the 10 times you deploy today.
2019: Adrian Cockcroft * CraftConf, May 9 2019 https://www.youtube.com/watch?v=rnygCAvVBj8 If you have a competitor that is updating 10 times a day and you are updating every 2 weeks, then you will fall behind.
sullis
inouehi
yutootsuka
track3jyo
masayaaoyama
hiro_y
ivargrimstad
utgwkk
fishofprey
eatplaynap
yusukebe
.png){kind=avatar}
headwaters
sasakendayo
keithpitt
lynnandtonic
jasonvnalue
jlugia
moore
sonatard
lara
lauravandoore
dougneiner
morganepeng
brad_frost
danielanewman