Task: Develop Backout Plan |  |
This task results in a plan to be used by the production support organization to roll back the release if there is a problem during or after deployment.
Disciplines: Deployment
Purpose
The purpose of this task is to develop the criteria, procedures, and responsibilities associated with rolling back a specific release into the production environment to prevent or minimize interruptions to other products or services.
Relationships
Roles | Primary Performer: Developer | Additional Performers: Deployment Engineer
Inputs | Mandatory: None | Optional: Deployment Plan
Outputs | Backout Plan
Main Description
A rollback might be needed for a variety of reasons, including corruption of the production code base, inoperable components, an unplanned undesirable effect of the release on other production systems, an unhappy customer, etc. The Development team should provide the production support organization with a specific plan and decision criteria made available to them to avoid or minimize service interruptions.
Steps
Determine if backout plan exists
Determine whether the development team has a backout plan already written for a previous release. If so, part of that plan%EOL%might be reusable. If this release is the development team%sq%s first, another development team with a similar feature set%EOL%might have a plan that can be used as a starting point.
Develop the backout plan (if applicable)
If a backout plan does not exist, or one cannot be found to be used as a starting point, answer the questions documented in%EOL%the Artifact: Backout Plan to start and develop a backout plan.
Update the backout plan (if applicable)
If a backout plan does exist that can be used as a baseline, review that plan and update, add, or delete information as necessary. When the plan is completed, it should reflect entirely the contents of the upcoming deployment only, not a release in the past or one in the future. In other words, the backout plan should be specific only to this release.
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. EPF Copyright.