So you think your release is too complex for Continuous Delivery…

Adriaan de Jonge

Let’s  start  with  a  bit  of  introduction

Why  is  your  release  so  complex?

Common  patterns  in  complex  releases

▪ Dependencies ▪ Size ▪ Legacy technology ▪ Not supported by standard tools ▪ Variation in technology ▪ Program lives in a database instead of code ▪ Vendors/Suppliers follow their own process ▪ Organized in silo's ▪ Rules & regulations ▪ Approvals

Let’s  look  at  each  one  of  them.

Problem:  Dependencies

Compo

nent

A

v12

Com

pone

nt B

v238

Com

pone

nt C

v1

022

Com

ponent D

v3

Component E

v982

Component F

v43

Umbrella v1013

Solution:  Create  Umbrella  Versions

Problem:  Legacy  technology

Solution:  Pace  Layering

Problem:  Size

Solution:  Release  Trains

WE TH FR MO TU WE TH FR MO TU WE

Unit

Integration

Performance

Exploratory

UAT

On commit

Every hour

Every week

Every sprint

Every sprint

Acceptance Every night

PVT

Solution:  Release  Trains

Problem:  Not  supported  by  standard  tools

Problem:  Variation  in  technology

Problem:  Program  in  a  database  instead  of  code

Solution:  Favor  principles  over  practices

Problem:  Vendors  follow  their  own  process

Solution:  Ask  your  vendors  to  follow  your  principles

Problem:  Organized  in  silos

Solution:  Create  multi-­‐disciplinary  teams

•  Specialty oriented •  Functionally organized •  Project focused •  Work with Individuals

•  Work oriented •  Functionally •  Product focused •  Work with Teams

End to end responsible product focussed teams. DONE = LIVE!

From To Feature teams

Testers

Business Analysts

Development

Operations Systems Management

Problem:  Approvals  cost  time

Solution:  Create  a  Value  Stream  Map

Solution:  Use  a  tool  to  track  the  real  world

Problem:  “Rules  &  regulations  prohibit  DevOps”

Solution:  Discuss  the  “why”  behind  those  rules

Discussion