About the Release Train Process App

Release trains manage one or more release packages that have a common goal. That goal could be a date, such as a quarterly train; a set of features, such as performance or security improvements; or some other business requirement.

Most release trains are planned around a specific time frame, such as a month or fiscal quarter, but some solve a specific problem, such as improved security or database performance. Each release train item provides easy access to critical data points, such as schedules and milestones, release train status, gate exit criteria, approvals, and release packages.


The primary participants in Release Trains are as follows:


Release trains follow a process organized into these stages, based on the swimlanes in the Release Train workflow:

The exit criteria points, called gates, do not match the swimlanes, which are a variation on the PDCA ( plan-do-check-act). PDCA is an iterative four-step management method used in business for the control and continuous improvement of processes and products. The swimlanes in the Release Train are PDCD (plan-do-check-deploy).

Following are the stages of the release and the specific actions that can be done in those stages.


The Plan stage is the primary planning stage for a release train.


Release trains are sent to development during the Do stage.


In the Check stage, the functionality delivered by the release packages associated with the release train is verified.


In the Deploy stage, the release packages associated with the release train are deployed to final or production environments.

Related Topics

Configuring Release Trains