How we introduced Continuous Delivery? Alex Schwartzwww.flickr.com/photos/burtonandy/4702810536/ Places Backend Delivery Team
How we introduced Continuous Delivery? Old Days: • Cycle time >35 days • 4-6 releases per year Now – for a legacy app: Cycle time ca. 10 days New App: PBAPI • 1-5 releases per week • 40 releases in prod in 5 month • Min cycle time 2 hours • Average cycle time ½ daywww.flickr.com/photos/mc_masterchef/178245348/
Focus – Form a Team Do not underestimate Conway’s Law. Release Dev QA Mgmt OPS Build Mgmt
Focuson thevalue stream Main Metric: Release Cycle Time
Eat your Own Dog Food You understand the value of Continuous Delivery? Use the same principle for your Improvement Process. Baby Steps, Baby Steps, Baby Steps , Baby Steps….www.flickr.com/photos/mshades/2132689629/
Automation“ Automating the wrong thing to early is dangerous Bullshit ! • Automate everything you do twice. • Automation will be your rescue. www.flickr.com/photos/gibbisons/5538845069/
AutomationClick-Button DeploymentsOur Automation: Full E2E pipeline in one tool, from commit to prod (for Thor systems).
Further Topics … TDD DevOps QA Test Automation Cut your ATD Acceptance Criteria stories Pairing Trust People