Even if there is one common definition for "DevOps", it should be re-defined every few months since DevOps ecosystem is changing fast. I am trying through this presentation to give my opinion about the DevOps engineer position, DevOps teams & a standardization framework for the DevOps success.

1. The Road Map to
Becoming a
DevOps
Professional

2. A Short History

3. Different Perspectives

4. Let’s Forget About
Definitions

7. DevOps Engineers, DevOps
Teams

9. ● 16% identified themselves as working in DevOps teams in 2014
● 19% in 2015
● 22% in 2016
State of DevOps

11. A Catalyst For Change
● Planting The 1st Seed
● Bootstrapping DevOps
● Costs / Risks

12. The Full Stack Developer

13. ● Transformation of all teams can come with costs and risks
● A Developer cannot do everything
Why ?

14. Skill #1:
Global/Strategic
Thinking &
Communication Skills

15. Skill #2: Code

20. Skill #3: Quality
Assurance

21. Skill #4: Security

22. Skill #5: Networking

23. Skill #6: Databases

24. Software Everywhere

26. With Great Power
Comes Great
Responsibility

27. Being More Productive

28. DevOps Should Be An
Evidence

29. Different Perspectives

30. Standardization

31. Patterns
● Successful DevOps Implementations (Netflix)
● The 12 Factor App (Heroku)
● The 13 Factor App (Mesosphere)
● Cloud Native Computing Foundation
● Web-scale (Google, Amazon ..)

32. Products, Not Projects
Features, Not Releases
Business-IT Alignment
Core Value Focus
Re-usability
Technology Agnosticism
Abstraction
Simplicity
Portability
Cost
Speed
Self-service
On-demand Resources
Scalability
Elasticity
Reactiveness
Resiliency
Interoperability
Security
Traceability
20 Patterns

33. 20 Patterns

34. 15 Factors
●
Embrace the DevOps Culture
●
Environment Isolations & Dev/Prod Parity
●
Anything as a Service
●
Use Cloud Computing
●
Use Containers
●
Automate Everything
●
Build Microservices
●
Create Business Capability Teams
& Deploy Business Services
●
Build API-First Products
●
Explicitly Isolate & Define Software Dependency
●
Externalize Configurations
●
Create Immutable Infrastructures & Artifacts
●
Stream Logs
●
Build Light & Business-Oriented Services
●
Use Health Checks & Create Self-healing System

35. ●
Yesterday’s DevOps =/= Today’s DevOps of Today =/= Tomorrow’s DevOps
●
DevOps engineer role and DevOps teams are becoming common in high and
meduim-performing IT organizations
●
The first challenge of a DevOps engineer/team is not falling in the silo model
●
The second challenge is being multidisciplinary
●
Don’t try to find the best definition for DevOps, focus on problems and solutions
instead
●
Standards are the best way to keep common goals between teams and unify
different perspectives and approaches
Conclusion

36. Thanks !
Aymen El Amri
@eon01
aymen@eralabs.io
Join DevOpsLinks: www.devopslinks.com