The document provides an introduction to DevOps, highlighting its importance in enhancing business success through improved development speed, communication, and software quality. It emphasizes the shift from traditional development processes to a collaborative DevOps approach that integrates continuous integration and automated operations. Additionally, it outlines key principles, the role of the DevOps engineer, and steps to implement DevOps effectively within organizations.

1. DevOps - An Introduction
Joe Tavin

2. Agenda
● Abstract.
● Rise of DevOps.
● DevOps Principles.
● Implementing DevOps.
● The DevOps Engineer.
2

3. About Me
● Education: Software Engineer, BSc. CS
● Experience: Since 2012, in DevOps roles
● Current: Senior SRE @ BigPanda
3

4. Abstract
● DevOps is a mode of Operating the Engineering
Organization.
● Having a team or person with a DevOps title does
Necessarily mean Engineering is working as DevOps.
4

5. DevOps - Why?
Research shows:
DevOps enhances Business Success.
Companies that utilize DevOps tend to be:
● More innovative
● Market leaders
● More successful businesses
5

6. Rise of DevOps
6

7. Developers vs Operators
7
More Features System Stability

8. Agile
● Competitive landscape requires Agile development
8

9. More Features - Less Stability
9

10. Solution: DevOps!
10

11. Benefits of DevOps
● Improve
○ Development Speed
○ Communication
○ Quality Deliverables
● Eliminate/Reduce
○ Siloed Culture
○ Long Feedback Loops
○ Buggy Code
○ Angry Users
○ Frustrated Developers
○ Frazzled Operations Engineers
11

12. DevOps Fundamentals
12

13. DevOps Philosophy
● Agile Says:
○ Development not complete until delivered to FEATURE OWNER
● DevOps Says:
○ Engineering process not complete until delivered to END USER
13

14. Engineering without
DevOps
14

15. Development Style
● Waterfall
15

16. 16
Develop
Features
Ensure
Quality and
Stability
Deliver to End User
Developers QA Operations
Development Process - No DevOps

17. 17
Develop
Features
Ensure
Quality and
Stability
Deliver to End User
One Process, Different Owners - Devops own the process!
Developers Dev/QA
DevOps
Development Process - With DevOps
Operations/Dev

18. DevOps Should
● Reduce Organizational Silos
● Accelerate Development Speed
● Improve Deliverable Software Quality
18

19. Important DevOps Principles
● Continuously Integrate / Deploy / Deliver (CI/CD)
○ Integrate with other system components.
○ Short, fast, automated, repeatable cycles.
○ Test often at many different stages of the development pipeline.
● Operations Automation
○ Everything required for operating the software is automated.
○ Operations are defined as code, For example: Infrastructure as code - IAAC.
19

20. Implementing DevOps
20

21. How?
1. Analyze Software Delivery Path from Developer to the End User.
2. Define Processes.
3. Automate them.
4. Iterate!
21

22. From Zero to DevOps
● Deploy Often.
● Break things.
● Understand pain points.
● Gain visibility.
● Fix.
● Measure.
● Iterate!
22

23. The DevOps Engineer
23

24. Skill Set
● Understands SDLC (Software Development Lifecycle)
● Software Development (debugging, profiling, logs)
● IT and Networking
● Cloud Infrastructure
● Security
● Integration and Automation Tools
● Continuous Learner
24

25. Culture
● Generalist vs Specialist
● Process Oriented Mindset
● Continuous Learner
● Automation Creator and Facilitator
25

26. Questions?
26

27. Stay in Touch!
Linkedin | WhatsApp
27

28. 28