how we introduced continuous delivery?

Alex SchwartzPlaces Backend Delivery Team

How we introduced Continuous Delivery?

www.flickr.com/photos/burtonandy/4702810536/

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 ½ day

www.flickr.com/photos/mc_masterchef/178245348/

Focus – Form a Team

Dev QA

Build Mgmt

Release Mgmt OPS

Do not underestimateConway’s Law.

Kanban/Lean

Avatar

Focus on the value stream

Main Metric:Release Cycle Time

Eat your Own Dog FoodYou 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

“• Automate

everything you do twice.

• Automation will be your rescue.

Bullshit !

www.flickr.com/photos/gibbisons/5538845069/

AutomationClick-Button Deployments

Our Automation: Full E2E pipeline in one tool, from commit to prod (for Thor systems).

Further Topics …

QA

Pairing

TrustPeople

DevOps

Test Automation

TDD

ATD Acceptance Criteria

Cut your stories