DevOps principles and practices - accelerate flow

30
DevOps Principles and Practices Accelerate Flow Murughan Palaniachari

Transcript of DevOps principles and practices - accelerate flow

Page 1: DevOps principles and practices - accelerate flow

DevOps Principles and Practices Accelerate FlowMurughan Palaniachari

Page 2: DevOps principles and practices - accelerate flow

Who am I?Murughan PalaniachariHeading DevOps @ Euromonitor

Website/Bloghttps://elevate-org.com/

LinkedIn https://in.linkedin.com/in/murughan

Twitter@Murughan_P

Page 3: DevOps principles and practices - accelerate flow

Must-read DevOps books

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

Page 4: DevOps principles and practices - accelerate flow

DevOps how it started

http://itrevolution.com/the-history-of-devops/

Page 5: DevOps principles and practices - accelerate flow

DevOps how it started

http://itrevolution.com/the-history-of-devops/

Page 6: DevOps principles and practices - accelerate flow

High-performing Organization.

Page 8: DevOps principles and practices - accelerate flow

High-performing Organization.

Page 9: DevOps principles and practices - accelerate flow

High-performing Organization characteristics.

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

Page 17: DevOps principles and practices - accelerate flow

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/

Page 18: DevOps principles and practices - accelerate flow

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.

Page 19: DevOps principles and practices - accelerate flow

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.

Page 20: DevOps principles and practices - accelerate flow

Limit work in progress

 • Too many items in In-Progress state.

• Multitasking.• Context switching.• Interruptions

Page 21: DevOps principles and practices - accelerate flow

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/

Page 22: DevOps principles and practices - accelerate flow

Reduce batch sizes • Waterfall type

release.• Big bang release.• Skyrocketing levels

of WIP.• Long lead time.• Poor quality• Late release• Wait

Page 23: DevOps principles and practices - accelerate flow

Deploy small amount quickly and Frequently

 • Single-piece flow, where each operation is performed one

unit at a time.• Tiny batches needed for continuous deployment.• Use Trunk-based development.• Faster feedback• Reduce risk• Less overhead• Detect and resolve faster • Each change committed to version control is integrated,

tested, and deployed into production

Page 24: DevOps principles and practices - accelerate flow

Everything in Source Control

 

Page 25: DevOps principles and practices - accelerate flow

Reduce the number of handoff

 • Long deployment lead time months or quarters.

• Hundreds (or even thousands) of tasks to deploy.

• Multiple departments to work on a variety of tasks.

• Too much of WAITS• Knowledge loss

Page 26: DevOps principles and practices - accelerate flow

Reduce the number of handoff

 

Automate Everything

Page 27: DevOps principles and practices - accelerate flow

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

Page 29: DevOps principles and practices - accelerate flow

• 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