Continuous Delivery Explained

Jez Humble defines Continuous Delivery as, “The ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”

As the first post-agile methodology, the goal of continuous delivery is to have all deployments be so routine that you can do them at any time with no impact to your customers.

Sounds easy!

In fact, to do this, you need to automate and simplify all practices and process from requirements to deployment including, quality assurance and testing, continuous integration, configuration management, environments and deployment, data management, release management and organizational structure. In this session, we’ll introduce theses foundational practices of Continuous Delivery. We’ll delve into the details with practical suggestions on how you can get started and make progress in all foundational areas. Along the way, we’ll suggest some tools that could be used to assist your adoption. Lastly, we’ll discuss some of the challenges and roadblocks that you might encounter when you begin your Continuous Delivery journey.