Abstract: This is the story of how Capital One used DevOps Culture and Kanban Principles to significantly increase the speed of feature delivery, while lowering risk. Large organizations can be filled with manual processes, and many people feel there is nothing they can do about them. Our team took the name “Meteor” inspired by the one that took out the dinosaurs, because we wanted to cause the mass extinction of these manual processes.
In this presentation, we will discuss the ‘old’ manual way that work was completed at Capital One and the inefficiencies that we saw as a result. We will discuss the transformation to the DevOps culture that we helped to push. With the elimination of component teams and proper application of Kanban principles, we have taught teams how to manage their own adoption of DevOps in an effort to move the organization to full continuous integration and continuous delivery.
Learning Outcomes: - Define "self-service DevOps culture" and show methods for implementing within large organizations.
- Illustrate the core principles needed to coach development teams to embrace DevOps.
- Create an effective pipeline to deliver features into production multiple times a day with zero downtime.
- Use effective branching strategy for CICD.
- Show the benefits of using component testing with Github Pull Request checks for code quality.
- Understand how to use kanban methodologies to manage both the flow of work and team dependencies.
- Understand the benefits of feature teams vs. component teams.
Attachments:
