Project Implementation Plan - Download as DOC by Project-Documents

VIEWS: 85 PAGES: 28

The Implementation Plan defines the Project’s strategy for moving from the old environment to the new, or the As-Is to the To-Be.

For example, if the project involves implementing a new IT system, the plan will illustrate how it will be done. It should include information about: key dates / schedule; dependencies and pre-requisites; roles & responsibilities; implementation approach and considerations; dress rehearsals; testing approaches; change management & communications; contingencies and fall-back; post go-live…etc

More Info
									Insert Company Logo




Insert Project Title

Implementation Plan




Document Status

Version Number:       1.0
Date:                 insert date
Status:               Draft




                                    Page 1 of 28
Insert Company Logo



Preface

For more information on this document, contact:

Insert name

Insert “Job Title”
Insert “Project Name”
Insert Telephone number
Insert e-mail address

Document Location

Insert document location / file path

Document Revision History

   Date       Version            Author           Comments




                                                             Page 2 of 28
Insert Company Logo



Document Approval

Insert Name            Insert Job Title


Signature              Date



Insert Name            Insert Job Title


Signature              Date



Insert Name            Insert Job Title


Signature              Date



Insert Name            Insert Job Title


Signature              Date



Document Endorsement

Insert Name            Insert Job Title


Signature              Date



Insert Name            Insert Job Title


Signature              Date




                                          Page 3 of 28
Insert Company Logo


Document Review

The following people have been consulted in the compilation of this document:

 Business Area          Name                                    Role
Insert name of   Insert Name          Insert Job title / role
Business Area




                                                                                Page 4 of 28
Insert Company Logo



Contents

1         INTRODUCTION ................................................................................................... 7
    1.1   Purpose of this document ................................................................................................................. 7
    1.2   Intended Audience ............................................................................................................................ 7
    1.3   Approach ........................................................................................................................................... 7
    1.4   Document Scope .............................................................................................................................. 7
    1.5   Definitions ......................................................................................................................................... 8
    1.6   References ........................................................................................................................................ 8
2         KEY DATES .......................................................................................................... 9
3         DEPENDENCIES & PRE-REQUISITES ............................................................. 10
4         ROLES & RESPONSIBILITIES .......................................................................... 11
    4.1   Deployment Manager ...................................................................................................................... 11
    4.2   Steering Committee ........................................................................................................................ 11
    4.3   Project Director ............................................................................................................................... 11
    4.4   <Vendor> System Lead .................................................................................................................. 11
    4.5   Business Leader(s) ......................................................................................................................... 11
    4.6   Power Users/Testers ...................................................................................................................... 12
    4.7   Technology Stream Manager.......................................................................................................... 12
    4.8   Application Delivery Team .............................................................................................................. 12
    4.9   Legacy Systems Conversion Developer ......................................................................................... 12
5         IMPLEMENTATION APPROACH & CONSIDERATIONS .................................. 13
6         DRESS REHEARSALS ...................................................................................... 14
    6.1   Objectives ....................................................................................................................................... 14
    6.2   Scope .............................................................................................................................................. 14
    6.3   Timeframes ..................................................................................................................................... 14
    6.4   Roles & Responsibilities ................................................................................................................. 14
7         TESTING APPROACH ....................................................................................... 15
    7.1   Scope .............................................................................................................................................. 15
    7.2   Data Validation ................................................................................................................................ 15
    7.3   Data Reconciliations ....................................................................................................................... 15
    7.4   Conversion Record Count / Control Totals ..................................................................................... 15
    7.5   New System Integrity Reports ........................................................................................................ 15
    7.6   Functional Testing ........................................................................................................................... 16
    7.7   Environmental Testing .................................................................................................................... 16
                            rd
    7.8   Interfaces & 3 Party Testing ......................................................................................................... 16
    7.9   Go/No-Go Checklist and Go-Live Sign-Off ..................................................................................... 16
8         CONTROL ROOM .............................................................................................. 17
    8.1   Objective ......................................................................................................................................... 17
    8.2   Scope .............................................................................................................................................. 17
    8.3   Timeframes ..................................................................................................................................... 17
9         PLATFORM REQUIREMENTS .......................................................................... 18
    9.1   Summary ......................................................................................................................................... 18
    9.2   Timeframes ..................................................................................................................................... 18
10        FACILITIES & OTHER REQUIREMENTS .......................................................... 19
11        COMMUNICATIONS........................................................................................... 20
12        CHANGE MANAGEMENT & INCIDENT MANAGEMENT ................................. 21



                                                                                                                                            Page 5 of 28
Insert Company Logo


