In a highly integrated environment with agile teams having many dependencies, Capital One had the typical rigorous release and change management process you would expect at a large national bank. Through the adoption of DevOps and other “shift left” enablers, Capital One was able to automate these processes and quality gates, to enable release-on-demand and eventually continuous delivery.
- Title: Adopting DevOps in the enterprise: Lessons from Capital One
- Release date: May 2017
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 0636920458999
You might also like
Scaling DevOps and continuous delivery at ING
Our journey started five years ago by implementing Scrum in order to develop our ING mobile …
Serverless Security: Understand, Assess, and Implement Secure and Reliable Applications in AWS, Microsoft Azure, and Google Cloud
Apply the basics of security in serverless computing to new or existing projects. This hands-on guide …
(Re)Building an engineering culture: DevOps at Target
Target has been focused on (re)building an engineering culture for over a year. One of the …
DevOps for the Modern Enterprise
"Many organizations are facing the uphill battle of modernizing their legacy IT infrastructure. Most have evolved …