This document outlines five principles for moving to a DevOps culture: embrace change and experimentation, automate everything, remove waste and decrease oscillations, implement measurement, and promote open information sharing and collaboration. It provides examples of practices like infrastructure-as-code, continuous delivery, and test automation that can be implemented on pilot projects to help adapt the culture. The overall message is that organizations must embrace these DevOps principles and adapt or risk falling behind.

1. How to move forward to a
DevOps Culture?
@derya_sezen

2. Principle 1
Culture: Embrace change & experimentation

3. No standardization!
Converge by time!

4. Change the KPIs!
Ops has MTTR, MTBF, RTO, RPO, but Dev not!

5. Principle 2
Automation: automate everything!

6. Principle 3
Lean: Remove waste, decrease oscillations

7. Principle 4
Measurement

8. Principle 5
Sharing: Open information sharing, collaboration, communication

9. Share practices

10. ChatOps boosts
DevOps!

11. funkydorian: hubot github status
Hubot: github status: new file logo.png
216 seconds ago

12. Practice 1: Infrastructure-as-code
- hosts: kloia.cloud
sudo: True
user: funkydorian
vars:
scriptdir: "/var/www/agile42"
wwwuser: "www-data"
wwwgroup: "www-data"
pbname: $inventory_hostname
tasks:
- name: Remove script directory
action: file path=$scriptdir/ state=absent
- name: Create script directory
action: file path=$scriptdir/ state=directory owner=$wwwuser group=$wwwuser mode=0755
- name: Checkout app on Github
action: git repo=git://github.com/funkydorian/start.git

13. What changed?
Configuration Management
evolved towards infra-as-code

14. Practice 2:
Continuous Delivery

15. Deploy is not Release!

16. Practice trunk-based
development

17. Practice 3:
Test Automation

18. Select 2-3 Pilot Project!

19. Project1: Continuous Delivery
Project2: Infrastructure-as-code/dockerize
Project3: Test Automation

20. Adapt or lose!