I built an open-source tool called *DevOps Maturity* to help teams assess where they are in their DevOps journey — and figure out what to improve next.
In many teams, evaluating DevOps maturity across CI/CD, testing, security, and collaboration is often fuzzy or based on gut feeling. This tool aims to make that process clearer and more actionable.
*Key features:*
- A lightweight CLI and web toolkit to assess your maturity
- A clear specification model to guide team discussions
- An extensible design, so you can adapt it to your workflows
It’s designed to be team-friendly, useful in retros, onboarding, or improvement planning sessions.
Would love to hear your thoughts on:
- How do you measure maturity in your DevOps process?
- Do you use scoring models or just gut feeling?
- What would make this kind of tool more useful in your team?
I built an open-source tool called *DevOps Maturity* to help teams assess where they are in their DevOps journey — and figure out what to improve next.
In many teams, evaluating DevOps maturity across CI/CD, testing, security, and collaboration is often fuzzy or based on gut feeling. This tool aims to make that process clearer and more actionable.
*Key features:* - A lightweight CLI and web toolkit to assess your maturity - A clear specification model to guide team discussions - An extensible design, so you can adapt it to your workflows
It’s designed to be team-friendly, useful in retros, onboarding, or improvement planning sessions.
Would love to hear your thoughts on: - How do you measure maturity in your DevOps process? - Do you use scoring models or just gut feeling? - What would make this kind of tool more useful in your team?
Links:
- Toolkit: https://github.com/devops-maturity/devops-maturity - Spec: https://github.com/devops-maturity/spec
Happy to hear feedback, ideas — or just chat about maturity models. PRs welcome too!
Thanks for reading