DevOps principles and practices - accelerate flow

DevOps transformation - Principles & Practices. High-performing organization DevOps Culture.

1. DevOps Principles and Practices Accelerate Flow Murughan Palaniachari

2. Who am I? Murughan Palaniachari Heading DevOps @ Euromonitor Website/Blog https://elevate-org.com/ LinkedIn https :// in.linkedin.com/in/murughan Twitter @ Murughan_P

3. Must-read DevOps books https:// www.linkedin.com/pulse/must-read-books-transform-organization-murughan-palaniachari

4. DevOps how it started http://itrevolution.com/the-history-of-devops /

5. DevOps how it started http://itrevolution.com/the-history-of-devops /

6. High-performing Organization.

7. High-performing Organization. https :// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

8. High-performing Organization.

9. High-performing Organization characteristics. https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

10. Source: https ://elevate-org.com/2016/12/14/top-10-devops-values /

11. https :// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

12. What is DevOps https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

13. What is DevOps https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

14. https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

15. https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

16. https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x

17. DevOps Principles and Practices - Increase the flow of work and reduce lead time Make our work visible. Limit work in progress. Reduce batch sizes. Everything in Source Control. Automate Everything . http://itrevolution.com/books/phoenix-project-devops-book /

18. Make our work visible Our work is Invisible. We cant see where flow is being impeded. We cant see when work is piling up, where is the waste, & why wait. Not all the team members has up-to-date information of work.

19. Make our work visible http://itrevolution.com/books/phoenix-project-devops-book / we need to make our work as visible as possible. Have Visual work boards, such as kanban boards or sprint planning boards. we can also manage our work so that it flows from left to right as quickly as possible. Helps us to measure metrics – WIP, Lead time and throughput.

20. Limit work in progress   Too many items in In-Progress state. Multitasking. Context switching. Interruptions

21. Limit work in progress(WIP)   Set WIP limit. Unless item is done we cant take more items. One piece flow from left to right. Queues Buffers Swim lanes https://theagileist.wordpress.com/2015/06/22/the-arrow-advanced-kanban-board /

22. Reduce batch sizes   Waterfall type release. Big bang release. Skyrocketing levels of WIP. Long lead time. Poor quality Late release W ait

23. Deploy small amount quickly and Frequently   Single-piece flow, where each operation is performed one unit at a time. T iny batches needed for continuous deployment. Use Trunk-based development. Faster feedback Reduce risk Less overhead Detect and resolve faster E ach change committed to version control is integrated, tested, and deployed into production

24. Everything in Source Control  

25. Reduce the number of handoff   Long deployment lead time months or quarters. Hundreds (or even thousands) of tasks to deploy. M ultiple departments to work on a variety of tasks. Too much of WAITS Knowledge loss

26. Reduce the number of handoff   Automate Everything

27. Automate Everything   Jez Humble says – Computers Perform Repetitive Tasks, People Solve Problems Code deployment should be automated, repeatable, and predictable Production-like environments at every stage. Enable Continuous integration of code Enable Continuous delivery pipelines Treat Infrastructure as code Environments must be created in an automated manner Make infrastructure easier to rebuild than to repair Environments should be stable, reliable, consistent, and secure . Build a fast and reliable automated validation test suite

28. https://xebialabs.com/periodic-table-of-devops-tools /

29. DevOps Culture - Communication & Collaboration, Trust, Decreasing silos, Fast Feedback loops, Systems thinking, LEAN, Automation, Measurement & Continuous Improvement  Make our work visible. Limit work in progress. Reduce batch sizes. Everything in Source Control. Automate Everything. Takeaways

30. http ://itrevolution.com/books/phoenix-project-devops-book / https:// www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x http:// itrevolution.com/devops-handbook https://elevate-org.com Reference/Further studies