| Full title | Define a procedure for deploying changes to running services |
|---|
| Objective | Define a non-intrusive procedure for deploying the changes, so that their implementation does not interfere with the running services |
|---|
| Applicability | This practice concerns mostly the maintenance phase of software development. |
|---|
| Context | The practice applies to all projects that are intensively changed and used. |
|---|
| Addressed elements in SMM | 5.4. Implementation of modifications |
|---|
| Actions | - Identify services that could be affected by the subject change
- Define a deployment procedure that minimizes the impact on other services
- Consult the procedure with owners of affected services.
- Prepare and verify rollback routines (at least for the core parts of the deployment procedure) that allow for reversing the deployment in a safe way
- Define the deployment schedule in collaboration with the owners of affected services
- Make a simulated deployment for the change, if necessary
- Involve the owners of the affected services
- Monitor the simulation and make notes concerning the observed deviations from the procedure
- Update the procedure, if needed
|
|---|
| Risks | - The change is not announced early enough
- Other services could be negatively affected by the change
- There are implicit dependencies between other services that could negatively affect the deployment
- The procedure is incomplete or unfeasible
- Some risk factors could materialize and negatively affect the deployment
|
|---|
| Related practices | BP-E.3: Identify and evaluate available options for implementing Implement a change request process |
|---|
