A Maturity Model for Continuous Delivery

The application is built to be fully configurable and easily adaptable, by modifying the data file (js/data/data_radar.js). The default data file contains a sample data set, based on a fictions financial institution’s gap analysis. Using a continuous deliverymaturity model can facilitate discussions on what you want to achieve with CI/CD and will help you map out a step-by-step approach to implementing the various elements. Building up your pipeline incrementally, with achievable goals along the way, makes the process more manageable and provides opportunities to take stock and learn from what you have done so far.

Developers do not have access to production logs. Can recreate builds from source code. Automated unit and integration tests. Avoids products that causes vendor lock-in. Feature toggling to switch on/off functionality in production. Fully automated provisioning and validation of environments. Almost all testing is automated, also for non-functional requirements.

Start now with Clarive Free, Team, Biz or Enterprise editions

Alternately, change the name of data file that gets included, by modifying the build/build.js and js/radar/common.js files. The data file contains a sample data set, based on a fictions financial institution’s gap analysis. Depending on your organization, your end goal may be to have changes deployable within a day . Or your goal may be to achieve continuous deployment, with updates being shipped if they pass all stages of the pipeline successfully. You can also use continuous feedback from production to inform hypothesis-driven development .

continuous delivery maturity model

As a distributed revision control system it is aimed at speed, data integrity, and support for distributed, non-linear workflows. Discover the latest trends, best practices in test automation through our guides, articles, and on-demand webinars. Schedule a demo with one of our specialists and start improving your devops practices. In this blog post, we will be exposing maturity level checklists for different DevOps areas so you have an idea where you at in terms of Continuous Delivery. The suggested tools are the tools we have experience with at Standard Bank. The alternative tools are listed simply as a comparative aid.

DevOps with Clarive

The high priority practices were chosen because they give the most impact in terms of productivity, quality, delivery and risk mitigation. Continuous Delivery presents a compelling vision of builds that are automatically deployed and tested until ready for production. The speed of introducing new functionality – from a client request to delivery. CI/CD allows us to run updates in a matter of days or weeks compared to a whole calendar year with the classic waterfall approach.

Deploying is the core of how you release your application changes. Continuous Delivery and Continuous Deployment capabilities, together, represent the holy grail of modern software engineering. Continuous Delivery and Continuous Deployment are closely related, so I’ll refer to both as CD from now on for simplicity. Continuous Integration is a key enabler of CD. Others want to push the envelope further. The company might desire to transfer everything related to IT systems, including the core level, to CI/CD, DevOps, and Agile at once without having enough experience and knowledge.


Tricentis products help accelerate testing of all your applications, data, and business processes and integrate with tools across your delivery pipeline. GitOps has emerged as a key technology in the cloud native computing space over the last few years. Research into delivery velocity has shown that speeding up software delivery is closely correlated with business success. GitOps is an approach for building incredibly robust and repeatable continuous delivery pipelines. This project now includes a second data file (js/data/iac_radar.js), based on the IaC Maturity Model. To use IaC sample data, rename the file to data_radar.js; it will be automatically included in the build.

  • Perhaps you have a gap in some processes that you are not even aware of.
  • Fast and high-quality results from the application of the technique are possible only after a long and thorough adjustment of the interaction between all the parties involved.
  • The Maturity Model Gap Analysis Tool is applicable to many discipline, not only Continuous Delivery.

Ways you can improve your organization’s performance against DORA metrics to achieve faster and more agile deployments. The application is a browser-based tool, which uses the D3.js JavaScript library. Visualizations are rendered using JavaScript and SVG. You can fully orchestrate tools that are involved in the process and manage your release milestones and stakeholders with Clarive. Testing automatization can be in code, systems, service etc. This will allow the testing each modification made in order to guarantee a good QA.


The idea allows one to run various types of tests at each stage and complete it by launching with the deployment of the system in the actual product that end-users see. Feedback on database performance and deployment for each release. A detailed explanation of what each level of GitOps maturity looks like in practice.

What phases are part of continuous delivery?

  • Stage 1 – Build/Assembly.
  • Stage 2 – Unit Test.
  • Stage 3 – Code Quality Analysis.
  • Stage 4 – Integration Test.
  • Stage 5 – Acceptance/End-to-End Tests.
  • Stage 6 – Store Versioned Binary Artifact.

Article was published on: 10/11/22

Author: Viktor Nikolaev

Victor is a professional crypto investor and stockbroker, specializing in such areas as trading on the stock exchange, cryptov currencies, forex, stocks and bonds. In this blog he shares the secrets of trading, current currency indices, crypt currency rates and tells about the best forex brokers. If you have any questions, you can always contact nikolaev@forexaggregator.com

Leave a Reply