02 — Capability · BC-720.50
Release & Deployment
Move tested changes into production environments on purpose, in a known order, with a way back if the result is not what was expected.
- Deployment Management
- Release Engineering
- Environment Management
In scope
- Environment provisioning and promotion path
- Release packaging and scheduling
- Deployment automation and rollback
- Post-deployment verification
Out of scope
- Change approval and the change calendar (see BC-740)
- Continuous delivery for a software product business (see BC-1220)
Decomposes into · 4
- BC-720.50.10Environment ManagementProvide and refresh the development, test and staging environments changes pass through, and keep them close enough to production to mean something.
- BC-720.50.20Release PlanningBundle changes into releases, sequence them against dependencies and the business calendar, and communicate what is coming.
- BC-720.50.30Deployment AutomationScript the path to production so deployments are repeatable, logged and reversible rather than performed by hand from memory.
- BC-720.50.40Deployment VerificationConfirm after each deployment that the application works, the data is intact and the users can tell no difference except the one intended.