This document discusses how Capital One implemented continuous delivery across their large enterprise. They first adopted agile practices using the Scaled Agile Framework which improved quality, productivity, and time to market but work was still happening late in the process. Capital One then adopted DevOps practices by creating dedicated teams focused on automation, integration, testing, and removing constraints. This included establishing a continuous integration pipeline, adjusting their testing approach, and providing self-service tools. Continuous integration and continuous testing enabled continuous delivery across the large enterprise. Key lessons included creating accountability, communicating ROI, sharing best practices, providing training, and being prepared for changing roles and additional costs.

1. Making Continuous Delivery a Reality at a Large
Enterprise
Adam Auerbach

2. About Me
Tweet me @Bugman31
LinkedIN - Adam Auerbach
Responsible for Capital One’s Advanced Testing and Release
Services Teams, which include:
•Performance Testing
•Service Virtualization
•Automated Testing
•Release Management
•Test Data

4. Continuous Delivery is a software development
discipline where you build software in such a way that
the software can be released to production at any
time.
-Martin Fowler

5. Continuous Delivery was realized
through adoption of DevOps and Agile
DevOps'
Con+nuous'
Integra+on'
Con+nuous'
Tes+ng'
Con+nuous'
Monitoring'
Con+nuous'
Delivery'
Agile'

6. Our view of Continuous Delivery

7. Our Agile Transformation

8. Three Years ago, we were really good at Waterfall

9. Using the Scaled Agile Framework (SAFE) we were able
to drive Agile adoption across the enterprise

10. Implementing Agile drove improvements to quality,
productivity and time to market

11. Even with Agile, we still had work happening late in the
process.

12. While better, still not good enough

13. DevOps

14. What is DevOps?

15. Collaboration

16. Automation

17. Fast Feedback

18. Removing Constraints

19. How we did it at Capital One

20. We created dedicated teams focused on DevOps
enablers

21. Establish a Continuous Integration pipeline

22. Adjust our approach to testing

23. Real-Time Test Automation

24. Everything is tied to the pipeline

25. Realtime Dashboards

26. Virtualize Constraints

27. Robust Test Environments

28. Provide Self-Service tools to teams

29. Continuous Integration + Continuous Testing = Continuous Delivery

30. Some lessons learned

31. To drive adoption across the enterprise, we created
accountability at the top and bottom

32. Value Stream Analysis can be a great tool to
communicate ROI for hesitant leaders

33. Create communities to share best practices

34. Provide Training and off the shelf resources to
jumpstart adoption

35. Be prepared for changing roles

36. This is Hard!
• Reuse proven Frameworks
• Evangelists at every level and discipline
• Be ready for the need to educate everyone on
everything
• Leverage dedicated resources who support and
nurture the community
• Be prepared for additional costs

37. Making Continuous Delivery a Reality at a Large
Enterprise
Adam Auerbach