Intro
Project
Development
Operations
Culture
Infrastructure
Finish
 

Maturity Model
Assessment Tool

Tell us where you are in your DevOps journey so we can help.

In order to refine your organization’s DevOps practices, we need to evaluate your current maturity across five domains. DevOps maturity is a measure of your organization’s ability to properly implement and respond to common software development challenges. Once we know where you stand, we can help you move in the right direction.

Always

Always. This guideline is always followed.

Sometimes

Sometimes. Guideline exists, but it is only partially followed.

Rarely

Rarely. Guideline is defined but rarely followed.

Never

Never. Guideline does not exist for this objective.

Project

The project realm examines your organization's approach to tracking and managing software projects.

Features and defects are tracked and frequently reviewed in a centrally managed tool.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

The project has a defined, active product owner.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

User feedback is collected after each release.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Scope and change requests are tracked and prioritized.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Development

The development realm examines your organization's practices and procedures related to software creation.

A source code management tool is used.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Source code branches map to a specific feature, requirement, or defect.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Source code is continuously integrated into a baseline.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Source code includes automated unit tests where effective.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Source code is peer-reviewed before merging into a baseline.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Operations

The operations realm examines your organization's ability to effectively test and deploy software.

Build process is defined in the codebase.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Builds are centrally managed and controlled.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Build artifacts are versioned and stored.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Environments—including those for development, quality, customers, and production—are separate.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Environments can be easily recreated.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Culture

The culture realm examines how well positioned your organization's culture is to support the spirit of DevOps.

Operations continually works toward making development more productive.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Manual intervention is continually removed (where possible).

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Failure is accepted and understood as a normal byproduct of active software development.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

All team members understand how work packages map to the overall project/system plan.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Infrastructure

The infrastructure realm examines how well your organization's infrastructure and tooling can support DevOps workflows.

Virtual or cloud-based technology is used to create and support environments.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Environments are defined in code and versioned with the codebase.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

The application or system can automatically failover in the case of an outage.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Applications are actively monitored for failures.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

The application or system supports introducing experimental features in production for usability and other testing purposes.

?
icon3 Always.
icon2 Sometimes.
icon1 Rarely.
icon0 Never.

Your Action Plan

Provide your contact information below and we will send you a personalized assessment.

Please send me more helpful information from Base2Solutions.
X
Always

Always. This guideline is always followed.

Sometimes

Sometimes. Guideline exists, but it is only partially followed.

Rarely

Rarely. Guideline is defined but rarely followed.

Never

Never. Guideline does not exist for this objective.