Tweet
Tweet

Slide 1

Slide 1 text

DevOps:  With  Great  Power   Comes  Great  Responsibility Dan  North Principal   Dan  North  &   Associates  Ltd.

Slide 2

Slide 2 text

@tastapod

Slide 3

Slide 3 text

Once  upon  a  time… Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod

Slide 4

Slide 4 text

Development  was  the  bottleneck Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod

Slide 5

Slide 5 text

Agile  methods  alleviated  this Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod

Slide 6

Slide 6 text

Deployment  became  the  bottleneck Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod

Slide 7

Slide 7 text

Agile  manifesto  is  based  on  values People and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Adapting to Change over Following a Plan @tastapod

Slide 8

Slide 8 text

yet  Agile  training  is  all  about  practises @tastapod

Slide 9

Slide 9 text

Agile  gives  the  dev team  full  autonomy @tastapod

Slide 10

Slide 10 text

Agile  gives  the  dev team  full  autonomy @tastapod

Slide 11

Slide 11 text

Dev  team  resents  formal  release  processes @tastapod

Slide 12

Slide 12 text

so  they  just  press  on  regardless… https://funnyjunk.com/user/peaceloveandponies @tastapod

Slide 13

Slide 13 text

Resulting  in  a  classic  tug-­‐of-­‐war https://www.flickr.com/photos/eoskins/9500756501 @tastapod

Slide 14

Slide 14 text

Team  autonomy  doesn’t  scale @tastapod

Slide 15

Slide 15 text

The  downstream  view  of  “autonomy” Let’s just push this to production @tastapod

Slide 16

Slide 16 text

The  downstream  view  of  “autonomy” @tastapod

Slide 17

Slide 17 text

The  downstream  view  of  “autonomy” @tastapod

Slide 18

Slide 18 text

The  downstream  view  of  “autonomy” @tastapod

Slide 19

Slide 19 text

Consistency  requires programme  thinking • The  programme is  bigger  than  any  single  team -­‐ Just  like  the  team  is  bigger  than  any  single  member • The  programme  includes  all the  stakeholders -­‐ Upstream,  downstream and  sideways • Consistency across  the  programme  is  king @tastapod

Slide 20

Slide 20 text

Consistency  comes  from collaboration • Collaboration  across  dev teams • Collaboration  between  dev team  and  ops team • Collaboration  on  tooling and  automation • Collaboration  on  process and  safeguards @tastapod

Slide 21

Slide 21 text

Spoiler:  DevOps  is  just  Dev  and  Ops Dev Ops @tastapod

Slide 22

Slide 22 text

This  is  not  DevOps Dev DevOps Ops @tastapod

Slide 23

Slide 23 text

Actively  address  the  cultural  divide I’M LISTENING! @tastapod

Slide 24

Slide 24 text

Treat  Ops as  first-­‐class  users • The  log file  is  a  user  interface • “The”  log  file  is  dead,  long  live  monitoring • Monitoring and  alerting are  first-­‐class concerns • Warnings  are  warnings,  errors  are  errors • Design as  though  you  are  on  call @tastapod

Slide 25

Slide 25 text

DevOps  brings  everyone  to  the  table… @tastapod

Slide 26

Slide 26 text

…at  least  nearly  everyone @tastapod

Slide 27

Slide 27 text

Next  up,  DevSecOps DevCompOps DevHROps DevFinOps @tastapod

Slide 28

Slide 28 text

And  now…  Questions! Thanks  for  listening http://dannorth.net dan@dannorth.net @tastapod @tastapod