2) Where not everyone was even doing the basics of CI yet?
In this talk we'll cover the steps that were taken to go from just the basics to full blown Continuous Delivery, discussing who we needed to convince that continuous delivery was THE way to go, the tools and approaches that worked for us, and how we managed to move to Continuous Delivery without any major disruptions to our existing delivery flow.
Amount of time needed to deploy went down across the board. The reduction in deploy time was as high as 80% on some projects. Teams went from doing maybe 20 or so builds a week to doing 20 or so builds a day. Human interaction was essentially removed although being continuous deployment a human still needs to push the button. These are the tangible benefits to be had from trying on the "new hotness" and moving towards Continuous Delivery - delivering features to customers more quickly by continuously moving code into production. Many companies try it, only to discover that speeding up their existing software deployment cycle leads to chaos.
What gets in the way for companies attempting to continuously deliver software? As it turns out, the software deployment process has typically been waylaid by organizational rigidity put in place to fight downtime and failures rather than to provide for efficient deployments. As organizations try to deploy more quickly, they are held back by error-prone and unpredictable deployment processes being executed by an Operations staff that becomes increasingly overworked and overtired.
