DevOps Maturity Assessment
Score how your team builds, tests, deploys and runs software: version control, automated testing, releases, monitoring and incidents, and delivery measures, with next steps for each gap.
- Free
- No sign-up to try
- Works as you type
Rate how your team builds, tests, releases and runs software today.
0 of 15 answered
Answer the questions to see your score by area as you go.
Answer at least 12 of 15 questions to save your results as a Room.
How it works
How the DevOps Maturity Assessment works
- 1
Answer the questions
Pick the answer closest to where you are today. It takes a few minutes.
- 2
See your score
Your score by area appears as you answer, with the weakest areas first.
- 3
Save your results
Create a Room with your scores, next steps and an adviser to talk them through.
Worked example
What it makes
15 questions across 5 areas. Each answer scores 0 to 3; an area's score is its points as a share of the most it could get.
Source control and builds
- All code and configuration, including infrastructure, is in version control.
- Every change is built and checked automatically when it's committed.
- Changes are reviewed by someone else before they're merged.
Testing
- Automated tests run on every change, and a failing test stops the release.
- Tests cover the most important user journeys, not just small units of code.
- Test environments are created by script the same way as production.
Deployment and release
- Deploying to production is a scripted step anyone on the team can run.
- Releases are small and frequent rather than large and rare.
- A bad release can be rolled back or switched off quickly.
Monitoring and incidents
- Monitoring and alerts tell the team about problems before users report them.
- There's an agreed incident process, with written reviews after incidents.
- Logs and metrics are in one place the whole team can search.
Flow and culture
- The team tracks deployment frequency, lead time, change failure rate and time to restore.
- The people who build the service share responsibility for running it.
- Security checks, such as dependency scanning, run in the pipeline.
Results bands: Early (0+), Developing (40+), Established (70+), Leading (90+). A self-assessment from your own answers: a starting point for a conversation, not an audit, certification or professional advice.
Who it's for
Who uses it
Engineering managers
Find the biggest gap holding back delivery.
Platform teams
Agree priorities for the pipeline with the teams that use it.
CTOs
Get a quick, shared picture of practices across teams.
Good to know
What to consider
- It covers practices, not tools: any CI/CD stack can score well or badly.
- Answer for one team or service at a time; practices often differ between teams.
Questions
About the DevOps Maturity Assessment
Which delivery measures does it ask about?
Deployment frequency, lead time for changes, change failure rate and time to restore service. The assessment asks whether you track them, not what your numbers are.
Is this an audit or a certification?
No. It scores your own answers against a written rubric to show where you stand and what to do next. Use it to start a conversation, not as an audit, certification or professional advice.
Make your results now
Free, no sign-up to try. It becomes a Room you can edit, publish and share.
Create my resultsRelated
Related tools
- Agile Maturity AssessmentScore how your team really works today on backlog and planning, delivery rhythm, roles and collaboration, customer feedback and continuous improvement, with next steps for each weak area.
- Incident Postmortem ChecklistMake a blameless incident postmortem checklist: preserve the evidence, build the timeline, find causes, hold the review and track actions to done.
- Security Review ChecklistMake a security review checklist for a new tool or vendor: what it touches, sign-in and access, data handling, vendor evidence and a recorded decision.