Andrew Phillips > Quotes

“Slow, error-prone, manual processes, delays, handoffs and lengthy fix cycles inevitably lead to infrequent releases. And when you infrequently release large numbers of changes and fixes in one go, the go-live is predestined to be stressful and often followed by days or weeks of post-release emergency patches.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“Continuous Delivery changes the way that you and your software development teams work together. This is not a process that stops at the boundaries of the software development team. It helps to foster a professional, high-performance team culture. It frees each group to make the professional decisions for which they are trained and yet encourages them to interact more and depend upon one another’s skills and expertise.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“With Continuous Delivery, developers commit their changes to central version control several times a day, from where the changes are automatically built and tested to produce an updated version of the product.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“After weeks of working on an isolated copy of the code. the new features now need to be combined or “merged” into one single codebase.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“Effectiveness in terms of overall business value generated is more important than efficiency in terms of departmental cost.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“IT needs to be freed from its silo and become an integral part of the organization, typically as a multidisciplinary team focused on delivering benefits to the business - one of the core principles of Devops.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“The ability to roll back the change means that no developer should need to leave the office with the application in a “broken” state, which would block the progress of the rest of the development team.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“The goal of Continuous Delivery is to create a constant flow of changes to production: an automated software production line. The core concept that makes this happen is the Continuous Delivery pipeline. The pipeline breaks the software delivery process down into a number of stages. Each stage is aimed at verifying quality of new features from a different angle in order to prevent errors from affecting your users.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days

“The delivery pipeline is the key concept that enables a continuous flow of changes to production in a Continuous Delivery environment. Key points of the pipeline are: Functionality is only added when the quality is right. All changes to the source code immediately result in a new version of the application. Each new version is automatically tested against all available tests. New versions are automatically deployed to production. All installation and configuration of machines and environments is fully automated.”
― Andrew Phillips, The IT Manager’s Guide to Continuous Delivery: Delivering Software in Days