How to get a bigger bang through smaller batches
Reducing batch size is a secret weapon in Agile software development.
Batch size is the amount of work you carry between stages in your workflow and a batch is only complete when it’s made it all the way through your workflow and is delivering value.
Working in small batches gets your product to market sooner. It makes it much more likely you’ll deliver on time and budget, and catch quality issues before they start to create huge headaches.
The effect is especially strong with big batch projects. Research shows that as you increase the planned duration of your project, the slippage you’re likely to experience increases exponentially.
Working in small batches can seem counterintuitive because you lose economies of scale, but economic analysis shows that the benefits far outweigh the downsides.
In this post you’ll learn how working in small batches reduces project risk and you'll get five practical ways to reduce batch size. Plus you can take a quiz to learn how effective you are currently at keeping your batches small.
How to reduce batch size in Agile software development (and why you should)
|