Continuous Delivery

Transcript

1. Continuous Delivery
2. Software Developer @ @duduribeiro } http://carlosribeiro.me
3. https: //opensanca.com.br
6. What is Continuous Delivery?
7. –Jezz Humble “Continuous Delivery is the ability to get changes of all types— including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”
8. Software release should be 
 a fast, repeatable process
10. Waterfall
12. Business Project 1 Project 2 Project 3 Operations QA DBA SysEng
14. Release Testing Operations Coding Development Business Specification Product
 Vision Water Scrum Fall
17. Product Development Operations
18. Why Continuous Delivery?
24. Metrics
26. https://github.com/capitalone/Hygieia
27. “The HP LaserJet Firmware team re-architected their software so they could apply these practices (even though they were not releasing the firmware any more frequently). In the excellent book they published about their journey (from 2008 - 2011), they record the outcomes they achieved: - Overall development costs reduced by ~40% - Programs under development increased by ~140% - Development costs per program reduced by 78% - Resources driving innovation increased by 5x”
28. Changes
31. From 0 to Continuous Delivery
33. DevOps
34. Continuous Integration
35. Infrastructure as Code
36. } - Build - Test
43. CI Principles - Automate everything - Infrastructure as code - App & Infrastructure on VCS - Unify dev and ops team - Perform unit / integrate test
45. Definition of Done
46. –Tim Brown “Aquela grande funcionalidade que você trabalhou nas últimas duas iterações não tem qualquer valor.”
47. Software Improvement & Architecture
48. Feature Toggle
49. Always ready to production
51. Continuous Improvement
53. Etsy
61. 1K deploys - 1 year
62. Summary - Why? - Metrics - Leadership Support - Choose a team to start - Continuous I(mprovement|ntegration)
64. Questions??