The concept of Change Management should not be looked at as something that is going away in DevOps, instead it should be viewed more, as a way of improving the verification process, saving resources, using the pipeline as the change management tool and streamlining the process.
DevOps breaks down Change Management in three ways:
Risk reduction – DevOps reduces risk via the introduction of robust automated testing of both application and infrastructure code, the rapid detection of problems through greatly enhanced monitoring and feedback loops and an enhanced rollback ability.
Constant builds – A key principle underlying DevOps is that we take things that are painful such as builds, versioning and deployments and do them constantly in order to learn how to do it better and take the pain away.
The process is the documentation – DevOps is a highly automated, end-to-end process from inception through, testing, deployment and support and as part of the process we build in checks and balances through testing, feedback loops and monitoring that are required for compliance in the change management process. In DevOps, instead of having a highly manual documentation process, the automated workflow becomes the documentation process.