Planning a rollout

Edit online

During the Plan Rollout phase of a release, you create a series of tasks that represent each of the unique rollouts that are to be accomplished for the release. For example, a release might involve two source configuration items (CIs) to 20 target CIs across three sites. Each individual rollout must be defined as a task in the release work plan.

About this task

When you create the tasks in a planned rollout, each task is an implementation task. Implementation tasks affect CIs, and planned rollouts by definition affect CIs. All current and upcoming implementation tasks that are scheduled in your data center are displayed in the Change Implementation Schedule. The Change Implementation Schedule calendar can be used to identify potential conflicts and the dates that are most appropriate for scheduling an implementation task.

For each rollout task that you create, you specify a software image CI reference and bring this reference to the release as a source for the deployment. Not only does this capture CI data for auditing purposes, but it also captures the data necessary for performing the task. A separate deployment ID is subsequently created for each of the rollout tasks in the plan.

The tasks that are part of a Plan Rollout activity typically include the following:

  • Developing site rollout plans. The task owner creates the plans for rolling out the release to each site to which the release will be deployed. Plans include release dates and deliverables. While completing this task, you can refer to related RFCs, problems, and known errors that are addressed in the release.
  • Scheduling asset delivery. If new assets are deployed as part of the release, the delivery of those assets is planned. All assets should be received at a central internal location prior to delivery to the site.
  • Scheduling the release implementation. The deployment of the release is scheduled for each site.j
  • Coordinating with communication and training. In this task, you determine when training related to the release will be provided to the affected sites. In addition, necessary communications to the sites are scheduled.