Patterns

Patterns in XL Release is like a template but for Delivery.

What is Deliveries?

Deliveries are flows of stages that a set of tracked items must go through. These can be designed as reusable patterns, and can prevent releases from going forward until the tracked items they contain are completed. This allows you to synchronize multiple sub-releases into a larger release cycle.

What is Delivery Patterns in XL Release?

Delivery Patterns are a more comprehensive way to manage multiple releases together

The Delivery Patterns feature in Release allows you to use deliveries and tracked items to synchronize multiple releases together. This allows you to design delivery patterns that conform to the release standards being used by your organization, such as SAFe.

With Delivery Patterns, you can:

Model your deliveries in patterns that represent your organization’s strategy for application development, testing, and deployment to production or any other environment

• Define the items of work that you want to track through the delivery process, no matter how many release processes support those items through their lifecycle
• Create delivery stages and transition points that synchronize the status of tracked items across release pipelines
• Establish and enforce a delivery schedule while allowing individual teams to work at their own pace
• Descope items from a delivery with full visibility and transparency for all stakeholders

How Delivery Patterns works?

The Delivery Patterns feature in Release uses Deliveries to link multiple releases together. Deliveries are designed patterns that define a flow of stages that a set of tracked items must go through. These tracked items are linked to tasks in a set of releases, and allow you to orchestrate the progress of each release so that they can be delivered together as part of a larger feature release.

Deliveries consist of stages and transitions.

• Stages contain tracked items, which are either completed from the releases, or can be manually completed in the Delivery screen.
• Transitions are manual stages that need to be completed before the delivery can move to the next phase. For example, an approval stage will often need to be inserted between building and testing, and marked complete by the relevant approvers.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.