This slide provides a birds eye view on DevOps. The slide was used to discuss devOps in comparison with Waterfall and Agile methodologies. It explains the reason for adopting DevOps and the Challenges and potential risks. It also goes through some Tools and Frameworks for Continuos Integration and Automation. Trunk Based Development, Testing Levels and Test Infrastructure and some other points discussed here.

5. Continuous innovation seamlessly released to
production multiple times a week without impacting
the consumers

12. Dev QA
Done Means “Tested”

16. Early Customer Feedbacks
Early Defect Detection
Reduced Costs
Increased ReleaseVelocity
Reduced Deployment Failure

18. Given operation X fails,Then the alarm operation-x:failed will be raised
No More – “It worked in my local box”

19. Dev
QAOpsDone Means “In Production”

21. Dev
QAOpsDone Means “In Production”

27. Framework
Elements
Functionality Examples
SoftwareVersion
Management
Software configuration control -
well-designed, flexible repository structure
Subversion, Git, Mercurial,
Perforce, and ClearCase
CI/CD Orchestration Executes scheduled and event-driven
jobs
Jenkins
Artifacts Repository Organized
store of artifacts related to the product.
Zephyr, HPQC
Continuous Delivery Minimize Downtime, Keep it Simple Ansible, Docker

29. Time between
merges
Difficulty of
merging Exponential
since
changes
compound
on each other

31. SIMPLE
• Developers do not need to know the details
• End-to-End Enhanced Velocity
• Quality feedback to developers

32. • Level 1 (As Part of CI)
• Static Analysis, Sanity Functional Test, Unit test & Test coverage
• Level 2 (Nightly Integration and Regression)
• End-to-End Feature Testing
• Level 3 (Weekly or Release)
• Interoperability tests, Regulatory tests, Performance benchmarking

35. Eliminate "DevOps is tools" thinking
Embrace DevOps as a
“thought framework”