DevOps Maturity Model

	A	B	C	D	E	F	G
1	Red Hat Consulting 2016
2
3	DevOps Maturity Model
4
5	Scoring is done Dev (1-5) and for Ops (I-V)
6
7	Additional 'synergy score' is assigned for collaboration and coordination between Development and Operations
8
9	None	Emerging	Established	Effective
10	No real communication between developers and operational teams during projects or at overall level through established projects	Leadership understanding of DevOps. Initial organisational and process structures in place. Policies and limited metrics in place	Project participation includes operational staff. Some direct deployment into production. Release cycles short and frequent for some platforms. Organisation is place to support and encourage cooperation	Well established DevOps process, with rapid deployment cycles and frequent updates. Continuous and improvement to development process.
11
12
13
14
15	DEVELOPMENT
16		1 – Initial	2 – Managed	3 – Defined	4 – Quantitatively Managed	5 – Optimizing
17	Test & Verification	Automated Unit tests on every build. Separate test environment	Automatic Integration Tests. Code analysis. Test coverage analysis.	Automatic component tests. (Some) automatic integration tests.	Full automatic acceptance tests. Automatic performance tests. Automatic security tests. Manual exploratory testing based on risk based testing analysis.	Verify expected business value. Defects found and fixed immediately (roll forward).
18	Information & Reporting	Baseline process metrics. Manual reporting.	Measure the process. Static code analysis. Automatic reporting.	Automatic generation of release notes. Pipeline traceability Reporting history	Report trend analysis. Real time graphs on deployment pipeline metrics.	Dynamic self-service of information. Customizable dashboards. Cross-reference across organizational boundaries.
19	Build & Deploy	Centralized version control. Automated scripts for building software. Nightly builds. No management of artifacts Manual deployment. Environments are manually provisioned.	Polling builds. Any build can be re-created from source control. Management of build artifacts. Automated deployments Automated provisioning of environments.	Triggered builds (commit hook). Fail builds if quality is not met (code analysis, performance, etc.) Push button deployment and release of any releasable artifact to any environment. Standard deployment process for all environments	Team prioritises keeping codebase deployable over doing new work. Builds are not left broken. Orchestrated deployments. Blue Green Deployments,	Zero touch Continuous Deployments.
20	Data Management	Data migrations unversioned and performed manually.	Automated and versioned changes to datastores.	Changes to datastores automatically performed as part of the deployment process.	Automatic datastore changes and rollbacks tested with every deployment.
21	Release	Infrequent and unreliable releases/	Painful infrequent but reliable releases.	Infrequent but fully automated and reliable releases in any environment.	Frequent fully automated releases. Deployment disconnected from release. Canary releases.	No rollbacks, always roll forward.
22	Culture & Organization	Teams organised based on platform/technology. Defined and documented processes.	One backlog per team. Adopt agile methodologies. Remove team boundaries. Share the pain.	Extended team collaboration. Remove boundary dev/ops. Common process for all changes.	Cross-team continuous improvement. Teams responsible all the way to production.	Cross functional teams.
23
24	OPERATIONS
25		I	II	III	IV	V	6
26	Standards	None or limited operational documentation	Patch and Release Management	Platform Standard Builds : infrastructure level elements(back up etc)	System Management and Reporting	SLA's and Service Catalogues
27	Deployment	Basic Provisioning	ISV and Inhouse ApplicationPackaging	Self service platform requests and deployment	Automated Build Testing for production platforms
28	Updates	Core Build : OS only	Infrastructure Standard Builds	Automated Provisioning and Patching	Asset Management and Integration
29	Configuration	No central configuration management	Build and install configuration	Limited central configuration management	Fully functional central configuration management and database	Orchestration and fully automated deployment and testing
30	Process	No documented process for production system deployment	Manual and documented workflow for production updates	QA and Staging Process	Self Service Provision	Workload Standard Builds
31	Security	No automated security hardening or testing		Compliance Auditing	Advanced Security Configuration
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100