8/8/2019 Pmportal Deployment Guide Template 22Sep10 0606AM 494

http://slidepdf.com/reader/full/pmportal-deployment-guide-template-22sep10-0606am-494 1/3

Deployment Guide Template

To use this template for your project, click on Info in Page Operations and choose "copy" or "export".

View of this template.examples

<System> Deployment Guide Template

Deployment Date: <Date>

Document Date:

Document Identification

AUTHOR:

Name Position Phone E-mail

Revision History:

Date Revision Description

Key Stakeholder Signoff:

Approver Name Title/Unit Signature Date

Document Purpose

This document is intended to provide key stakeholders with a solid understanding of the scope, approach and execution planned for the<System> Deployment. It will provide important facts on the end-user support to be provided during the Pre-Launch, Launch and Post-Launch

phases. In particular, this document includes detailed information regarding the approach, issue tracking and escalation process, projectcommunication, contact and conference call numbers, roles and responsibilities, resource allocation, and scheduling during the Post-DeploymentSupport period. Also included in the document are Contingency plans, Entrance and Exit Criteria for the Post-Deployment Support period.

Objective

The Post-Deployment support objective is to serve as the first tier of support for users going live with the <System> Deployment from <Date>through <Date>. The Post-Deployment Handbook is intended to be the framework through which the Post-Deployment Team works to ensure asmooth transition to the <System> application. It contains materials outlining the issue escalation processes, project communications strategy,and resource allocation.

In Scope: In scope is the Launch and support of the new <System> application into the <Unit, Group, other>. <Fill in anything else that may be inscope on this project>

8/8/2019 Pmportal Deployment Guide Template 22Sep10 0606AM 494

http://slidepdf.com/reader/full/pmportal-deployment-guide-template-22sep10-0606am-494 2/3

Out-of-Scope: <Fill in anything that may be out of scope on this project>

Training/Process Issues

The primary goal of the <support team> is to provide quick resolution to end-users during the time immediately following deployment of newsystem functionality. A critical component to the success of Post-Deployment is the integration with other key support groups during thePost-Launch period. The <Support Team> works closely with business process owners, the deployment team, enhancement contacts and thedata team to ensure that critical end-user issues are resolved in a timely manner.

Training or process issues received by <Responsible Party> will be forwarded back to the end user by <Method>.

Support Roles and Responsibilities Detail

Describe the support that will be available to this product, including support that will be available to this product after hours. The following tabledescribes the roles and responsibilities of the various parties involved in the Post-Deployment process.

 Role  Responsibilities

End-User Identify <System> related issues/errors and report the issues to <Responsible Party> for help

<List other roles and responsibilities>

Post-Deployment Support Criteria

The following criteria must be met prior to the start of the Post-Deployment Period. NOTE that any exceptions to the entrance criteria should benoted and accepted by all key stakeholders (IT and Business).

Criteria Completed

Post-Deployment Handbook has been completed, reviewed and signed-off by key stakeholders Yes No

Post-Deployment Support (and equipment) has been secured Yes No

Support resources have been identified and secured Yes No

Post-Deployment Support review meeting has been held to discuss roles and responsibilities of support resources Yes No

A Go decision has been made by the Business Team and has been communicated to the users Yes No

Systems have been tested and confirmed operationally ready for deployment. Business and Core testing teams andfunctionality signoff has been completed.

Yes No

Communication Plan Template

Issue Management

Contingency Plan

Post-Deployment Support Exit Criteria

The following criteria must be met prior to the end of the Post-Deployment Period. NOTE that any exceptions to the exit criteria should be notedand accepted by all key stakeholders (IT and Business)

Exit Criteria Completed

8/8/2019 Pmportal Deployment Guide Template 22Sep10 0606AM 494

http://slidepdf.com/reader/full/pmportal-deployment-guide-template-22sep10-0606am-494 3/3

By <date> a decision will be made by stakeholders as to the necessity of continuing Post-Deployment Support Yes No

Stakeholders have agreed to the condition of <System> stability and support can be transition to normal production supportoperations (Service Desk)

Yes No

All Very High and High issues pertaining to <System> have been resolved or are being address in a manner agreed uponwith all key stakeholders

Yes No

<System> Post-Deployment Issue Summary documentation is completed and distributed to all key stakeholders Yes No

Service Desk/Integrations Hand-off meeting is held and they agree to officially support <System> Yes No

All reported issues have been placed in the disposition category agreed upon by key Business & IT stakeholders. Anyoutstanding gaps in functionality have been identified, documented, and communicated to the national KM team and trainingorganization via either direct communication or use of existing processes.

Yes No

Production Support/Sustainment teams has assumed responsibility for all deferred/open issues and is ready to resumenormal production processes.

Yes No

Post-Deployment Support Contact List

<System> Email Distribution List:

Name Email Phone Additional Info. Roles/Responsibilities