Site icon Doron Katz

How Progressive Delivery can Enhance your CI/CD Pipeline

In a modern and evolved organization you would ideally find teams leveraging Continuous Integration and Continuous Delivery (CI/CD) pipelines. CICD enabled faster and more reliable delivery of software to customers by automating the build, test, and deployment processes. Ideally allowing your customers to receive releases in a predictive manner, the outcome of your team sprints, ultimately reducing risk compared to conducting those steps manually. But releasing your features to all users at once, such as unexpected bugs, compatibility issues, or negative user feedback.

That’s where progressive delivery comes in. Progressive delivery is an approach that extends CI/CD with feature flags, gradual rollouts, and observability. It allows developers to release new features or changes to a subset of users first, and then monitor and evaluate their impact before rolling them out to the rest of the user base. This way, developers can reduce the risk of deploying faulty or unwanted features, and gain valuable insights from real user behavior and feedback.

This article explores how progressive delivery can enhance your CI/CD pipeline, and what are some of the tools and patterns that can help you implement it.

What are the benefits of progressive delivery?

Progressive delivery offers several benefits for software development teams, such as:

What are the tools and patterns for progressive delivery?

There are many tools and patterns that can help you implement progressive delivery in your CI/CD pipeline, such as:

Getting started with progressive delivery

Below are suggested steps you can follow to get started with progressive delivery:


In agile, customer value is God, and you validate and iterate by releasing to segments of your customer base, as part of continuous experimentation in a continuous delivery man we.

Progressive delivery is a powerful approach that can enhance your CI/CD pipeline, and help you deliver software that is not only fast and reliable, but also user-centric and value-driven. By using tools and patterns such as feature flags, canary releases, and observability, you can reduce the risk and uncertainty of software releases, and increase the confidence and satisfaction of both developers and users.

Exit mobile version