Workflow Detail: Plan Deployment

Description

Deployment planning requires a high degree of customer collaboration and preparation. A successful conclusion to a software project can be severely impacted by factors outside the scope of software development such as the building, hardware infrastructure not being in place, and the staff being ill-prepared for cut-over to the new system.

To ensure successful deployment, and transition to the new system and ways of doing business, the Deployment Plan needs to address not only the deliverable software, but also the development of training material and system support material to ensure that end users can successfully use the delivered software product.

Related Information

This section provides links to additional information related to this workflow detail.

Timing

This work is performed early in each iteration, generally starting late in the Construction phase and continuing through Transition. It can begin as soon as iteration planning is reasonably complete for the iteration.

Optionality

Recommended whenever an executable release will be externally deployed outside the primary development team, either for the purposes of delivering the software to the end user, or for testing purposes.

How to Staff

A deployment manager needs to be someone who is aware of the operational needs of the end user and capable of pulling together all the items that go into making the product. The deployment manager runs the beta test and, in the case of "shrink wrap" products, deals with the manufacturers to ensure that adequate quality is achieved in the product.

The deployment manager "gets the product out there" and, as such, needs to be well versed in the required infrastructure, and user needs, to ensure that the product is available for the users.

Work Guidelines

See the Related Information section for additional guidance that will help you in performing this work.

Rational Unified Process