From agile to DevOps to continuous delivery, improving the process of software development.
Software development protocol used to dictate fewer releases. The emphasis was on creating monolithic builds that were extremely high-quality and stable. Customers were happy with updates every one or two years. While this model is still applicable in select industries, the bulk of teams are striving to move to a more nimble and agile release process. This movement, referred to as “continuous delivery,” has gained significant momentum and taken the industry by storm.
Continuous delivery has flourished with the rise of the SAAS model. This models allows for more frequent software updates and is now a competitive imperative in today’s fast-paced market. Developers are moving code to a shared repository so that they can integrate their code, detect problems early and fix them. Developer must service users whose preferences and devices are changing rapidly. The quicker you release code, the faster you can innovate and achieve higher customer satisfaction.
"To Be Continuous" Podcasts
- 1. Why Continuous Delivery
- 2. Favorite Things about Continuous Delivery
- 3. Evolution of Continuous Delivery
- 4. Shipping Velocity and Team Structure
- 5. The Fear of Shipping
Articles on Continuous Delivery
- - The Scoop On Continuous Delivery Of Software Releases
- - Canary release is the new beta
- - Canary launches – how and why to canary release
Case Studies on Continuous Delivery