global pm method logy

7/31/2019 Global PM Method Logy

1/12

Multi site and source systems deploymentFramework and Methodology

Frank Pataky


2/12

About the Deployment MethodologyDeployment Methodology is a globally consistent framework for implementing Projects. It

provides guidance, a road map and templates to help sites successfully plan and manage ERP

deployment where multiple sites and multiple source system conversions are need.

Why a standardmethodology?

Focused effort,less rework,

increasedefficiency

Access to righttools

and templatesspeeds up

deployment

Standardapproach

= reduced time= reduced cost

Consistentapproachto tracking

benefits

Right first timeimplementation


3/12

The 17 Deployment Methodology stages

The deployment methodology has been divided into 17 key stages which can at times overlap or run in parallel

Risked Based Project Management (RBPM) stages are also shown to illustrate the alignment of the Framework

with the quality assurance requirements as outlined by RBPM methodology

Objectives, high level milestones, outputs and deliverables are detailed within each stage

R B P M

1. Initiation 2. Requirements &Analysis 3. Design 4. Build 5. Test 6. Transition

7. PostImplementation

S t a g e s

1. DeploymentSite

Evaluation

2. DeploymentProject

Initiation

3. Impact

Analysis4. Inbound &

Outbound DataSourcingAnalysis

5. DataMappingAnalysis

6. Technical

Design

7. ProcessDesign

8. Build / Unit

Test

9. Functional

Rules Testing

10. TechnicalTesting

11. UAT

12. Finance/ITOperations

Setup

13. Parallel Run& Initial Process

Changes

14. Book ofRecord


Project Review& Closure

15. SourceSystem

Tranches16. ProcessChange &Benefits

Realization


4/12

Deployment Methodology: Stages 1-2

Knowledge = predictability

The more we know upfront, the more accurate theestimates for time and effort required to do the job

No assumptions on site readiness

Evaluation identifies if site is not ready or timing isntright

Site onboarding and expectation management

Allows us to work with the site to identify scope andbenefits of deployment, and gain buy-in from keystakeholders

A standard approach = smoother project kick-off and lifecycle

Budget approved and locked in, adequate resourcingagreed at these earlier stages

R B P M

1. Initiation

S t a g e s

1. Deployment SiteEvaluation

2. DeploymentProject Initiation


5/12


Local requirements identified, analysed and agreed

Confirm the fit of the standard deployment components Target, Gold, Group Systems and standard feeds for the site

Legacy to target data mapping is done

Needs skills and experience but also standard tools and

templates to make the process easier and more predictable

R B P M

2. Requirements &Analysis

S t a g e s

3. Impact Analysis

4. Inbound &Outbound Data

Sourcing Analysis

5. Data MappingAnalysis


6/12

FTP Deployment Methodology: Stages 6-11

A stage dedicated to process design

Functional Rules Testing (TURF)Included as a particular form oftesting required for platformdeployment

Central environments

= standardised projects andreduced cost and deliverydependencies

R B P M

3. Design 4. Build 5. Test

F T P S

t a g e s

6. Technical

Design

7. ProcessDesign

8. Build / Unit

Test

9. Functional

Rules Testing

10. TechnicalTesting

11. UAT


7/12


Transition stage is one of the most complex

Consistent operations set up, not reinventing the wheel

Leverage the significant amount of work already done tosupport the current deployments

Adaptable methodology: Supports parallel run

Standard approach to Book of Record

Leverage and standardise tranche experiences

Its here where benefits and process changes are realised themethodology will give us a standard approach and tools for this

R B P M

6. Transition

S t a g e s

12. Finance/ITOperations Setup

13. Parallel Run & InitialProcess Changes

14. Book of Record

15. Source SystemTranches

16. Process Change &Benefits Realization


8/12

FTP Deployment Methodology: Stage 17

Often the forgotten stage in projectsbut value shouldnot be underestimated

Review and closure, gathering of lessons learnedand improvements will be critical to improving themethodology if we are to reduce the time tomarket and the cost of deployment

Continuous improvement

We will gather improvements and makeadjustments at each stage to fine tune themethodology not waiting 18 months to improvethings

R B P M


F T P

S t a g e s


Project Review &

Closure


9/12

Implement using a structured and repeatable framework to:

Minimise cost

Maximise standardisation

Reduce duration of implementation projects

Use Standard Deployment Methodology

Start at a sigle site

Develop Future sites target: plan and plan per site

Drive deployment to sites from regional team using Subject Matter Expert (SME)resource

Develop a sprate roll-out plan for each sites

Our approach


10/12

The how

Testing

Processes &Functionality

DataManagement

InformationManagement& Reporting

BUILD

Communications & Engagement

Support

Operations

Implementation& Transition

DEPLOY

Project Governance & Co-ordination

Technology Infrastructure

Business Change and Benefits Realisation

Nine work-streams sharing both Finance and IT resources


11/12

Resources

Build a region-centric team to run multiple site deployments in tandem

Build a global team of SME to be travel to site implementations as required

Provide Subject Matter Expert (SME) regional team resources to support site teams

Follow the standard work stream organisation both in region and site teams

Functiuonal Users and IT to work closely together, ideally physically co-located

Avoid the need for building substantial implementation teams in each site but develop lasting skills and experience in the site teams

Develop a partnership between local teams to deliver to other regional sites

Target team composition 20 % from previous sites 80% from local sites

Recruit and develop the global teams


12/12

One Team

Mix of roles, skills and

grades across countries

Excellent cross-site

communications

Building a One Team environment

Joint recruitment approach

Flexible working

practises

Team mobility

Career progression and

succession planning

Comprehensive on-boarding

and team development plan

Joint Business and IT teamwork Local and region teams

working in unison

global pm method logy

Documents