The small batches principle

Abstract

Why are small batches better? Small batches result in happier customers. Features get delivered with less latency. Bugs are fixed faster. Small batches reduce risk. By testing assumptions, the prospect of future failure is reduced. More people get experience with procedures, which means our skills improve. Small batches reduce waste. They avoid endless debates and perfectionism that delay the team in getting started. Less time is spent implementing features that don't get used. In the event that higher-priority projects come up, the team has already delivered a usable system. Small batches improve the ability to innovate. Because experimentation is encouraged, the team can test new ideas and keep the good ones. We can take risks. We are less attached to old pieces that must be thrown away. Small batches improve productivity. Bugs are fixed quicker and the process of fixing them is accelerated because the code is fresher in the mind. Small batches encourage automation. When something must happen often, excuses not to automate go away. Small batches encourage experimentation. The team can try new things-even crazy ideas, some of which turn into competition-killing features. We fear failure less because we can easily undo a small batch if the experiment fails. More importantly, experimentation allows the team to learn something that will help them make future improvements. Small batches make system administrators happier. We get instant gratification, and hell month disappears. It is simply a better way to work.