This document provides an overview of Chef's DevOps Journey Assessment (DOJO). The DOJO evaluates an organization's DevOps maturity across two dimensions: working with people and working with machines. It describes a DevOps journey map and phases. The DOJO process involves setting individual and group scores for statements across various sections like organizational culture, coding practices, continuous integration, and compliance automation. The goals are to assess the current state and agree on six-month goals. Chef consultants facilitate the DOJO and provide follow-up support through Chef's customer success program.

1. VISUALIZING YOUR
JOURNEY WITH CHEF
/ /
/ /
Michael Goetz mpgoetz@chef.io @michaelpgoetz
Justin Redd justinredd@chef.io @justinredd

2. DO YOU KNOW WHERE YOU'RE
GOING?

3. DO YOU KNOW HOW TO GET
THERE?

4. HOW DO YOU MEASURE
SUCCESS?
Working with People
Working with Machines

5. HOW DO YOU GET THERE
WITHOUT TEARING THE WHOLE
THING DOWN?

6. CHEF DOJO
DEVOPS JOURNEY ASSESSMENT

7. AGENDA
The DevOps Journey
DOJO Mechanics
Working with People
Working with Machines

8. THE DEVOPS JOURNEY
DevOps Journey Map
The Journey Phases
What You Get When We Are Done

9. DEVOPS JOURNEY MAP

10. THE JOURNEY PHASES
Multiple phases can and should be worked in parallel
The earlier phases evolve significantly as the journey progresses
It's natural to skip or inconsistently implement certain phases, so be
aware of problems this causes in the later phases

11. WHAT YOU GET WHEN WE ARE
DONE

12. DOJO MECHANICS
Safety
Scoping
Goal Setting
Our Scale
Scoring

13. SAFETY
This is a safe space. All of you should feel free to
share openly and honestly without repercussions.

14. SCOPING
We focus on a service and the people who provide
it.
Development Operations
Management Architecture
Testing Security
Compliance Release
Support

15. GOAL SETTING
In this exercise, we want to assess your current
state. After you have that, we want you to agree to a
six month goal.

16. OUR SCALE
Score Description
0 Not planned
1 Planned
2 Inconsistently implemented in some areas
3 Consistently implemented in some areas
4 Consistently implemented throughout the
organization

17. SCORING
The sections of the DOJO each have a few
statements. For each section, we will follow this
process:
Individuals score each statement for current state
Group shares scores
Group discusses differing scores
Repeat for goals

18. WORKING WITH PEOPLE
1. Organizational Success Factors
2. Organizational Culture
3. Data-Driven Decision Making
4. Coding Practices

19. ORGANIZATIONAL
SUCCESS FACTORS
1. The organization widely recognizes IT as a competitive advantage to
its business
2. The organization's leadership team recognizes IT as a competitive
advantage
3. Clearly defined business champions lead change
4. Clearly defined technical champions lead change
5. A project with measurable business value been selected to be
automatically deployed to production
6. There is a clear understanding of why the business is undertaking a
technology transformation

20. ORGANIZATIONAL
CULTURE (WESTRUM)
1. Information is actively sought
2. Responsibilities and risks are shared
3. Cross-functional collaboration is encouraged and rewarded
4. New ideas and innovations are welcomed
5. Failure leads to inquiry

21. DATA-DRIVEN DECISION
MAKING
1. The organization has quantifiable goals
2. The organization's goals are visible to all of its members
3. Data is collected and used to make decisions
4. Cost and utilization are monitored
5. Monitoring data from pre-production environments is used to make
release decisions
6. Monitoring provides business performance information

22. CODING PRACTICES
1. Developers follow code inspection standards (rubocop, foodcritic,
etc.)
2. Code reviews are performed and results are shared with developers
3. Every change is reviewed by at least two people with relevant skill
and contextual knowledge
4. Software and automation components are shared and co-
developed
5. Any potential contributor to a project can find its code and
documentation with minimal assistance
6. Regularly scheduled automation demos occur
7. The codebase is almost always in a releasable state

23. WORKING WITH
MACHINES
1. Version Control
2. Chef Local Development
3. Continuous Integration
4. Chef Code Deployment
5. Application Deployment
6. Continuous Delivery
7. Virtualization as a Service
8. Full-Stack Automation
9. Compliance Automation
10. Sustaining Operations Culture

