DevOps Maturity Model

DevOps isn't a destination, it's a journey towards a frequent and more reliable release pipeline, automation and stronger collaboration between development, IT and business teams. This maturity model is designed to help you assess where your team is on their DevOps journey.

Base

Congrats, it looks like you're making the first strides in your DevOps journey!

People and culture first

The first step in moving to DevOps is to pull from agile principles - people first, then process and tools.

Culture is the foundation on which every successful team is built and is a core ingredient of a DevOps implementation. A DevOps culture brings a sense of shared responsibility across teams, yields faster time to market and faster resolution times, and helps mitigate unplanned work.

One small but impactful way to initiate culture change is to run workshops that identify areas of improvement between your dev & ops teams. To help, we've built a DevOps playbook.

Hungry for more?

Beginner

Go lean with Agile & Git

In looking at the three ways of DevOps - flow, amplify feedback, and continuous learning and experimentation - each phase flows into the other to break down silos and inform key stakeholders.

To master 'flow' teams need to make work visible across all teams, limit work in progress, and reduce handoffs to start thinking as a system, not a silo. One way to start approaching 'flow' is through practices like agile. Find out more here.

Another way to master 'flow' is by moving to distributed version control systems (DVCS) like Git, which is all about quick iterations, branching and merging - all things you need in a lean DevOps environment. Learn more here.

Hungry for more?

Advanced

Amplify feedback for faster resolution

In looking at the three ways of DevOps - flow, amplify feedback, and continuous learning and experimentation - each phase flows into the other to break down silos and inform key stakeholders.

Amplifying feedback can help you catch failures before they make it downstream, and accelerate your time to resolution. One easy way to speed up feedback is by automating notifications so that teams are alerted to incidents or bugs when they happen. See how Atlassian's Site Reliability Engineers do incident management and practice ChatOps for conversation-driven development.

Hungry for more?

Expert

Technology drives culture

We see DevOps as a lifecycle with each phase flowing into the other to break down silos and inform key stakeholders along the way. You plan the work, then build it, continuously integrate it, deploy it, finally support the end product and provide feedback back into the system.

The tools and technology your teams use can drive better automation and collaboration between teams. We've put together a list of some we use - check it out.

Hungry for more?

Base

Base

Congrats, it looks like you're making the first strides in your DevOps journey!

People and culture first

The first step in moving to DevOps is to pull from agile principles - people first, then process and tools.

Culture is the foundation on which every successful team is built and is a core ingredient of a DevOps implementation. A DevOps culture brings a sense of shared responsibility across teams, yields faster time to market and faster resolution times, and helps mitigate unplanned work.

One small but impactful way to initiate culture change is to run workshops that identify areas of improvement between your dev & ops teams. To help, we've built a DevOps playbook.

Hungry for more?

Beginner

Beginner

Go lean with Agile & Git

In looking at the three ways of DevOps - flow, amplify feedback, and continuous learning and experimentation - each phase flows into the other to break down silos and inform key stakeholders.

To master 'flow' teams need to make work visible across all teams, limit work in progress, and reduce handoffs to start thinking as a system, not a silo. One way to start approaching 'flow' is through practices like agile. Find out more here.

Another way to master 'flow' is by moving to distributed version control systems (DVCS) like Git, which is all about quick iterations, branching and merging - all things you need in a lean DevOps environment. Learn more here.

Hungry for more?

Advanced

Advanced

Amplify feedback for faster resolution

In looking at the three ways of DevOps - flow, amplify feedback, and continuous learning and experimentation - each phase flows into the other to break down silos and inform key stakeholders.

Amplifying feedback can help you catch failures before they make it downstream, and accelerate your time to resolution. One easy way to speed up feedback is by automating notifications so that teams are alerted to incidents or bugs when they happen. See how Atlassian's Site Reliability Engineers do incident management and practice ChatOps for conversation-driven development.

Hungry for more?

Expert

Expert

Technology drives culture

We see DevOps as a lifecycle with each phase flowing into the other to break down silos and inform key stakeholders along the way. You plan the work, then build it, continuously integrate it, deploy it, finally support the end product and provide feedback back into the system.

The tools and technology your teams use can drive better automation and collaboration between teams. We've put together a list of some we use - check it out.