Directions for using
template:
Read the Guidance
(Arial blue font in brackets) to understand the
information that should be placed in each section of this template. Then delete
the Guidance and replace the placeholder within <<Begin text here>>
with your response. There may be additional Guidance in the Appendix of some
documents, which should also be deleted once it has been used.
Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size:
You may elect to indent sections for readability.
|
Author |
|
|
Author Position |
|
|
Date |
|
Ó 2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Microsoft
and Visual Basic are either registered trademarks or trademarks of Microsoft in
the
Change Record
|
Date |
Author |
Version |
Change Reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Version Approved |
Position |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
|
|
Document Properties
|
Item |
Details |
|
Document Title |
Deployment Plan |
|
Author |
|
|
Creation Date |
|
|
Last Updated |
|
Cross-over from Existing System
Verify that Solution Works for Users
Monitor for Defects While on Site
[Introduction to the
Template
Description:
The
Deployment Plan describes the factors necessary for a smooth deployment and
transition to ongoing operations. It encompasses the processes of preparing,
installing, training, stabilizing, and transferring the solution to operations.
This includes details about installation scenarios (i.e., at remote or branch
offices), monitoring for stability, and verifying the soundness of the new
solution(s).
Justification: This plan is the how-to
guide to implement the solution into production. This plan provides detailed
deployment guidelines and will help drive the solution’s deployment phase. Deployment is the beginning of the
realization of business value for a given solution. A detailed and verified
deployment plan will accelerate value realization for both the customer and the
project team.]
{Team
Role Primary: Release Management
is responsible for designing and implementing the solution's deployment.
They are responsible for the solution infrastructure and ensuring that it
continues to run smoothly after it is deployed.
Team
Role Secondary:
Development verifies that the plan
will meet the solution requirements. Program Management verifies that the
plan satisfies the solution vision and scope.}]
[Description:
Provide an overall summary of the contents of this
document.
Justification:
Some
readers may need to know only the highlights of the plan, and summarizing
creates that user view. It also enables the full reader to know the essence of
the document before they examine the details.]
<<Begin text here>>
[Description:
The Objectives section defines the primary drivers that were used to create the
deployment approach and the key objectives of that approach.
Justification:
Identifying
the drivers and deployment objectives signals to the customer that Microsoft has
carefully considered the situation and created an appropriate deployment
approach.]
<<Begin text here>>
[Description:
The Development Scope section describes the solution architecture and deployment
size.
Justification:
These characteristics and metrics will indicate the level of effort and
complexity of the deployment.]
[Description:
The Seats section describes the magnitude of the deployment in terms of sites,
seats, countries, and other relevant size factors.]
<<Begin text here>>
[Description:
The Components section lists and describes the components to be deployed and any
critical dependencies among them.]
<<Begin text here>>
[Description:
The Architecture section describes the solution’s architecture and how it might
affect deployment – e.g. centralized servers, hub and spoke, and
parallel.]
<<Begin text here>>
[Description:
The Deployment Schedule section identifies the deployment’s critical dates and
anticipated schedule. This information should be granular as appropriate for the
project.]
<<Begin text here>>
[Description:
The Installation section defines how the overall deployment will
occur:
Based
on the strategy, describe the roadmap for deploying to target
sites.]
<<Begin text here>>
[Description:
The Deployment Resources section identifies the staffing that will be needed to
complete the deployment and the sources of the personnel (internal staff,
contractors, etc).]
<<Begin text here>>
[Description:
The Solution Support section describes how the users are supported during the
deployment. This should be consistent with the Support Plan that describes how
support will occur during operations.]
[Description:
The Help Desk section describes the
support provided to users and applications by the Help Desk organization. This
should include first-level support for direct user questions and application
issues, as well as in-depth support for new or difficult
issues.]
<<Begin text here>>
[Description:
The Desktop section describes any changes in current desktop application support
that may be required during deployment.]
<<Begin text here>>
[Description:
The Servers section describes any changes in current server support that may be
required during deployment.]
<<Begin text here>>
[Description:
The Telecommunications section describes any changes in current telecom support
that may be required during deployment.]
<<Begin text here>>
[Description:
The Coordination of Training section describes how end-user and support staff
training is coordinated with the deployment schedule. The training may occur
just-in-time, before, just after, as needed, or on a pre-scheduled
basis.]
<<Begin text here>>
[Description:
The Site Installation Process section describes the four phases of site
installation: preparing, installing, training, and
stabilizing.]
[Description:
The Preparing section describes how the physical site is prepared for
deployment. This should include the following tasks:
[Description:
The Validation section describes how site information is validated. This may be
by reviewing a preliminary site survey, a phone interview with local site
manager or IT staff member, by audit, etc.]
<<Begin text here>>
[Description:
The Scheduling section describes how sites are scheduled. This may include lead
times, site contacts, hours required, begin and end dates, and expected
duration. It should also address any anticipated loss of function or
interruption to local site services or business.]
<<Begin text here>>
[Description:
The Review Procedures section describes the process for reviewing the accuracy
of procedures for users and operations/installation staff based on the site
validation information. This should include an accuracy check on different
users, target platforms, help desk support, operational policies (logins,
passwords), and review checklists and procedures.]
<<Begin text here>>
[Description:
The Notify Site section describes the communication plan for the scheduling and
transfer of software, hardware, installation prerequisites, and other solution
components. Communication methods may include conference calls, video
teleconferences, netshows, etc. This section should identify the key
communication items and how they will be delivered.]
<<Begin text here>>
[Description:
The Installing section describes the installation processes that will take place
on the site.]
[Description:
The Install Hardware and Software section describes the key tasks required for
installing the solution. Reference any specific installation scripts or
checklists that the technical team will use or include a summary of their
detailed activity. You may place the checklist in the
Appendix.]
<<Begin text here>>
[Description:
The Cross-over from Existing System section describes how solution users will
migrate from the existing software environment. This may include items such as
timing (first of month, Monday, Friday) and moving local data (mail messages,
use of utilities, logon scripts). You may also reference the Migration Plan,
which defines migration strategies and stages.]
<<Begin text here>>
[Description:
The Verify that Solution Works for Users section describes how the solution is
verified to be functional. This could include processes such as walk-throughs of
test scripts by installation technicians or running a diagnostics utility to
verify connectivity or dialup. If a checklist is developed, place it in the
Appendix.]
<<Begin text here>>
[Description:
The Activate Use by Users section describes how users will activate their
initial use of the application (i.e., clicking on a special desktop icon,
started by the trainer, etc.).]
<<Begin text here>>
[Description:
The Training section describes the training activities at the installation site
for end-users and local support staff.]
[Description:
The End-user Training section summarizes how end-users are trained to use the
solution. You may reference the End-user Support Plan for more detailed
information.]
<<Begin text here>>
[Description:
The Support Staff Training section summarizes how site and support staff is
trained to use and maintain the solution. You may reference the Support Plan for
more detailed information.]
<<Begin text here>>
[Description:
The
Stabilizing section describes the activities over the
period of time during which the site activity is monitored for proper use and
any problems brought to attention of the installation technology team and
trainers prior to leaving the site.]
[Description:
The Monitor for Defects While on Site section describes the on-site support for
defect reporting and fixes. This should include the duration of the support, who
will provide it, how issues or defects are recorded and fixed, and how this
information is incorporated into the solution’s overall quality
reporting.]
<<Begin text here>>
[Description:
The Sign-off by Site section describes the site sign off criteria and process.
It should include the specific acceptance criteria and who must be involved in
the sign off process.]
<<Begin text here>>
[Description:
The Survey for Satisfaction section describes the survey that will be
distributed to assess site satisfaction of the installation process. This
information should include a description of the survey process and how the
survey results will be assessed.]
<<Begin text here>>
[Description:
The Transfer to Operations section describes the process (prior to
production but after site installation and training) by which all
responsibilities will be transferred from the solution teams to operations and
support groups. Sub-sections are listed below; use those applicable and add if
required.]
[Description:
The Responsibilities section describes how the support responsibilities are
partitioned between the local site and the central IT support and help desk
groups.]
<<Begin text here>>
[Description:
The Activation of Reporting and Monitoring section describes the reporting and
monitoring procedures for looking at use patterns, incidents, component
performance etc. The Monitoring Plan may be referenced here, which provides
additional details.]
<<Begin text here>>
[Description:
The Logbooks section describes the logbook format and how data is tracked to
monitor operations and incidents. The Monitoring Plan may be referenced here,
which provides additional details.]
<<Begin text here>>
[Description:
The Help Desk section describes how the Help Desk will be brought “on line” to
support the solution. Details of Help Desk support can be found in the Support
Plan.]
<<Begin text here>>