Score your organization's DevOps maturity across automation, culture and metrics.
This maturity score combines the four DORA metrics (deployment frequency, lead time for changes, change failure rate, MTTR) with two supporting capability dimensions (automation, monitoring/observability), each self-rated 1-5, into a single weighted score. The DORA metrics are weighted at 0.2 each (80% of the total) since they're outcome-based and empirically linked to organizational performance, while automation and monitoring are weighted at 0.1 each (20% total) as enabling capabilities. Categories — Beginning, Developing, Defined, Managed, Optimizing — mirror common capability maturity model (CMM) terminology adapted for DevOps.
score = df×0.2 + lt×0.2 + cfr×0.2 + mttr×0.2 + auto×0.1 + mon×0.1
The four DORA metrics are outcome measures with published research correlating them to organizational performance; automation and monitoring are important enabling practices but are inputs rather than validated outcomes, so they carry less weight in this model.
Use the helper text ranges as anchors, but for the most defensible score, base each 1-5 rating on your actual DORA metric values (e.g. actual deployment frequency, actual lead time) rather than a subjective feeling of maturity.
Elite-tier DORA metrics across the board, fully automated CI/CD with infrastructure as code, comprehensive observability with proactive alerting, and a culture of blameless postmortems driving continuous improvement.
Yes — a low weight dimension like automation can't compensate for weak outcomes in the DORA metrics, which is intentional: the model rewards actual delivery performance over process investment alone.