Deployment Plan Template (This is a simple task list)
System Deployment Guide Template (This is a detailed template that encompasses all of the outputs listed below)
What is a Deployment Plan?
The deployment plan outlines the scope, approach and execution planned for the deployment of the project deliverables. The plan includes, where relevant, information about system support, issue tracking, escalation processes, roles and responsibilities before, during, and after deployment. The deployment plan is intended to provide clients, stakeholders and support personnel with a smooth transition to the new product or software being deployed. The deployment plan describes each step of the deployment process at each deployment location, whether there is one site or multiple sites, or one deployment or a phased deployment planned. The Deployment Plan defines all of the work steps for complete deployment, and who does them.
What information needs to be gathered to create a deployment plan?
- Deployment goals and critical success factors
- Roles and responsibilities of the parties involved in the deployment of the project deliverables
- Task and resource dependencies
- How team members will communicate
- How to track issues and resolve them
- Backout options
- Training plan
- BC/DR Requirements
The anticipated outcomes from the deployment plan include, but are not limited to, or may not always include:
Samples or Templates
Describe the activities for a phased implementation or rollout. Track the dates for the release of various functions, and/or track the formal review points in the testing cycle of your product. Your release plan may also include the following activities, as appropriate:
Create a Product Implementation Task List. Describe what preparation is required for this new tool or application to operate. Specify any features that need modification to adapt to the new product. Identify the steps necessary to assist the user in preparing for this new product.
Develop a plan to communicate with all interested parties of this project (stakeholders, sponsors, users, developers, Change Review Board) This planning ensures that everyone who needs to be informed about project activities and results gets the needed information in a timely manner.
Use a tool to record:
Plan for what to do when something goes wrong during deployment, including how to go back to prior business processes and applications. Engage the appropriate sections of the Communications Plan.
Outline the training timeline and describe the approach, activities and tasks necessary at each point in the deployment.
|BC/DR Plan||Plan for what to do when something goes wrong. Develop a business resumption plan and comprehensive statement of action.|
Follow these guidelines for compiling the information to be included in the deployment plan:
- Identify the resources required to support this product, including facilities, hardware, software, associated documentation, staff, etc.
- Describe any procedures or lessons learned that may help with the support.
- Describe any expected areas of change to the product.
- Describe the plans for transitioning the product to the support organization. Include:
- Roles and responsiblities for each activity
- Resources needed to carry out the transition activities and where those resources will come from
- Schedule and milestones for conducting the transition
- Installation procedures and other information necessary to support
When is the deployment plan written?
The Deployment planning begins in the design phase and continues throughout the project lifecycle.
Who owns the deployment plan?
The deployment plan is typically drafted by the Project Manager, but its development is a team effort.