DevOps transforms software operations by fostering a culture of shared responsibility among development and operations teams, where developers take ownership of shipping, monitoring, and responding to software incidents. It encourages turning traditional operations into engineering roles and emphasizes the importance of measuring success in alignment with business objectives. Ultimately, DevOps aims to deliver applications and services at a higher velocity through collaboration and effective communication.

1. How DevOps changed the way we
operate software
SERHAT CAN | TECHNICAL EVANGELIST @ATLASSIAN | AWS COMMUNITY HERO | @SRHTCN

2. DevOps
Devops
devops

3. @srhtcn
• DevOpsDays global team
• DevOpsDays İstanbul
• AWS Community Day Turkey
• ServerlessDays İstanbul
Conferences
• Cloud and Serverless Turkey
• Devops Turkey
Community
About me
Engineer, Technical Evangelist at Atlassian
AWS Community Hero

4. Why
Why
How
What

5. THE PROBLEM DEVOPS AIMS TO SOLVE
Dev Ops

6. THE PROBLEM DEVOPS AIMS TO SOLVE

7. A culture where people, regardless of title or background, work
together to imagine, develop, deploy and operate a system.
DEVOPS DEFINITIONS I LIKE
Ken Mugrage

8. DevOps is the combination of cultural philosophies, practices, and
tools that increases an organization’s ability to deliver applications
and services at high velocity: evolving and improving products at a
faster pace than organizations using traditional software
development and infrastructure management processes.
DEVOPS DEFINITIONS I LIKE
Amazon Web Services
aws.amazon.com/devops/what-is-devops/

9. Let me explain.
YOU SAY DEVOPS IS NOT A JOB TITLE OR SOMETHING WE DO?
Companies have their own realities. Factors like legacy apps,
company size, sector or even engineer’s backgrounds affect
what DevOps is for them.

10. @srhtcn

11. 1. CREATE A CULTURE OF
SHARED RESPONSIBILITY
AMONG DEV AND OPS.

12. One goal
Customer oriented.
Ownership
Take responsibility.
Transparency
Open
communication.
Leadership
support
We trust you make
the best decision.
Culture of shared responsibility

13. @srhtcn
Pipelines

14. @srhtcn
FORMULA 1: BEST OF THE BEST

15. @srhtcn
F1 DRIVERS KNOW EACH
COMPONENT OF THE CAR VERY
WELL, NOT JUST ENGINES.

16. 2. DEVELOPERS TAKE OWNERSHIP:
THEY SHIP, LOG, MONITOR AND
RESPOND TO INCIDENTS

17. 2. DEVELOPERS TAKE OWNERSHIP:
THEY SHIP, LOG, MONITOR AND
RESPOND TO INCIDENTS
Dev - Ops
Gain empathy
Dev - Management
Increasing demands

18. @srhtcn
WE DON’T HAVE TO
BUILD & MANAGE
A LOT OF THINGS
ON OUR OWN.
Constructor Engine
Alfa Romeo Ferrari
Ferrari Ferrari
Haas Ferrari
McLaren Renault
Mercedes Mercedes
Red Bull Honda
Renault Renault
Williams Mercedes

19. 3. TURN TRADITIONAL OPS
INTO AN ENGINEERING ROLE.

20. 3. TURN TRADITIONAL OPS
INTO AN ENGINEERING ROLE.
This does NOT mean using:
• Docker
• Kubernetes
• Jenkins

21. @srhtcn

22. @srhtcn
PETS VS CATTLE

23. @srhtcn
“A good intention, with a bad approach,
often leads to a poor result.”
Thomas A. Edison
4. DESIGN AND ARCHITECT TO
FOSTER COLLABORATION
AND OWNERSHIP.

24. @srhtcn

25. @srhtcn
https://www.atlassian.com/blog/software-teams/modern-software-development-trends

26. @srhtcn
5. TRACK AND MEASURE
WHAT IS IMPORTANT FOR
THE BUSINESS.

27. An Emerging SRE Concept:
Service Level Objectives - SLO

28. How to measure “DevOps” success?
Remember: Tie technical goals to business goals
• Lead time for changes
• Deployment frequency
• Time to restore service
• Change failure rate

29. How DevOps changed the way we operate software
Created a shared responsibility among dev and ops
Developers started taking ownership
Ops became an engineering role
Built architectures to foster collaboration and ownership
Started measuring what matters for the business

30. Thank you!
SERHAT CAN | TECHNICAL EVANGELIST @ATLASSIAN | AWS COMMUNITY HERO | @SRHTCN