Fulfill Deployment Stage

Description

The purpose of the value stream stage “Fulfill Deployment” is to execute the Fulfillment Orchestration when the change window for deployment is open. The Fulfillment Orchestration is documented in the change records and can be coded as part of the Product Release to automate the Fulfillment Orchestration.

Table 1. Fulfill Deployment Value Stream Stage

Entrance Criteria:

  • Signed-off preconditions for deployment

  • Validated Knowledge Item for Product Release

Exit Criteria:

  • Actual Product Instance is deployed in production

Value Item:

  • Deployed Actual Product Instance

Activities:

  • Shall create the Desired Product Instance topology from the Product Design

  • Shall reserve the required Resources (e.g., hardware capacity, cloud resources, licenses, …​)

  • Shall create Order(s) to cater for the deployment of any dependent services required

  • May inform support specialists from the Monitoring bridge and the service desk

  • Shall verify the orchestration for the Desired Product Instance and associated Fulfillment Books, and validate if all preconditions are met

  • May suppress monitoring Events to prevent them from being escalated during the change window

  • Shall deploy artifacts from the Build Package as part of the Product Release on the Actual Product Instance(s), and update the topology

  • Shall deploy new or updates to Runbook(s)

  • Shall deploy new or updates to Service Monitor(s)

  • Shall deploy/activate the Knowledge Item(s) as part of the Product Release

  • May start the Actual Product Instance(s)

Examples of Participating Stakeholders:

  • Operations Manager

  • Product Manager

  • Release & Deployment Manager

  • Release & Deployment Manager

Participating Data Objects (Component):