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

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

3.
Disclaimer
This talk is based on
personal experience

4.
Are you DevOps enough?

5.
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

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

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

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

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

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

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

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

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

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

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

16.
Visualize you goal with checklist

17.
Transfer status and team roles

18.
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

19.
CORE INFRASTRUCTURE: HARDWARE

20.
CORE INFRASTRUCTURE: NETWORK

21.
CORE INFRASTRUCTURE: VIRTUALIZATION

22.
CORE INFRASTRUCTURE: VM LIFECYCLE

23.
CORE INFRASTRUCTURE: CONTAINERS

24.
CORE INFRASTRUCTURE: DATA STORAGE

25.
CORE INFRASTRUCTURE: BACKUPS

26.
CORE INFRASTRUCTURE: MONITORING

27.
OMG! I just
wanted to be
DevOps…

28.
DEV INFRASTRUCTURE: CI/CD (JENKINS)

29.
DEV INFRASTRUCTURE: ARTIFACTS

30.
DEV INFRASTRUCTURE: STATIC ANALYSIS

31.
DEV INFRASTRUCTURE: PROXY/LB

32.
DEV INFRASTRUCTURE: DATABASES

33.
DEV INFRASTRUCTURE: VCS

34.
DEV PROCESS: CI/CD JOBS

35.
DEV PROCESS: COMMUNICATION

36.
DEV PROCESS: DOCKER IMAGES

37.
DEV PROCESS: DOCKER STACKS

38.
CUSTOMER SUPPORT

39.
Developers-driven approach to tooling

40.
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

41.
Success is always in team work

42.
What to read?

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