A DevOps maturity assessment framework based on C.A.L.M.S. principles to guide teams through transformation journeys.
The adidas DevOps Maturity Framework is a structured assessment tool that helps teams evaluate and improve their DevOps practices based on the C.A.L.M.S. model. It provides maturity levels for capabilities that teams can use to self-assess their current state and understand what's needed to advance to higher levels of DevOps proficiency.
DevOps teams, engineering managers, and organizations undergoing DevOps transformation who need a structured approach to assess and improve their practices.
It offers a practical, evolving framework based on real-world experience from adidas, with clear maturity levels and continuous improvement guidance that helps teams systematically advance their DevOps capabilities.
The DevOps maturity framework was created by adidas as a guide for the first DevOps cup to support the teams on their DevOps transformation journey.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates the comprehensive C.A.L.M.S. framework, ensuring balanced coverage of cultural and technical aspects for DevOps improvement, as detailed in the README.
Provides clear maturity levels that teams can use for self-assessment and setting progressive goals, outlined in the framework documentation.
Embraces Lean principles and continuous evolution, encouraging teams to aim for perpetual advancement, as mentioned in the motivation section.
Includes the DevOps Maturity Increase Index (DMII) for measuring maturity progression quantitatively, adding objective assessment, as specified in the DMII.md file.
Based on adidas's internal DevOps journey, offering practical insights and proven approaches from a large organization's transformation.
Focuses on assessment rather than providing detailed implementation steps or tool recommendations, leaving teams to figure out execution on their own.
Relies heavily on team self-assessment, which can be subjective and prone to biases without external validation or auditing mechanisms.
With only a few markdown files and contact emails, the documentation may not be sufficient for teams without prior DevOps expertise or extensive examples.