24. VERSION CONTROL
1. All source code is stored in a version control system (VCS)
2. All infrastructure and deployment code is stored in VCS
3. Developers can view projects in VCS
4. Developers suggest and/or provide changes to projects in VCS
5. Developers create new projects in VCS as needed
6. VCS shows who is responsible for each codebase
7. Code documentation is easy to write and is viewable by all with VCS
access

25. CHEF LOCAL
DEVELOPMENT
1. Developers provision their own isolated VMs as needed
2. Developers use VM images that closely resemble production
systems
3. Developers use Chef development tools (ChefDK, Vagrant, etc)
4. Chef development workstation setup is automated
5. Developers download code dependencies in a friction-free manner
6. Developers run unit tests (ChefSpec) locally
7. Developers run functional tests (ServerSpec) locally
8. Developers run compliance checks (InSpec) locally
9. Developers use Test Kitchen to verify that cookbooks work as
intended

26. CONTINUOUS
INTEGRATION
1. All projects use a CI service
2. The CI service automatically tests new branches
3. CI job templates exist for each type of software project (Chef
cookbook, Java app servers, Node.js app, etc.)
4. CI jobs lint projects
5. CI jobs unit test projects
6. CI jobs integration test projects
7. CI jobs execute functional tests against projects
8. CI jobs verify compliance of projects
9. CI makes the quality of the code base highly visible
10. CI confirms that versions are unique
11. CI jobs automatically update dependencies
12. CI jobs use monitoring to assess each change's effect on system
health

27. CHEF CODE
DEPLOYMENT
1. CI jobs upload cookbooks to a Chef server
2. Cookbook updates are only uploaded via CI
3. All non-cookbook Chef policy (environments, roles, data bags, etc.)
is only uploaded via CI
4. CI jobs pin dependencies so that they cannot be modified in later
deployments
5. CI jobs assign a set of cookbook versions to a Chef environment
6. Cookbook deployments are automated
7. Cookbook deployment automation manages the sequence of
deployments

28. APPLICATION
DEPLOYMENT
1. Applications are deployed without manual intervention
2. Applications follow a clear promotion path (e.g., Dev -> QA ->
Staging -> Production)
3. Application deployment automation manages the sequence of
deployments (e.g.: Database schema first, then app servers)
4. CI jobs automatically update, pin, and test runtime dependencies of
applications
5. Application deployment automation performs parallel, rolling,
and/or canary deployments
6. Deployments are run during the business day without causing
negative user experiences

29. CONTINUOUS DELIVERY
1. All validation and deployments are executed in a pipeline that goes
from source control all the way to production
2. Small batches of work flow through the pipeline
3. Changes are released weekly, if not more frequently
4. Changes that pass validation are automatically released to
production

30. VIRTUALIZATON AS A
SERVICE
1. All servers are provisioned via APIs
2. The API is a generally accepted API such as EC2, Azure, OpenStack,
vSphere, Docker
3. Access restrictions allow authorized users (e.g., developers and
operations) to provision resources, and deny unauthorized users
4. Resources are provisioned in a friction-free manner
5. System images are built via an automated process
6. System images are built from scratch or from a well known, trusted
origin
7. System images are built in a pipeline
8. System images are frequently updated

31. FULL-STACK
AUTOMATION
1. Storage resources are provisioned by code
2. Networking resources are provisioned by code
3. Identity services are managed by code
4. DNS is configured by code
5. Messaging queues are provisioned by code
6. Security validation is performed by code
7. Performance validation is performed by code
8. The entire application is test provisioned and deployed in an
alternate datacenter

32. COMPLIANCE
AUTOMATION
1. Compliance policies are expressed in code
2. Compliance is checked automatically
3. Compliance automation removes non-compliant nodes from
production upon detection
4. Nodes are destroyed beyond a certain age (e.g. 30 days)

33. SUSTAINING
OPERATIONS CULTURE
1. Automated services stress the production system (e.g. Chaos
Monkey)
2. Production alerts first notify those who wrote the code
3. Operations, Security, Network, Automation, Testing, and
Compliance experts provide developer-friendly tools and coaching
to enable development teams

34. HOW DO I DO THIS WITH MY
ORGANIZATION?
Participate in the Customer Success Program at Chef
Bi-annual workshops at your location
Not in the program? Contact us anyway and we can work
something out!
sales@chef.io
success@chef.io
mpgoetz@chef.io
justinredd@chef.io

35. THANK YOU!