DevOps cannot work independently. It has to be integrate with the existing frameworks. Software we create does not exist separately from the people who use it and the people who create it. Devops is about finding ways to adapt and innovate social structure, culture, and technology together in order to work more effectively.

There are many software development methodologies, but they focus primarily on requirement management and its impact on the development effort. There are many excellent books  that cover in detail different approaches to software design, development, and testing; but these, too, cover only a fragment of the value stream that delivers value to the people and organizations that sponsor our efforts.

What happens  once requirements are identified, solutions designed, developed, and tested? How are these activities joined together and coordinated to make the process as efficient and reliable as we can make it? How do we enable developers, testers, build and operations personnel to work together effectively?

DevOps describes an effective pattern for getting software from development to release. We describe techniques and best practices that help to implement this pattern and show how this approach interfaces with other aspects of software delivery.

The pattern that is central  is the deployment pipeline. A deployment pipeline is, in essence, an automated implementation of your application’s  build, deploy, test, and release process. Every organization will have differences in the implementation of their deployment pipelines, depending on their value