Traditionally software development has adopted an all-or-nothing approach to delivery, with large releases containing many features and a lengthy catalogue of bug-fixes, performed every few months. Realising the shortcomings of this model, in the last five years, there has been a powerful move towards delivering radically smaller releases, radically more often.
Continuous Delivery – a practice that optimizes the whole lifecycle for releasing high quality software as rapidly as possible – has been proven to deliver value more frequently, reduce risk of failure, and allow a business to respond near-instantaneously to customer requirements.
Drawing on ideas from the lean startup movement, the approach demands commitment to identifying a minimum viable product, ensuring value can be measured empricially, and performing the least responsible quantity of up-front analysis
In this talk, Stephen Nelson-Smith, Principal Consultant at Agile Project Sweden, discusses:
- The challenges to successful implementation, both technical (building completely automated pipelines, using feature-flags and dark releases) and organizational (identifying tangible business threat, committing to wholesale change)
- Common themes in incomplete or flawed programmes
- The the central place of an complete infrastructure automation framework such as Chef
The talk will conclude with a high-level strategy for success based on the realization that continuous delivery demands not only kaizen (incremental improvement), but also kaikaku (radical change).