Ideas similar to my gospel of continuous deployment, architecture sustenance and operational excellence.
“DevOps” is an emerging set of principles, methods and practices for communication, collaboration and integration between software development (application/software engineering) and IT operations (systems administration/infrastructure) professionals.[1] It has developed in response to the emerging understanding of the interdependence and importance of both the development and operations disciplines in meeting an organization’s goal of rapidly producing software products and services.[2][3][4][5][6]
Illustration showing Devops as the intersection of development (software engineering), technology operations and quality assurance (QA)
The use of Devops integration can have profound results in product delivery, quality testing, feature development and maintenance releases (including the once special but now ubiquitous “hot fix“). Organizations without Devops capabilities can see problems emerge from the “gap” of information shared between development and operations. This occurs as operations request greater reliability and security, developers ask for faster infrastructure responsiveness, while business users ask for more application enhancements and releases made available faster.[citation needed]
Devops Impact on Application Releases
Reduced change scope
Increased release co-ordination
norootsquash 