Release trains are a collection of application releases. 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, application release status, stage gate criteria, approvals, and turnovers.
At each stage, release participants and stakeholders can view the status of each release train.
At various points during the process, a release manager can:
- Add application releases.
- "Fast track" the release train to move it straight to the Verification stage.
- Update the release train status (green, amber, or red).
- Change the release schedule for stages that have not been completed. If stage gate completion dates are changed, due dates for exit criteria can be automatically changed as well.
- Create turnovers once a train has passed the Scheduling and Scoping stage.
- Copy the release train.
- Cancel the release train.
Schedule and Scope
The Schedule and Scope stage is the primary planning stage for a release train.
- Release manager
- Approval board
A release manager does the following during this stage:
- Enters the release train name and purpose.
- Selects the primary release manager.
- Selects the release type for the release train.
- Enters start and end dates for the release train.
- Enters end dates for each of the release train stages.
- Adds application releases to the release train and requests that application releases be added to it.
- Sets train approval requirements.
- Adds exit criteria to each stage gate.
Once these activities are completed, the release manager sends the train to the construction stage. The release train cannot proceed if scoping exit criteria is not met, however.
Construction
Release trains are sent to development during the construction stage.
- Release Manager
- Approval board
In this stage, all application releases are typically under development. Most of the work during this stage is managed through the Application Releases process app.
When development is complete for all application releases on a train, the train is sent to the release manager for development approval. If construction exit criteria has not been met or if the release manager rejects the train, it is returned to the product owner.
After approval, the train progresses to the verification stage.
Verification
In the Verification stage, the functionality delivered by the application releases associated with the release train is verified.
- Release Manager
- Approval board
During verification, the release manager verifies that the QA exit criteria has been met, and then sends the release train for executive approval.
After executive approval, the train is deployed to production.
Deployment
In the Deployment stage, the turnovers associated with the release train and its application releases are deployed to final or production environments.
- Release Manager
- Release Engineers
During this final stage, the release manager or a release engineer determines that the train is ready for deployment and deploys the train.
Once deployment successfully completes, the train is closed by the release manager or release engineer.