deployment planning

7/27/2019 Deployment Planning

1/31

Prepared By : Pn. Salwa bint i Abdul K ohar

Pusat Lat ihan Kemahiran E-Access


2/31

Understand What is a Deployment?

Understand What is a Deployment Plan?

Inputs What information needs to be gathered to create a

deployment plan?

Outputs The anticipated outcomes from the deployment plan

include


3/31

is where the release milestone occurs

once the team addresses all outstanding

issues and ships the product or places it in

service

Part of Project Closure


4/31

Construct software components

Verify and test

Convert data

Train users and document the system

Install the system


5/31

The Deployment Plan defines and plan all

of the work steps for complete deployment,

and who does them

The Deployment Plan describes how the

product will be transitioned to the user

community


6/31

Creating a deployment plan is essential to creating and

installing a configuration management environment.

The deployment plan outlines the scope, approach and

execution planned for the deployment of the project

deliverables.

The plan includes:

Information about system support, issue tracking, escalation processes,

roles and responsibilities before, during and after deployment.


7/31

The deployment plan is intended to provide

Client, stakeholders and support personnel with a

smooth transition to the new product or software beingdeployed.

The deployment plan describes each step of

the deployment location, Whether there is one site or multiple sites, or one

deployment or a phased deployment planned.


8/31

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

Contingency information

Training plan


9/31

Release plan

Production Readiness

Communication Plan

Issue/charge Request tracking method

Contingency Plan

Training Plan


10/31

Describe the activities for a phased implementation or rollout.

Track the dates for the release of various function, 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:

Preparation of the environment

Conversion information


11/31

Product installation information

Distribution details

Data migration

Remember:

Implementation dates should never fall on make

no changes dates. Deliverables: Release Plan Template, Detail

Release Plan Example


12/31

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 userin preparing

for this new product.

Deliverables: Production Readiness Checklist


13/31

Develop a plan to communicate with all interested

parties of this project (stakeholders, sponsors,

users, developers)

This planning ensures that everyone who need to

be informed about projects activities and results

gets the needed information in a timely manner.

Deliverable: Communication Plan Template


14/31

Use a tool to record:

Project issues and their associated actions and

owners

Project decisions and reasons

Deliverable: Issue/Action-Decision LogTemplate


15/31

Plan for what to do when something goes

wrong.

Develop a business resumption plan and

comprehensive statement of action.

Deliverables: Contingency Plan Template.


16/31

Outline the training timeline and describe

the approach, activities, and tasks

necessary at each point in the deployment.

Deliverable: Training Plan Template


17/31

Step 1 : Identifying compatibility, conversion and

migration strategies

If the system will replace an existing system,compatibility, conversion, and migration issues

must be addressed. Specifically: Data from an existing system must be carried forward (and

possibly converted in format) for the new system. Existing user interfaces (screen formats, commands, etc) must

be supported in the new system.

All existing application programming interfaces (APIs) must be

maintained


18/31

Step 1 : Identifying compatibility, conversion and

migration strategies (cont)

Migration from the existing system to the new one must notdisrupt end user service for more than a pre-determined amount

of time (varies depending on the business).

The new system must be capable of operating in parallel with the

old system during the migration period.

There must be a capability to fall back to the old system, if

needed, during the first two weeks of operation.

Old archive data may need to be processed on the new system.

If it is cryptographically protected, then the encryption keys will

need special consideration when migrating


19/31

Step 2 : Determining the deployment schedule

Transitioning a system into a production

environment requires planning andpreparation. Technical factors to be considered

include : Users of the system may need to be trained.

The production support environment must be prepared andproduction support staff must be trained and ready to support the

system.

Production support procedures, including backup, recovery, and

problem resolution must be established


20/31


Business factors influencing the deployment

schedule include : There may be specific business objectives which require the system

to be deployed by a specific date; failure to meet this date may

significantly reduce the value of the system.

There may be time periods during which deployment of the system isimpossible due to business or operating conditions, including but not

limited to ends of financial reporting periods or periods during which

the system cannot be shut down


21/31


Some systems can never be shut down (example :

network and telephony switches)These systems may require new versions of the

system to be deployed while the previous version is

still running.

Upgrading a high-availability system usuallyrequires special architectural considerations


22/31

Step 3: Determining the deployment sequence

Some systems must be deployed incrementally, in

parts, due to timing or availability issues.

If the system cannot be deployed all at once, the

order in which components must be installed, and

the nodes on which they are installed, must bedetermined.


23/31


Common deployment scheduling patterns include:

Geographically - by area Functionally - by application

Organizationally - by department or job function


24/31


When an application is deployed over a period of

time, issues which need to be resolved include: The software must be able to run in a partial configuration

Different versions of the software must be capable of coexisting

It must be possible to revert back to a prior version of the system

in the event that problems with the new system are detected


25/31

Step 4: Determining user training needs

For each category of user, including

administration, operators, and end users, identify: What types of IT systems they use at the present. If this system will

bring the first use of IT to any users, either within or external to the

organization, flag this as a special requirement that will merit

special attention.

What new functions will be brought to them by this system. In broad terms, what their training needs will be.


26/31

The deployment planning begins in the

design phase and continues throughout

the project lifecycle.


27/31

The deployment plan is typically drafted by

the Project Manager, but its development

is a team effort.


28/31

The solution life cycle shown in the

following figure depicts the steps in the

planning, design, and implementation of

system solution.

The life cycle is a useful tool for keeping a

deployment project on track.


29/31

Business Analysis

Business requirements

Business constraints

Technical Requirements

Use-case analysis

Usage analysis

Quality of services requirements

Logical Design

Logical architecture

Deployment scenario

Deployment Design

Deployment architectureImplementation specifications

Implementation plans

Deployment Implementation

Hardware setup

Installation, upgrade, and migration

Configuration and customization

Development and integrationPrototypes and pilots

Production rollout

Operations

Monitoring

Maintenance

Performance tuningSystem enhancements and upgrade


30/31

Three primary issues to consider that

come into play before or after the

Deployment Phase of a system

development project are listed below :

Lack of Defined Scope of Work

Pricing Billing


31/31

THANK YOU FOR YOUR ATTENTION

deployment planning

Documents