DevOps become a buzzword in a last few years. Several companies, development and product teams have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. Do you think is achievable for you team or it’s still a bunch of drama? There is no common approach for measuring achievements and understanding how much DevOps’ich the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

1. DevOps checklist or how to
understand where is your
team in DevOps landscape
Mikalai Alimenkou
@xpinjection
http://xpinjection.com

3. Telegram channel
https://t.me/xpinjection_channel

4. Disclaimer
This talk is based on
personal experience

6. Are you DevOps enough?

7. Available maturity assessments
• https://services.google.com/fh/files/misc/cloud-cre-production-maturity-
assessment.pdf
• https://www.atlassian.com/devops/maturity-model
• https://devopsassessment.net/
• https://medium.com/@alexbmeng/site-reliability-engineering-principals-
fd52229bfcd6
• https://www.usenix.org/conference/srecon18asia/presentation/andersen
• https://www.usenix.org/conference/srecon18europe/presentation/quinn

9. #1. Do you have
“DevOps engineers”,
who “resolves” all
infrastructure relates
issues?

10. #2. Does everybody
know where he sits
and how he looks like?

11. #3. Do you invite
“DevOps engineer” to
all process meetings?
Do they actively
participate?

12. #4. Do you have DevOps
improvements/issues
backlog? How many of
them are fixed in a
month?

13. #5. Do developers
and infrastructure
engineers practice
pair programming?

14. #6. Do you have
clearly described
incident management
process? Are
developers involved?

15. #7. Can “DevOps
engineer” describe
system from
architectural point of
view?

16. #8. Do you have
regular infrastructure
tools workshops for
developers?

17. #9. Do developers
participate in
infrastructure tools
selection?

20. To make a
progress you
have to set a
clear goal first

21. Visualize you goal with checklist

22. Transfer status and team roles

23. Main checklist categories
• CORE INFRASTRUCTURE
Hardware, virtualization, network, containerization, datastores,
backups, monitoring
• DEVELOPMENT INFRASTRUCTURE
CI/CD, artefacts, static code analysis, proxy, load balancer,
databases, VCS
• DEVELOPMENT PROCESS
CI/CD jobs, Docker images, Docker stacks, communication
• CUSTOMER SUPPORT

24. CORE INFRASTRUCTURE: HARDWARE

25. CORE INFRASTRUCTURE: NETWORK

26. CORE INFRASTRUCTURE: VIRTUALIZATION

27. CORE INFRASTRUCTURE: VM LIFECYCLE

28. CORE INFRASTRUCTURE: CONTAINERS

29. CORE INFRASTRUCTURE: DATA STORAGE

30. CORE INFRASTRUCTURE: BACKUPS

31. CORE INFRASTRUCTURE: MONITORING

32. OMG! I just
wanted to be
DevOps…

33. DEV INFRASTRUCTURE: CI/CD (JENKINS)

34. DEV INFRASTRUCTURE: ARTIFACTS

35. DEV INFRASTRUCTURE: STATIC ANALYSIS

36. DEV INFRASTRUCTURE: PROXY/LB

37. DEV INFRASTRUCTURE: DATABASES

38. DEV INFRASTRUCTURE: VCS

39. DEV PROCESS: CI/CD JOBS

40. DEV PROCESS: COMMUNICATION

41. DEV PROCESS: DOCKER IMAGES

42. DEV PROCESS: DOCKER STACKS

43. CUSTOMER SUPPORT

44. Developers-driven approach to tooling

46. Summary
• Found and grow DevOps culture, not job titles
• Work as a team at all stages of development cycle
• Prepare and share tools for developers
• Build continuous education and knowledge sharing
• Share responsibilities and accountability for success
• Prefer specialization for complex activities
• Choose right tools together to automate routine

48. Success is always in team work

49. What to read?

50. @xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com