13      KEY PERFORMANCE INDICATORS (KPI’S) .................................................... 22
14      FALL BACK / CONTINGENCY .......................................................................... 23
15      POST GO-LIVE ACTIVITIES .............................................................................. 24
16      ARCHIVING, DISABLEMENT & DECOMMISSIONING ..................................... 25
17      RISKS & ISSUES................................................................................................ 26
18      APPENDICES ..................................................................................................... 27
 18.1   Detailed Implementation Schedule ................................................................................................. 27
 18.2   Support Schedule ........................................................................................................................... 28




                                                                                                                                   Page 6 of 28
Insert Company Logo



1 Introduction

1.1     Purpose of this document
The purpose of this document is to define and gain agreement to the Implementation Strategy for the xxx Project. It is
based upon a typical ICT implementation project.
This Implementation Plan is intended to be combined with a number of subsidiary planning documents supporting it.
Together these documents represent the full Implementation planning document suite. The Implementation planning
document suite comprises of the documents listed in the table below:
To delete this guidance text box, double click mouse in the left margin then press delete.



                                 Document                                                        Due
Implementation Strategy
Dress Rehearsal scope
Control Room approach
Roll back/contingency plan
Go/No-go Scorecard
Detailed Implementation schedule (preview contained in Appendix 1)
The structure of the Implementation involves a sequence of interrelated activities that
enable the start-up of the new application and closedown of legacy systems.
The Implementation consists of an orchestrated conversion/load/configuration sequence,
preceded by (at least one) dress rehearsal depending on the complexity of the Implementation
and business operations impacted. The dress rehearsal is a full run-through of the final
Implementation sequence, run sufficiently ahead of Implementation to resolve any issues that
arise and plan activities around areas previously missed.


1.2     Intended Audience
In this section describe whom this document has been written for. Often this consists of both a primary audience, and a
group of other stakeholders whom it may be of interest to but is not vital that they read in detail.
To delete this guidance text box, double click mouse in the left margin then press delete.


1.3     Approach
In this section describe the steps taken in developing this document. Describe any investigations carried out, research
methodology used and consultation carried out to date.
To delete this guidance text box, double click mouse in the left margin then press delete.


1.4     Document Scope

1.4.1 In Scope

This defines exactly what this document will cover and where the boundaries lie. List all items that are included in the
scope.
To delete this guidance text box, double click mouse in the left margin then press delete.




                                                                                                           Page 7 of 28
Insert Company Logo


1.4.2 Out of Scope

List identified items that will not be covered in this document.
To delete this guidance text box, double click mouse in the left margin then press delete.


1.5     Definitions
In the table below define any terms which this document’s audience may not understand, including specific terms,
abbreviations and acronyms.
To delete this guidance text box, double click mouse in the left margin then press delete.




      Term / Acronym                                                 Definition




1.6     References
This item lists any documents to which this document refers including any previous investigations carried out. Include all
previous documents prepared as part of this project.
To delete this guidance text box, double click mouse in the left margin then press delete.

This document has used the following documents as points of reference:

[1]    Insert reference to other documents / sources of information

[2]    Insert reference to other documents / sources of information

[3]    Insert reference to other documents / sources of information

Etc…




                                                                                                          Page 8 of 28
Insert Company Logo



2 Key Dates

                  Milestone/Activity    Date   Owner

Production environment in place

Dress Rehearsal <xxx>
- Preparation
- Execution

Training completed

Implementation activities/preparation

Data conversion

Conversion validation

Setup Activities – New Environment

Go/No-go checkpoints and signoff

Go live

Post go-live activities

Legacy systems decommissioned: <xxx>




                                                  Page 9 of 28
Insert Company Logo



3 Dependencies & Pre-requisites
The following lists the key dependencies and pre-requisites for the Implementation.
Refer to the xxx Project Consolidated Project Plan for further details.
•         New System integrity check and reports scoped, developed and tested
•         Conversion software complete
•         Conversion preparation (mapping, scope validation/reconciliation)
•         Integration testing completed and signed off
•         Communications Plan in place
•         Training completed
•         Business processes identified, defined or modified where necessary, and rolled out (in parallel with training)
•         Business cut offs determined and planned
•         Hardware/platform/communications in place and stable
•         Software freeze in place prior to Implementation
•         Environment and application performance testing completed and signed off
•         Facilities in place (at all work participating in Implementation)
•         Operational readiness planning has completed, including preparatory work for all support group
          Implementation activities
To delete this guidance text box, double click mouse in the left margin then press delete.




                                                                                                          Page 10 of 28
Insert Company Logo



4 Roles & Responsibilities
This section summarises the various roles and responsibilities of the IT and business managers with respect to
Implementation, and dress rehearsals. Each role player will be given a schedule of dates, times, and activities including
signoffs and dependencies relevant to their role within the Dress Rehearsals and Implementation.
To delete this guidance text box, double click mouse in the left margin then press delete.


