Release on Demand is the final element of the Continuous Delivery Pipeline. It is the method through which features deployed into production are released incrementally or immediately to Customers as PER market demand. It is the last element in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD) and Release on Demand, as can be seen in Figure. 

Continuous delivery is deploying software product incrementally with new features as continuously and frequently as needed. It consists of PROCESSES and workflows that reduce cost and improve speed, quality and reliability of the software product.

The course of Continuous Delivery is started by the consent of an EPIC. The stakeholders track the progress by using the Program Kanban Board where progress of features can be tracked from team level to business level.

Once the consent is made, the Epic goes through four stages of Continuous Delivery. 

• Continuous Exploration – The Product Management does the exploration on the epic to get its maximum benefits. This exploration is done amongst customers, key stakeholders, agile teams, business owners. Once the value is obtained, it is broken down into its artifacts. The Program Backlog is made.
• Continuous Integration – The features from the backlog are taken and then executed. They are developed, TESTED, integrated, and validated. 
• Continuous Deployment – Once the features are made, they are deployed. Automated Testing of features and non-functional requirements is done.
• Release on Demand – The software is ready to be deployed on demand. They are released as soon as they BECOME available and whenever it is needed.