This document provides an introduction to DevOps. It begins with background on the presenter and then outlines the topics to be covered: What is DevOps?, Why DevOps?, and How to DevOps?. Under What is DevOps?, it explains that DevOps emphasizes communication and collaboration between development and operations teams. It also discusses definitions of DevOps and what DevOps is not. The Why DevOps? section notes that DevOps can increase speed, reduce risks, and help companies adapt to changes. How to DevOps? involves cultural shifts, focusing on people, processes, tools, and adopting concepts like automation, lean, measurement and sharing.

1. Introduction to DevOps

2. About Me
● Technical Lead, SEEK Asia
● I was with 5 start-ups ( ServiceClicks, txn.my, aquamob,
tkt.my, CurrenSeek )
● Helped startups to design systems, build teams
● Currently helping enterprise change and adapt to Agile
and DevOps culture.
http://github.com/mazjs
Twitter : @mazharul_anwar

3. What we will be talking about today :
- What is DevOps ?
- Why DevOps ?
- How to Devops ?

4. What is DevOps ?

6. It’s really just teams that work well together

7. Developers VS Operations
NOT a DevOps Scenario ...

8. Developers ( Traditional way )
NOT a DevOps
Scenario ...

9. Operations ( Traditional Way )
NOT a DevOps Scenario ...

10. Developers VS Operations
When ...

12. Call it a culture, a movement, a philosophy.
In short, DevOps is a partnership between
development and operations that emphasizes
communication, collaboration, and integration.
- Atlassian

13. Gene Kim’s 3 way DevOps

14. What DevOps is not ?
Team(s), and/or person(s)
“Doing so perpetuates the kinds of silos that DevOps aims to break down and prevents
DevOps culture and practices from spreading and being adopted by the wider
organization” - Rouan Wilsenach

15. History of DevOps

17. Why DevOps ?

18. Speed in Software Development
Why is it Important ?

19. “It's Not the Big That Eat the Small...It's the Fast That Eat the Slow”
- Jason Jennings
Business needs velocity
( The need for agility )

20. V-Cycle is slow and risky

21. Chances are , your budget and/or timeline
will overrun.
( Riskier and Slower )

22. Unpredicted changes
( Black Swan Events )

23. Many more ...

24. How to overcome these problems ?

25. Iterative and Incremental Development

26. Fast Delivery

27. Companies that
adopted DevOps

28. Companies that
adopted DevOps

29. Benefits of DevOps

30. Teams that practice DevOps deploy 30x
more frequently, have 60x fewer failures, and
recover 160x faster.
- Puppet Labs 2016 State of DevOps Repost

31. Benefits of DevOps
- Faster Delivery of features
- Improved communication and collaboration
- More time to innovate, less bug fixings
- Continuous product delivery
- Productive and happy teams
- Better career development opportunities

32. Building EVP
( Employee Value Proposition )

33. How to DevOps

34. Cultural Shift
https://martinfowler.com/bliki/DevOpsCulture.html

35. There are no simple 5 steps to get there. It is
a journey, and people can support it by
working in small batches, making their work
visible, and committing to a blameless
culture that responds to failure with learning
- Jessica DeVita

36. Journey … to find neverland ?

37. No … But a right balance of ...

39. People
● Cultural paradigm shift
● Shared responsibility
● Cross training of skills
● Always asking : Is my application driving business
value ?
● Building quality in the development process
● Forms Autonomous Teams

40. Process

41. Tools

42. Key Concepts we can adopt
- Culture
- Automation
- Lean
- Measurement
- Sharing

43. Key Concepts we can adopt

44. Culture
“Even with the best tools, DevOps is just another buzzword if you don't have the right culture.” - Rouan Wilsenach
- Cross Functional Collaboration
- Product / Project Oriented team instead of functional team
- Having a common goal and plan to reach it together as a team
- Blameless Culture
- Autonomous
- Communication Driven Development

45. Automation
- Eliminating repetitive manual works
- Continuous Integration
- Continuous Delivery
- Configuration as Code
- Infra as Code

46. Lean
- Continuous Iterations & Improvement
- Failing fast and failing often

47. Measurement
- Feature usage
- MTTR
- System failures
- Application failures
- Deployments
The first step is to measure whatever can be easily measured. This is OK as far as it goes. The second step is to disregard that which
can't be easily measured or to give it an arbitrary quantitative value. This is artificial and misleading. The third step is to presume that
what can't be measured easily really isn't important. This is blindness. The fourth step is to say that what can't be easily measured really
doesn't exist. This is suicide.
— Daniel Yankelovich "Corporate Priorities: A continuing study of the new demands on business." (1972)

48. Sharing
- Sharing responsibilities, success and failures among teams
- Shared Codebase / Collaboration / Toolset among teams
- Open Information sharing; Go Open Source!

49. Thank you!

50. Q&A

51. Resources
- https://www.docker.com/sites/default/files/Docker%20Transition%20to%20DevOps.pdf
- https://newrelic.com/devops/benefits-of-devops
- https://www.atlassian.com/devops
- https://theagileadmin.com/what-is-devops/
- https://martinfowler.com/bliki/DevOpsCulture.html