Artifact: Deployment Plan

	The Deployment Plan describes the set of tasks necessary to install and test the developed product such that it can be effectively transitioned to the user community.
Role:	Deployment Manager
Optionality/Occurrence:	Optional. Started in the Elaboration phase and is refined in the Construction phase.
Templates and Reports:	Template: Deployment Plan
Examples:
UML Representation:	Not applicable.
More Information:	Guideline: Deployment Plan

Purpose Timing Responsibility Tailoring

Input to Activities:  Create Deployment Unit Create Product Artwork Develop Training Materials Manage Acceptance Test Manage Beta Test Provide Access to Download Site Write Release Notes

Output from Activities:  Develop Deployment Plan

Purpose

The purpose of the Deployment Plan is to ensure that the system successfully reaches its users.

The Deployment Plan provides a detailed schedule of events, persons responsible, and event dependencies required to ensure successful cutover to the new system.

Deployment can impose a great deal of change and stress on the customer's employees. Therefore, ensuring a smooth transition is a key factor in satisfying the client. The Deployment Plan should minimize the impact of the cutover on the client's staff, production system, and overall business routine.

Timing

The Deployment Plan is started in the Elaboration phase and is refined in the Construction phase.

Responsibility

The Deployment Manager is responsible for creating and updating the plan.

Tailoring

All systems to be deployed must have a Deployment Plan. If the system is only being built as a prototype or a proof-of-concept, a Deployment Plan may not be necessary.

Rational Unified Process