What constitutes DevOps Culture, DevOps Principles and practices, DevOps core values, Development practices like TDD, BDD, Automated testing, Continuous Integration, Continuous Delivery, Infra as Code, Monitoring, Measurement, Continuous Learning

1. DevOps Culture
Murughan Palaniachari

2. http://www.unicomlearning.com/2017/Devops_Microservices_and_Containers_Summit_Bangalore/
Who am I?
Murughan Palaniachari
DevOps Coach
Organizer of
Cloud and DevOps meetup
Technical Agility Conference
http://aidevdays.com/
http://www.containerconf.in/
https://elevate-org.com/
https://devopsgames.com/
https://in.linkedin.com/in/murughan
@Murughan_P
With my Guru – John Willis & Jez Humble

3. Must-read DevOps books
https://www.linkedin.com/pulse/must-read-books-transform-organization-murughan-palaniachari
https://www.linkedin.com/pulse/my-learnings-from-book-goal-eliyahu-m-goldratt-murughan-palaniachari
@Murughan_P

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

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

6. @Murughan_P

7. @Murughan_P

8. I follow Agile
Methodologies and
you?
@Murughan_P

9. In reality we follow Water-Scrum-Fall!
https://continuousdelivery.com @Murughan_P

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

11. https://elevate-org.com/2016/12/14/top-10-devops-values/
Culture
Collaboration
Decreasing Silos
Trust
Failures are Learning Opportunities
System Thinking
No Blame Game
No Victims
Focus on end Goal
Sharing
Measurement
DevOps Values
Aim
Goal
Why
Blameless Post-mortem Lean
Automation
Continuous Improvement
@Murughan_P

12. Principles and Practices

13. Principle - Keep everything in Source Control
https://www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x
@Murughan_P

14. Limit work in progress
• Too many items in In-
Progress state.
• Multitasking.
• Context switching.
• Interruptions
@Murughan_P

15. 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/
@Murughan_P

16. Reduce batch sizes
• Waterfall type release.
• Big bang release.
• Skyrocketing levels of
WIP.
• Long lead time.
• Poor quality
• Late release
• Wait
@Murughan_P

17. 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
@Murughan_P

18. 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
@Murughan_P

19. @Murughan_P

20. @Murughan_P

21. Automate Everything

22. https://xebialabs.com/periodic-table-of-devops-tools/
@Murughan_P

23. • It is bringing in an aspect of Security in every process cycle of
Development.
• The purpose and intent of DevSecOps is to build on the mindset that
“Everyone is responsible for security"
DevSecOps
@Murughan_P

24. Why Automated testing?
• Happy Users
• Happy Business
• Happier Team
@robertsjason @Murughan_P

25. Mindset shift
Agile Testing by Lisa Crispin / Janet Gregory @Murughan_P

26. Agile testing pyramid & quadrant
@Murughan_P

27. TDD – Test Driven Development
“A software development process
that relies on the repetition of a
very short development cycle:
requirements are turned into
very specific test cases, then the
software is improved to pass the
new tests, only.” – Wikipedia
Fail
PassRefactor
1. Write a test,
watch it fail
2. Write just enough code
to pass the test
3. Improve the code
without changing the behaviour
@Murughan_P

28. Automated acceptance testing
@Murughan_P

29. @Murughan_P

30. This company lost $460 million in 45 min
and was out of business in 24 hours!!
@Murughan_P

31. Infrastructure as code
• Enable on demand creation
of dev, test, and production
environments
• Make infrastructure easier to
rebuild than to repair
• Any changes to
Infrastructure should go
through code not manual
changes.
@Murughan_P

32. https://continuousdelivery.com/ @Murughan_P

33. Continuous Integration
https://continuousdelivery.com/ @Murughan_P

34. Feature Branching
https://continuousdelivery.com/
@Murughan_P

35. Continuous Integration Principle
@Murughan_P

36. Zero Downtime releases
https://continuousdelivery.com/
@Murughan_P

37. Microservices
@Murughan_P

38. Microservices
@Murughan_P

39. Monitoring
• Create application logging telemetry that helps production
• Use telemetry to guide problem solving
• Enable creation of production metrics as part of daily work
• Create self-service access to telemetry and information radiators
• Find and fill any telemetry gaps
• Application and business metrics
• Infrastructure metrics
• Instrument and alert on undesired outcomes
• Use telemetry to make deployments safer
@Murughan_P

40. Metrics and Measurement
• You must measure for Continuous Improvement
@Murughan_P

41. High Performers
@Murughan_P

42. Continuous Learning
@Murughan_P

43. Takeaway
https://www.edx.org/course/introduction-devops-transforming-linuxfoundationx-lfs161x @Murughan_P