4.1     Deployment Manager
   Manage planning and execution of dress rehearsals and Implementation
   Manage the Control Room (see section 8)
   Monitor and report progress against Implementation Plan
   Conduct scheduled status meetings


4.2     Steering Committee
   Overall governance of Project
   Resourcing for business components of the detailed Implementation schedule
   Guidance and issue escalation point (escalated from Project Director)
   To be available/on call throughout Dress Rehearsals and Implementation periods for issue
    escalation
   Signoff for Dress Rehearsals
   Signoff to go-live


4.3     Project Director
   Overall management and coordination of Project
   Executive management of the dress rehearsals and Implementation
   Budget management for dress rehearsals and Implementation
   Guidance and issue escalation point (escalated from Deployment Manager)
   Signatory to all status reports issuing from Control Room


4.4     <Vendor> System Lead
   Conduct readiness assessment
   Coordination of <Vendor> responsibilities and resources
   Responsible for ensuring the correct software versions are installed
   Issue resolution


4.5     Business Leader(s)
   Dress Rehearsal and Cut Over data validation and reconciliation
   Coordination of business validation activities including business user activities within their
    areas of responsibility within the business


                                                                                                         Page 11 of 28
Insert Company Logo


   Direction and coordination of Power users and testing staff
   On call during unscheduled periods of Dress Rehearsals and Implementation
   On call for post go-live support
   Issue escalation to Control Room, and participation in issue resolution
   Signoff to validation


4.6    Power Users/Testers
   Perform testing and validation according to plan/directed by Business Leader(s)
   On call during unscheduled periods of Dress Rehearsals and Implementation
   On call for post go-live support
   Issue escalation/issue resolution


4.7    Technology Stream Manager
   Management of technical resources
   Management of hardware and infrastructure
   Management of IT change process
   Guidance and issue escalation point
   Technical signoff to Dress Rehearsals and Implementation


4.8    Application Delivery Team
   Delivery of technical infrastructure as per plan
   Backups and recovery responsibility
   Support components of data load as required
   Testing and confirmation of all infrastructure for Implementation and Go-live


4.9    Legacy Systems Conversion Developer
   Responsibility for delivery of <Legacy System> conversion software
   Coordination of Conversion related resources for Dress Rehearsals and Implementation
   Management of data extract and export to new system for data load
   Ownership of conversion control sheet (balancing and reporting of data conversion record
    counts and control totals)
   Issue escalation and resolution
   Signoff to technical data conversion




                                                                                      Page 12 of 28
Insert Company Logo


5 Implementation Approach & Considerations
In broad terms, the conversion of the legacy system to the new system is to be executed over a weekend period at xxx
date.
EXAMPLE:
The approach is referred to as a “big bang” approach as the legacy system(s) will not be run in parallel with the New
System. Plans and capability will be in place for back-out to the legacy system(s) (over the Implementation weekend)
should the need arise.
In addition to the legacy system(s) conversion the following staged components are required to achieve
Implementation. Each of these components will be incorporated in the detailed Implementation schedule. These
include:
- Manual conversion of <any legacy data required in new system but not included in Data Conversion Suite, e.g., due to
economics of development costs)
- Manual entry of <areas needing pre-population but not covered by the Data Conversion Suite)

The period immediately following Implementation will be monitored as a “bedding in” period. This will entail problem
tracking and resolution, as well as monitoring and testing of the production batches through the first week after go-live.
These tasks will be incorporated into the Implementation schedule.
After Implementation, the legacy system(s) will be decommissioned at an appropriate time to reflect business needs.
These timings are to be determined once the bedding-in period is finished.
To delete this guidance text box, double click mouse in the left margin then press delete.




                                                                                                          Page 13 of 28
Insert Company Logo



6 Dress Rehearsals

6.1     Objectives
The objective of a dress rehearsal is to practice the Implementation process. <Number> dress rehearsals have been
planned for this project.
In theory, the Implementation is rehearsed until we ‘get it right’. In practice, we have <number> rehearsals scheduled,
and each will be measured against the pre-determined signoff criteria for ultimate advancement to the next stage:
Implementation, and Go-live.
It should be noted that for the data conversion (a significant component of the Implementation), many ‘practices’ will
have already been performed during development and system testing.
To delete this guidance text box, double click mouse in the left margin then press delete.


6.2     Scope
The detailed scope of the Dress Rehearsals is determined by the detailed Implementation Schedule.
The scope of each Dress Rehearsal will also be a sub-set of the Implementation. The reasons for this are threefold:
•        Implementation is
								
To top