DevOps, is a software engineering practice that focuses on bringing together the development team and the operations team for the purpose to automating any projects at every stage.

1. A software revolution in the making
DevOps
Murali Dhar Ojha

2. ✔ Why we need DevOps?
✔ What is DevOps?
✔ Adoption on Strategies
○ Principles & Practices
✔ Where to start?
✔ Summary
Introduction

3. Why we need DevOps?
Short dev cycles and focus on innovation
Agile software development practicing is increasing
Reduced deployment failure also rollbacks with minimum "Time to Recover"
Improved communication between team and ccollaboration
Reduced costs and IT headcounts

4. Is DevOps realistic for Enterprise IT?
Why we need DevOps?

5. Wall Of Confusion
Why we need DevOps?

6. Blamestorming

7. Agile Delivery

8. Combination of software
culture philosophies,
practices, and tools
Ability to deliver applications
and services faster than
traditional software
development processes
Agility in both Development &
Operations
Frequent feature
deployments
What is DevOps?

9. CULTURE AUTOMATION
MEASUREMENT SHARING
DevOps Values

10. Better IT
alignment and
business
responsiveness
Faster, smaller,
more frequent
releases
Improved: Time
to market,
Quality of code,
products and
services
Customer satisf
action,
Employee
satisfaction
Lower long-term
costs
DevOps’ Goals

11. • Challenges and Gap Analysis
• Goals and Maturity Model
• Roadmap and Transition Plan
• Architecture & Tooling Landscape
DevOps Adoption Strategies

12. ● The first way - Flow of work (Left to right)
○ Understanding and improving flow
● The second way
○ Amplifying feedback loops (Right to left)
● The third way
○ Continuous experimentation and learning
DevOps Practices

13. Practices First Way
✔ Continuous
– Integration
– Delivery
– Deployment
✔ Value stream mapping
✔ Kanban

14. Practices Second Way
Examples of feedback loops
– Peer review of production changes
– Dashboards
– Production logs
– Post mortems
– Incident / problem /change management data sharing

15. Practices Third Way
✔ Allocate time for improvement
✔ Create culture that fosters
– Continual experimentation
– Taking risks and learning from failure

16. Right Priorities

17. Where to start
✔ Figure out the first ‘why’?
✔ Simplifying of complex processes
✔ Automation for repeatable tasks / processes

18. Summary
✔ Lock in the Why
✔ Agree an incremental approach
✔ Address the Devops Culture and Values
✔ Experiment and learn from all experiences - always looking to
improve

19. Thank You