How We Introduced Continuous Delivery?

688 views
607 views

Published on

My talk at the first NOBEL conf, an internal confernce by Nokians for Nokians in Berlin.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
688
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How We Introduced Continuous Delivery?

  1. 1. How we introduced Continuous Delivery? Alex Schwartzwww.flickr.com/photos/burtonandy/4702810536/ Places Backend Delivery Team
  2. 2. 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/
  3. 3. Focus – Form a Team Do not underestimate Conway’s Law. Release Dev QA Mgmt OPS Build Mgmt
  4. 4. Kanban/Lean Avatar
  5. 5. Focuson thevalue stream Main Metric: Release Cycle Time
  6. 6. 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/
  7. 7. 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/
  8. 8. AutomationClick-Button DeploymentsOur Automation: Full E2E pipeline in one tool, from commit to prod (for Thor systems).
  9. 9. Further Topics … TDD DevOps QA Test Automation Cut your ATD Acceptance Criteria stories Pairing Trust People

×