Deployment Plan Checklist

Location List

List each physical location in order of deployment, and the planned date (or range of dates) for each location.

{e.g.: San Jose: April 17, Brussels: April 24, Research Triangle Park: May 1}

Deployment Steps

List each step in the deployment process. (Use the Network Improvement Process Guide to suggest possible steps.) Use the overall Stages described in the Architecture Plan to separate the steps. Note that some steps may be conditional on the type of location (e.g. steps 1-7 will be repeated for each hub location, and steps 8-14 will be repeated for each remote location). For each step, list (when applicable):

A: Work: What work will be done at what type of location.

B: Responsibility: Who has been assigned to do the work.

C: Tools needed: What hardware, software, and tools (including configuration templates and scripts) they will need to bring to do the work

D: Tools present: What hardware, software, and tools must already be at the location for the step to be successful.

E: Preceding step dependencies: What steps must be successfully completed before this step can occur.

F: Following step dependencies: What steps downstream in the process require this step to be successfully completed.

G: Duration: How long the step will take to complete.

Start and End Dates

{e.g.: Step 1:

A: Work: Order all WAN circuits for Tier 1 (hub) locations.

B: Responsibility: Project Manager (name).

C: Tools needed: Not applicable (N/A)

D: Tools present: N/A

E: Preceding step dependencies: None.

F: Following step dependencies: Steps 4 - 17 require successful WAN circuit installation.

G: Duration: 45 days, according to the vendor.

H: Start Date and End Date: Order April 5, deliver by May 20^th. }

Deployment Templates

A: Hardware, Software: Based on the Architecture Plan, show a diagram or describe the new architecture and connections being supplied to each type of location; list the new software (or software upgrades) that will be loaded onto the new architecture.

B: Configuration, Scripts: Attach copies of the configuration files or scripts which will be loaded at each site type, based on the Architecture Plan.

Contingency (Backout) Plan

If there are problems at the moment of cutover from the old architecture to the new, describe the contingency plan steps in detail (i.e. exactly what steps must be taken to back out the new network elements and re-establish the old architecture as a fully functioning alternative).

Deployment Training

I verify that each person deploying this equipment / software / configuration in the production network has had at least one prior dry run session deploying identical network elements in a lab environment. Yes / No. (If no, then with explanation).

Responsibility

This Deployment Plan will be posted by the Network Improvement manager at http://xxxx/NetImprove/Projects/Project_Name/Deployment_Plan. It will be the responsibility of the project leader to update this Deployment Plan should any changes be made to the actual deployed architecture.