Blog URL: http://www.steerlean.com/single-post/2016/11/03/Product-Awesomeness-through-Continuous-Delivery
In the rapid evolving times of today, organizations face a new challenge to stay ahead of competition. The challenge is the ability to swiftly adapt to the changing market and business conditions – to keep up with the competition, market potential, technological enhances, etc. This leads the organizations to the desperate need of a mechanism that enables them to not only release new features rapidly, but also gives them the ability to react to the changing business and market scenarios. The only thing that holds them back from achieving this is the ultimate requirement of stability of the existing systems in production. This ask by the organizations to increase throughout, innovation and stability at the same time, makes them aspire for Continuous Delivery (CD).
What makes us think so and how does that fit in Agile paradigm?
By Agile Manifesto - Does that mean - incremental product development with iterative development, but at the end of each iteration are we ready to ship?
By Lean - How frequent is fast enough? as much as it can that is with each push/commit?
After every change, you can get instant automated feedback on the production-readiness of the system.
Ability to deploy any version of software to any environment.
1. A deployment pipeline models and visualizes your process for getting software from version control into the
hands of your users.
2. It implements and automates that process for each stage that every change to your software goes through,
from check-in to release. which may also contain a few manual stages such as approvals.
3. Assists collaboration between product roadmaps, simplifying program management.
4. With dependencies between pipelines, it is possible to model the dependencies between different software
products or components. As a consequence, it is possible to monitor in real time the status of complex changes
that involve or affect multiple products and components.
5. When you do not need APPROVAL to move to production, it becomes Continuous Deployment.
When there is pressure to innovate.
When there is need to rapidly adapt to the evolving domain and market.
When there is uncertainty from the users, partners and suppliers.
In case of safety-critical systems.
In case of uninterrupted critical services.