With Great Power Comes Great Responsibility

DevOps methods enable teams to ship software more quickly and frequently but that advantage is negated unless the reliability and sustainability practices of operations teams are included throughout planning and execution. Too many organizations that rapidly ‘sheep dip’ development teams in Agile practices that focus at the team level ignore the implications that arise at programme scale. Join this exclusive webinar with Dan North of DNA who will discuss how enterprise IT teams can enable collaboration without coercion. Attendees will learn how optimizations can be leveraged across both dev and ops teams so that the constraints that arise in stovepiped approaches are avoided.

Transcript

1. DevOps:  With  Great  Power   Comes  Great  Responsibility Dan  North Principal   Dan  North  &   Associates  Ltd.
2. @tastapod
3. Once  upon  a  time… Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod
4. Development  was  the  bottleneck Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod
5. Agile  methods  alleviated  this Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod
6. Deployment  became  the  bottleneck Define •Business  case •Requirements •Feasibility Develop •Design •Code •Test Deploy •Prepare   environments •Release @tastapod
7. 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
8. yet  Agile  training  is  all  about  practises @tastapod
9. Agile  gives  the  dev team  full  autonomy @tastapod
10. Agile  gives  the  dev team  full  autonomy @tastapod
11. Dev  team  resents  formal  release  processes @tastapod
12. so  they  just  press  on  regardless… https://funnyjunk.com/user/peaceloveandponies @tastapod
13. Resulting  in  a  classic  tug-­‐of-­‐war https://www.flickr.com/photos/eoskins/9500756501 @tastapod
14. Team  autonomy  doesn’t  scale @tastapod
15. The  downstream  view  of  “autonomy” Let’s just push this to production @tastapod
16. The  downstream  view  of  “autonomy” @tastapod
17. The  downstream  view  of  “autonomy” @tastapod
18. The  downstream  view  of  “autonomy” @tastapod
19. 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
20. 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
21. Spoiler:  DevOps  is  just  Dev  and  Ops Dev Ops @tastapod
22. This  is  not  DevOps Dev DevOps Ops @tastapod
23. Actively  address  the  cultural  divide I’M LISTENING! @tastapod
24. 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
25. DevOps  brings  everyone  to  the  table… @tastapod
26. …at  least  nearly  everyone @tastapod
27. Next  up,  DevSecOps DevCompOps DevHROps DevFinOps @tastapod
28. And  now…  Questions! Thanks  for  listening http://dannorth.net dan@dannorth.net @tastapod @tastapod