KEMBAR78
Level 3 Level 4 Level 5 Level 1 | PDF | Software Testing | Databases
100% found this document useful (1 vote)
221 views2 pages

Level 3 Level 4 Level 5 Level 1

The DevOps maturity model outlines 5 levels of maturity for DevOps practices: 1) Initial - Processes are ad hoc and unpredictable. 2) Defined - Processes are defined but not standardized. 3) Managed - Processes are standardized across projects using modified standard processes. 4) Measured - Process quality and performance are measured for visibility and predictability. 5) Optimized - Continuous process assessment leads to minimal risk and cost achieving objectives.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
221 views2 pages

Level 3 Level 4 Level 5 Level 1

The DevOps maturity model outlines 5 levels of maturity for DevOps practices: 1) Initial - Processes are ad hoc and unpredictable. 2) Defined - Processes are defined but not standardized. 3) Managed - Processes are standardized across projects using modified standard processes. 4) Measured - Process quality and performance are measured for visibility and predictability. 5) Optimized - Continuous process assessment leads to minimal risk and cost achieving objectives.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Devops Maturity Model

(Initial) (Defined) (Managed) (Measured) (Optimized)


Level 1 Level 3 Level 4 Level 5
Level 2
• Software is built • Regular, automated
Build manually. build process • Automated build & test
cycle every time a • Teams regularly meet to
Management & • No Management of • Any build can be re- change is committed. • Build metrics gathered,
made visible & acted on. discuss integration
artifacts and reports created from source problems and resolve
Continuous • No baselines are made control. • Dependencies managed
& integrated. • Build are not left broken. them with automation,
as part of the build • Baselines are kept for faster feedback & better
Integration process key builds. • Re-use of scripts & tools. visibility.

• Manual process to • Automated deployment • All environments


deploy software. to some environments. • Fully automated, self- • Orchestrated
service push-button managed effectively.
Environments & • Environment-specific • Creation of new process for deploying deployments managed.
• Provisioning fully
binaries. environments is cheap. software. • Release and rollback
Deployment • Environment • All configuration processes implemented
automated.
• Same process to deploy & tested. • Virtualization used if
provisioned manually. externalized & to every environment. applicable.
versioned.
• Infrequent, untracked & • Painful & infrequent, but • Change management • Environment and
unreliable releases. reliable releases and approvals processes application health • Operations and delivery
Release • No communication • Limited traceability from • defined and enforced. monitored and
proactively
teams regularly
collaborate to manage
regarding a release. requirements to release
management & • No self- • Minimal self-
• Regulatory and
compliance conditions • managed. risks and reduce cycle
time.
compliance auditing/regulation. auditing/regulation met. • Cycle time monitored.

• Manual testing after • Quality metrics and


deployment. • Automated tests written trends tracked.
as part of story/feature • Automated unit and • Production rollbacks are
• Repeatable test plans acceptance tests. • Non functional rare.
development. requirements defined
Testing not enforced.
• Tests can be triggered by • Testing part of and measured. • Defects found and fixed
• Developers don't write automated build. development process. immediately.
or execute tests. • Testing team is fully
integrated..

• Database changes • Database upgrades and


• Changes to databases rollbacks tested with • Release to release
Data • Data migrations done with automated
performed automatically
as part or deployment every deployment. feedback loop of
unversioned & scripts & versioned with database performance
Management performed manually. application.
process. • Database performance
monitored and
and deployment
process.
optimized.
Devops Maturity Model
• Processes are usually ad hoc and disordered. Outcomes are unpredictable, often exceeding
allocated budget and timelines. During times of crisis, you have a tendency to abandon process
Level 1 - and it is impossible to repeat successes.
Initial

• Processes are defined but not standardized across projects or even across different lifecycle
stages of the same project. The standards, process descriptions and procedures can vary
Level 2 - considerably from team to team.
Defined

• Processes are well characterized and standardized across all projects. Standard processes are
used to establish consistency throughout the organization. Projects establish their specialized
Level 3 - processes by modifying the standard processes to fit their needs and requirements, while still
Managed keeping to the standard frameworks defined by the organization.

• Process quality and performance are measured to achieve visibility and predictability. The
performance of your processes is controlled using statistical and other measurable techniques,
Level 4 - and predictions are based reliable data analytics.
Measured

• You are in the top percentile of DevOps practitioners. Your continuous assessments of the overall
Level 5 - process lead you to achieve your business objectives with minimal risk and cost.
Optimized

You might also like