Deployment Plan
The
deployment plan is the
deployment work product that
documents an endeavor's plans for deploying all or part of a
completed
application to its
production environments.
The typical objectives of a deployment plan are to document
an endeavors plans for:
- Delivering the final version of all deliverable work
products to the customer organization.
- Deploying the:
- Application to its production environments.
- Hardware components to their production
environments.
- Databases to their hardware components.
- Deploying the remaining software components to their
hardware components.
- Notifying the user organizations regarding the readiness
of the application for use.
The typical benefits of a deployment plan are:
- It decreases the risks associated with the deployment
activity.
The typical contents of a deployment plan are:
The typical stakeholders of a deployment plan are:
- Producers:
- Evaluators:
- Approvers:
- Maintainer:
- Users:
Phases
Preconditions
A deployment plan typically can be started if the following
preconditions hold:
A deployment plan typically has the following inputs:
- Work Products:
- Stakeholders:
Guidelines
- This is a living document that is developed incrementally
and iteratively in parallel with other documents.
A deployment plan is typically constrained by the following
conventions:
-
Content and Format Standard
-
MS Word Template
-
XML DTD
-
Inspection Checklist