Work Product Descriptor (Artifact): Deployment Plan |
|
 |
The Deployment Plan work product describes the organization, strategy, resources, and methods used to deploy the new application at customer sites. |
|
Purpose
This is the principal document that will guide the management through system deployment. This document provides a
detailed schedule of events, expected project duration, persons responsible, and event dependencies required to ensure
successful cut-over to the new system. Deployment can impose a great deal of change and stress on end users. Therefore,
ensuring a smooth deployment is a key factor in gaining acceptance and high satisfaction of the overall solution.
|
Relationships
Input To | Mandatory:
| Optional:
| External:
|
Description
Main Description |
The Deployment Plan describes the organization, strategy, resources, and methods used to deploy the new application at
customer sites. The plan identifies the responsibilities of everyone participating in the deployment and is written
from the user's perspective. The Deployment Plan also serves as the project's master document over the migration
period. As such, it contains the following elements:
-
The plan validates that the proposed solution actually is ready for deployment. It contains the steps needed to
make sure that the solution hardware, software, and documentation are in place to proceed.
-
The plan verifies that the people are trained and ready to support the new system. This includes the user, support
and temporary deployment communities.
-
The plan verifies that the organization is ready to accept the delivery of the proposed solution.
-
The plan verifies that the proper level of contingency planning has taken place and that the appropriate risk
mitigation procedures are ready.
|
Brief Outline |
The deployment plan consists of textual descriptions of the issues associated with the migration to the new
system. The plan may also include Gantt charts, Program Evaluation and Review Technique (PERT) charts, and
Critical Path Method (CPM) charts, calendars, tables, text descriptions of tasks and status graphs.
|
Properties
Optional |  |
Planned |  |
Key Considerations
The development of the Deployment Plan starts early in the project.
-
Do not wait until the deployment of the system is imminent to beginning the initial drafts of the document.
-
Review the Deployment Plan with the client and all users, including anyone in areas such as systems administration,
database, LAN, and HVAC whose systems or jobs may be involved with the new system.
-
Obtain client sign-off on all the deployment criteria outlined in the Deployment Plan to help ensure
formal stakeholder approval of the new system.
-
If the system is being deployed in multiple releases, the Deployment Plan should relate back to the Release
Plan.
-
Multiple releases imply multiple deployment periods. The issues associated with each period should be considered
when deciding on the content of a specific release.
-
Post-Live support procedures should be in place or well under construction by the time the Deployment and cut-over
plan is actually started.
|
Tailoring
Impact of not having |
The deployment team could cause serious disruption to the business possibly resulting in putting the legacy system back
into production.
|
Licensed Materials - Property of IBM
© Copyright IBM Corp. 1987, 2012. All Rights Reserved.
|
|