ES Implementation Process

ES IMPLEMENTATION PROCESS
Prepared by
Sujatha Jogi
Role
Quality
Date of preparation
December 28, 2008
Reviewed by
Lakshmi Narasimhan Komandur Suresh Thiagarajan
Role
Manager SEPG GQM-Quality
Date of Review
December 30, 2008
Approved by
Elizabeth Koshy
Role
Program Manager Process & Metrics
Date of Approval
February 9, 2009
1.1
Circulation List
https://my.igate.com/ipoint/quality/processes. jsp
Version Number
iGATE Global Solutions Limited Classification: Company Internal
iGATE Global Solutions Limited
TABLE OF CONTENTS
1. 2. 3. 4. 5. 6. 7. 8. 9. 9.1 9.2 9.3 9.4 9.5 9.6 10. 10.1 10.2 10.3 10.4 10.5 10.6 10.7 11. 11.1 11.2 11.3 11.4 11.5 12. 12.1 12.2 12.3 12.4 12.5 13. 13.1 13.2 13.3 14. OBJECTIVE ....................................................................................................................................... 4 SCOPE ............................................................................................................................................... 4 ENTRY CRITERIA ............................................................................................................................. 4 INPUT ................................................................................................................................................. 4 PARTICIPANTS ................................................................................................................................. 4 HIGH LEVEL PROCESS STEPS ...................................................................................................... 4 OUTPUT ............................................................................................................................................. 5 EXIT CRITERIA ................................................................................................................................. 6 METRICS ........................................................................................................................................... 6 EFFORT VARIANCE ...................................................................................................................... 6 SCHEDULE VARIANCE ................................................................................................................. 6 DEFECT REMOVAL EFFICIENCY ................................................................................................ 6 DEFECT INJECTION RATE ........................................................................................................... 6 PRODUCTIVITY ............................................................................................................................. 6 COST OF QUALITY ....................................................................................................................... 6 IMPLEMENTATION PROCESS ORACLE & PEOPLESOFT PRACTICE .................................... 6 DEFINITION PHASE .................................................................................................................. 6 OPERATIONS ANALYSIS .......................................................................................................... 7 SOLUTION DESIGN ................................................................................................................... 8 BUILD ........................................................................................................................................ 10 TRANSITION ............................................................................................................................ 12 TRAINING ................................................................................................................................. 13 PRODUCTION .......................................................................................................................... 14 IMPLEMENTATION PROCESS SAP PRACTICE ....................................................................... 16 PROJECT PREPARATION ...................................................................................................... 16 SIZING & BLUEPRINT ............................................................................................................. 20 FUNCTIONAL DEVELOPMENT ............................................................................................... 23 FINAL PREPARATION ............................................................................................................. 28 GO-LIVE & SUPPORT .............................................................................................................. 30 IMPLEMENTATION PROCESS SIEBEL PRACTICE.................................................................. 31 SCOPING & ANALYSIS ........................................................................................................... 31 DESIGN .................................................................................................................................... 33 CONFIGURATION & BUILD ..................................................................................................... 35 TESTING................................................................................................................................... 36 DEPLOYMENT, SUPPORT & MAINTENANCE ....................................................................... 38 PROCESS FLOW CHARTS ............................................................................................................ 40 PROCESS FLOW CHART ORACLE & PEOPLESOFT PRACTICE ..................................... 40 PROCESS FLOW CHART SAP PRACTICE ......................................................................... 41 PROCESS FLOW CHART SIEBEL PRACTICE.................................................................... 41 GLOSSARY ..................................................................................................................................... 42
REVISION HISTORY .................................................................................................................................. 43
February 9, 2009
Classification: Company Internal
Version No. 1.1
Page 2 of 43
February 9, 2009
Version No. 1.1
Page 3 of 43
1. OBJECTIVE The objective of the Enterprise Solutions (referred as ES in the rest of this manual) Implementation Process is to define the execution approach for all implementation projects falling under each of the practice areas in ES, namely Oracle, PeopleSoft, SAP & Siebel. Each of the practice areas have been provided specific individual implementation frame works as sequence of execution for Oracle & PeopleSoft are different from that of SAP or Siebel. While Oracle & PeopleSoft practice will follow one common implementation framework, SAP & Siebel practice areas have their own implementation frameworks. Based on the individual implementation framework for each practice, this process manual has provided separate sections for each practice area and the inputs, the set of tasks to be carried out in each phase and the outputs at the end of each phase have been clearly articulated in each of the sections. Templates, forms, guidelines and checklists have been provided under the respective sections for each of the practice areas. 2. SCOPE In Scope All Implementation Projects in Oracle Apps, SAP, PeopleSoft & Siebel practice units Out of Scope All Customer managed projects in ES business unit. All Upgrade projects in ES business unit. All application support and maintenance projects in ES business unit. All projects falling outside the ES Business unit in the organization.
3. ENTRY CRITERIA 3.1 Signed-off Contract / SOW 4. INPUT 4.1 Signed-off Contract / SOW
5. PARTICIPANTS Delivery Manager, Group Project Manager, Project Manager, Business Process Analyst (BPA), Configuration Manager(CM), Tech Lead, Developer, Quality Facilitator, Networks & Customer representative (SME, SPOC)
6. HIGH LEVEL PROCESS STEPS Sl No. 1. ORACLE & PEOPLESOFT PRACTICE Definition Phase SAP PRACTICE SIEBEL PRACTICE RELATED PROCESS IN QMS - Project Initiation - Project Planning - Project Progress monitoring
Project Preparation
Scoping & Analysis
February 9, 2009
Version No. 1.1
Page 4 of 43
2. 3. 4. 5. 6.
Operations Analysis Solution Design Build Transition & Training Production
Business Blueprint Realization Final Preparation Training Go-live & support
Design Configuration Build Testing Deployment Support Maintenance
&
&
- Estimation process - Development Process - Functional Testing process - Development Process - AMO process
For a detailed flow, refer to Process flow chart of the respective practice in Section 13 of this manual 7. OUTPUT The outputs from each phase for all the practices have been detailed in the respective sections below. Documented below are the key outputs for all the practices. ORACLE & PEOPLESOFT PRACTICE Project Management Plan document Current Business baseline Future process model High Level Gap Analysis Document Application Setups document Conversion Program Design Functional Design Document Technical Design Document Test plans Test scripts Test reports Risk and Issue Log Production support infrastructure document UAT Sign Off Training Documents. Trained key & end users Project Closure report Customer Satisfaction survey SAP PRACTICE Defined company business drivers Defined company business measurements Defined project implementation goals Implementation strategy & document Rollout strategy Approved project plan and schedule Project team training plan Communication plan Change management plan Quality assurance plan Configuration management plan Test plan Post implementation support strategy IT Infrastructure document Release plan Completed requirements document Completed business blueprint End user training & documentation plan Final test design Service level strategy Production system design Test results Final integration test report Refined production support
Version No. 1.1
SIEBEL PRACTICE Signed-off project scope document Project plan Communication plan Gap analysis Requirement specifications Identified data migration requirements Signed-off functional specification document Signed off design documents Test strategy Test plans CRP Plan Test reports Signed off UAT Trained end users Successful deployment of application as per FS in production Open issues resolved and closed Stable application in production Knowledge documents handed over and completed KT sessions Lessons learnt report Signed off project closure document
February 9, 2009
Page 5 of 43
ORACLE & PEOPLESOFT PRACTICE
SAP PRACTICE plan Ready production system Open issues resolved and closed Project sign-off and closure
SIEBEL PRACTICE
8. EXIT CRITERIA Project Support period over 9. METRICS 9.1 EFFORT VARIANCE 9.2 SCHEDULE VARIANCE 9.3 DEFECT REMOVAL EFFICIENCY 9.4 DEFECT INJECTION RATE 9.5 PRODUCTIVITY 9.6 COST OF QUALITY 10. IMPLEMENTATION PROCESS ORACLE & PEOPLESOFT PRACTICE Note: Since the implementation steps are similar to Oracle & PeopleSoft, both practices will follow one single implementation process detailed below; however the templates, guidelines, checklists & standards are different for each practice and the same have been provided under the headings of respective practice areas For a detailed flow, refer to Process flow chart of the respective practice in Section 13 of this manual 10.1 DEFINITION PHASE During Definition phase, the project management team plans the implementation project to define the Project Work Plan. The goals are to identify business and system requirements, propose the future business model, and propose the application and information technology architecture. The project team is organized and oriented. The team develops a plan to ensure team members receive the training and support necessary to perform their roles on the project. Tasks Resp onsib ility Templates /Forms ORACLE: Technical architecture baseline (TMP1) Financial & Operating Structure (TMP2) PM Guidelines Checklists Standards
Inputs
Client Current Technical Architecture Client current financials and operating structures Existing system architecture Current Business model High level process designs
ORACLE: Project Start-up checklist (TMP3)
Tasks
Prepare / procure the Business Process
February 9, 2009
Version No. 1.1
Page 6 of 43
Tasks
Resp onsib ility
Templates /Forms
Guidelines
Checklists
Standards
Architecture Prepare / procure the Current Business baseline document Prepare the Work Management Plans and Procedures Prepare the Project management plan Product Walk-through by the client to project team members Review and Obtain SignOff on Project plan & Current business baseline documents ORACLE: Project management plan (TMP4) Work management procedures (TMP5) Current business baseline (TMP6) PS: Project management plan in QMS Project Status report (TMP3) 10.2 OPERATIONS ANALYSIS During the Operations Analysis phase, the project team collects management, technical, and enduser business process information and requirements. The project team develops business requirements scenarios used to assess the level of fit between the detailed business requirements and standard application functionality. The project team also creates a model for the application ORACLE: Meeting agenda (TMP7) Meeting minutes ORACLE: Project managem ent checklist (TMP9) SME/ SPO C PM PM
Outputs
Project Management Plan document Work Management Procedures Document Current Business baseline
Project progress report (TMP8)
February 9, 2009
Version No. 1.1
Page 7 of 43
structure and suggests an overall technical architecture. Prototyping of business processes may begin in this phase to aid in analysis and demonstrate feasibility of design options. Tasks Inputs Tasks Current Business Baseline( As Is Process) Analyze Current Business operations Responsi bility Templates /Forms Guidelines Checklists Standards
PM
PS: Business requireme nt gathering (TMP9)
Gather accurate information and define detailed function, data and operational requirements Design business processes in detail, covering variants of the high level processes. Prepare business requirements mapping and conduct gap analysis Review and Sign-Off on Future process model, Gap analysis document and Reports list documents Outputs Future process model High Level Gap Analysis Document Master Reports tracking list
PM
PM
PM
PS: Fit-gap analysis (TMP2)
PM
ORACLE: Future business model (TMP10) High level gap analysis (TMP11) Master report tracking list (TMP12)
10.3
SOLUTION DESIGN
The goal of the Solution Design phase is to create the optimal business process solution to meet the current and future business requirements. During Solution Design, project team members design application configuration options and detailed business procedure documentation. Detailed design of any custom extensions, interfaces and data conversions occur during this phase. The team also identifies process and organizational changes required for implementation.
February 9, 2009
Version No. 1.1
Page 8 of 43
Tasks Inputs Current Business Baseline Future process model High Level Gap Analysis Document Master Report Tracking Report list Prepare the Module Design and Application setups Prepare Conversion environment
Responsi bility
Templates /Forms
Guidelines
Checklists
Standar ds
Tasks
PM & Tech lead PM & Tech lead
PS: Data conversion requirement s & strategy (TMP6) Data conversion specification (TMP7)
Prepare/define Conversion standards Prepare design Conversion programs Prepare data Conversion Conduct first CRP (Conference Room Pilot) Review and Sign-Off on Application setup document, security profile document, Conversion environment, Conversion program designs, Functional design document, technical design document and Security profiles Document. Outputs Application Setups document Conversion Environment Conversion Program Design Functional Design Document Technical Design Document Security Profiles
PM & Tech lead PM & Tech lead PM & Tech lead GPM & PM PM
ORACLE: Conversion environment (TMP13) Conversion Program design (TMP 14) Application extensions functional design (TMP15)
February 9, 2009
Version No. 1.1
Page 9 of 43
Tasks
Responsi bility
Templates /Forms Application extension technical design (TMP16) Security Profile (TMP34) BR100 Application setup document set {zip file} (TMP35) PS: Technical specification document (TMP5) Functional design document(TM P4)
Guidelines
Checklists
Standar ds
10.4 BUILD During the Build phase, the development team codes and tests all custom extensions including application enhancements, conversions, and interfaces. The team creates and executes performance, integration and business system tests. This phase of the project is focused mostly on quality control, testing and documentation of the solution. Whether the code is an extension of the packaged application or custom development quality is paramount to the success of this phase of the project. Tasks Inputs Application Setups document Gap Analysis document Development Environment Conversion Program designs Functional Design Document Technical Design Document CRP Comments Develop Conversion Programs Ensure to accommodate CRP Responsi bility Templates /Forms Guideline s Checklists Standards
Tasks
PM & Tech lead Tech lead
February 9, 2009
Version No. 1.1
Page 10 of 43
Tasks comments Develop Business system test plans and perform testing
Responsi bility Tech lead & Develope rs
Templates /Forms PS: Test plan (TMP10) Unit test plan template (TMP15)
Guideline s
Checklists
Standards
Perform Conversion unit tests, business object tests and validation tests. Conduct second CRP (Conference Room Pilot) Resolve the CRP comments and migrate the application along with customizations to UAT instance Obtain Sign Off Review the Test documents and obtain Sign-Off.
PM & Tech led PM & Tech lead PM & Tech lead
PM & Tech lead PM
PS: Test progress report (TMP17) Test closure report (TMP16) ORACLE: Production support infrastructur e (TMP23)
Design Production support infrastructure
GPM & PM
Develop Transition Plan Outputs System Test Script Conversion Test Plans Performance Test Scripts Performance Test Report Risk and Issue Form Risk and Issue Log Production support infrastructure document Develop Transition Plan document
PM & Tech lead ORACLE: System test script (TMP17) Conversion test plans (TMP18) Performance test scripts (TMP19)
February 9, 2009
Version No. 1.1
Page 11 of 43
Tasks
Responsi bility
Templates /Forms Performance test report (TMP20) Risk & issue form (TMP21) Risk & issue log (TMP22)
Guideline s
Checklists
Standards
Transaction & Contingency plan (TMP24) PS: Issue tracker (TMP1) Functional design document (TMP4) Test scripts(TMP 11)
10.5 TRANSITION During the Transition phase, the project team deploys the finished application into the customers organization. The transition phases success depends on the Build phase for the fully tested quality business system. The project team fully executes data conversion and uses the developed documentation to train end users and support staff. The project team conducts a production readiness check with the business user and technical community. There should also be multiple trail runs before the final version is released to the user community. If the implementation includes a phased deployment, transition will occur multiple times with subsets of the applications deployed to various geographical sites and/or business units at different times. Tasks Inputs Tasks Solution Design Document Application Setups document Conduct UAT (User Acceptance Testing) Prepare Production PM & Tech lead PM & Tech lead
Version No. 1.1 Page 12 of 43
Responsi bility
Templates /Forms
Guidelines
Checklists
Standards
February 9, 2009
Tasks Environment Setup applications and verify production readiness Implement production support infrastructure Outputs UAT Sign Off Production Environment Go Live readiness checklist
Responsi bility PM & Tech lead PM & Tech lead
Templates /Forms
Guidelines
Checklists
Standards
ORACLE: Installation QA checklist (TMP25) Production support infrastructur e (TMP23) Transition strategy (TMP26) Internal transition plan (TMP27) PS: Cutover approach plan (TMP14)
10.6 TRAINING During this phase, Project manager will identify the clients technical staff and Key users to provide the training. Training will be given on Functional business flows based on the key users roles. Tasks Inputs Application setups document Technical Design Document Functional Design Document Testing Document PM & Tech lead PM, Tech lead & Develope rs Responsi bility Templates /Forms PS: Applicatio n setup document (TMP13) Guidelines Checklists Standards
Tasks
Identify Key Users and End users. Prepare training material
PS: Training Plan (TMP8)
February 9, 2009
Version No. 1.1
Page 13 of 43
Tasks
Responsi bility
Templates /Forms Training manual(T MP12)
Guidelines
Checklists
Standards
Provide training Outputs Training Documents. Trained key & end users
PM & Tech lead ORACLE: Sample training document {Filled template} (TMP28) Train the trainer Manual (TMP29)
10.7 PRODUCTION The Production phase starts immediately with the production cutover. Production marks the last phase of the implementation and the beginning of the system support cycle. Included in this final phase is a series of refinement and measurement activities. The Information Systems (IS) personnel work quickly to fine-tune the system and begin regular maintenance. The group will also provide ongoing support to the organization for the remaining life of the application Tasks Refine production system Production issue resolution process flow Support Resource Plan Resolve Stabilization issues Fix Production bugs Provide function support to users and technical team Close Project Initiate the Customer satisfaction survey Outputs Issue resolution plan Project Closure report Customer Satisfaction Report Responsi bility Templat es /Forms Guidelines Checklists Standards
Inputs
Tasks
PM & Tech lead PM & Tech lead PM & Tech lead DM, GPM & PM
CSS template
ORACL E: Accepta
February 9, 2009
Version No. 1.1
Page 14 of 43
Tasks
Responsi bility
Templat es /Forms nce certificat e (TMP29) Client Satisfact ion report (TMP30) End report (TMP31) Project closure details (TMP32) iGates custome r satisfacti on survey form (TMP33)
Guidelines
Checklists
Standards
February 9, 2009
Version No. 1.1
Page 15 of 43
11. IMPLEMENTATION PROCESS SAP PRACTICE For a detailed flow, refer to Process flow chart of the respective practice in Section 13 of this manual 11.1 PROJECT PREPARATION The purpose of this phase is to provide initial planning and preparation for SAP ERP (formerly called as SAP R/3) implementation project. Although each implementation project has its own unique objectives, scope, and priorities, the steps in this Phase help identify and plan the primary focus areas to be considered. By following these early in an implementation project, it will help the project manager to ensure that the project proceeds efficiently, and that a solid foundation for a successful implementation project is laid. Tasks Inputs Signed SOW/Contract Documented list of the customers strategic objectives and business measurements for implementation Data gathered from the sales cycle Project scope document Define project mission statement Define business drivers Identify business measurements Identify project measurements Develop change charter Responsi bility Templates /Forms Guidelines Checklists Standards
Tasks
PM PM PM PM PM Refer to SAPs 1) Guidelines for creating a change charter (TMP1)
Assemble project charter components Approve project charter Review implementation proposal
PM PM PM, BPA, Tech lead
Refer to SAPs 1) Enterprise process area scope document (TMP2)
Confirm implementation methodology Check strategy for rollout
PM PM, BPA, Tech lead

February 9, 2009
Tasks Plan environment
Responsi bility PM, BPA, Tech lead
Setup environment
PM & Tech lead
Templates /Forms Refer to SAPs 1) IT Infrastruct ure document( TMP3) Refer to SAPs 1) IT Infrastruct ure document( TMP3)
Guidelines
Checklists
Standards
Define project roles and assign people
DM, GPM & PM
Refer to SAPs 1) Project Roles guidelines (TMP5)
Assign people to create change management team Create project plan
PM PM, Tech lead & SME/SP OC Refer to SAPs 1) Sample project plan (TMP7) Refer to SAPs 1) Project considerat ion guidelines (TMP4) Refer to SAPs 1) Project team training schedule (TMP8) Refer to SAPs 1) Project plan checklist (TMP6)
Prepare training plan
PM, BPA & Tech lead
Schedule team training and arrange for logistics Create communication plan
PM, BPA & Tech lead PM
Refer to SAPs 1) Project work plan report template (TMP16) 2) Weekly project status report template
February 9, 2009
Version No. 1.1
Page 17 of 43
Tasks Create change management plan and establish CAB
Responsi bility PM & BPA
Templates /Forms (TMP9)
Guidelines
Checklists
Standards
Refer to SAPs 1) Guidelines for creating a change charter (TMP1) Refer to SAPs 1) Quality Assurance container template (TMP10) Refer to CM & assets classificati on template in QMS Refer to SAPs 1) End user training plan template (TMP13) 2) Document ation and training needs assessme nt form (TMP12) Refer to: Unit test plan System test plan Integration & Integration test plan
Determine quality assurance standards
PM
Define configuration standards
PM & CM
Define end user training & documentation strategies
PM
Refer to SAPs 1) End user training strategy presentati on (TMP11)
Define testing plan
PM, BPA & Tech lead
Testing guidelines in QMS
Define post-implementation service & support strategy Define development
PM & Tech lead PM &
February 9, 2009
Version No. 1.1
Page 18 of 43
Tasks standards Determine required systems
Responsi bility Tech lead PM & Tech lead
Templates /Forms Refer to SAPs 1) IT Infrastruct ure document( TMP3)
Guidelines
Checklists
Standards
Define release strategy
PM & Tech lead
Conduct project kick-off
PM
Refer to SAPs 1) System & client deployme nt strategy (TMP14) Refer to SAPs 1) Kick-off presentati on, technical part presentati on (TMP15)
Outputs
Review Phase deliverables Signoff project preparation phase Defined company business drivers Defined company business measurements Defined project implementation goals Change charter for implementation project Approved project charter Implementation strategy & document Approved implementation and strategy Rollout strategy Project organization roles & responsibilities Change management team Approved project plan and schedule Project team training plan Communication plan Project meeting schedules
PM DM & GPM
February 9, 2009
Version No. 1.1
Page 19 of 43
Tasks Forms for agendas and minutes Forms for status reporting Change management plan Quality assurance plan Configuration management plan End user training and documentation strategy Test plan Post implementation support strategy Development standards IT Infrastructure document Release plan Kick-off meeting presentation Sign-off on project preparation phase
Responsi bility
Templates /Forms
Guidelines
Checklists
Standards
11.2 SIZING & BLUEPRINT The purpose of this phase is to create the Business Blueprint, which is a detailed documentation of the results gathered during requirements workshops. Furthermore, the Business Blueprint documents the business process requirements of the customer company. On this basis, you achieve a common understanding of how the customer company intends to run its business within the SAP ERP System. Tasks Inputs Previous phase sign-off Project plan Project team training plan & schedule Conduct review meetings and publish periodic status reports Responsi bility Templates /Forms Guidelines Checklists Standards
Tasks
DM, GPM & PM
Refer to SAPs 1) Weekly project status report template (TMP9)
Conduct necessary project team member training to upgrade all resources to required skills Create technical design by documenting the a) network environment b) system environment &
PM
Tech lead, System admin &
Refer to SAPs 1) IT Infrastruct
February 9, 2009
Version No. 1.1
Page 20 of 43
Tasks c) desktop environment sections of the IT Infrastructure document Document appropriate sections of the security manual Start defining customer business organization structure within the system Schedule and conduct workshops Recommend and seek approval on target organizational structure Schedule & prepare for Business process workshops Conduct general requirements gathering workshop Conduct Business process workshop
Responsi bility Network admin PM & Tech lead
Templates /Forms ure document( TMP3) Refer to SAPs 1) Security Manual (TMP17)
Guidelines
Checklists
Standards
PM
PM PM
PM PM & BA
PM & BA
Assess the need for additional detailed requirements gathering workshops
PM & BA
Refer to SAPs 1) Conversio n Questionn aire (TMP19) Refer to SAPs 1) Enhance ment justificatio n form (TMP20) Refer to SAPs 1) Process design template (TMP21) 2) Technical design template (TMP22) Refer to SAPs 1) Sample business blueprint summary
Page 21 of 43
If necessary, schedule & conduct detailed requirements workshop
PM & BA
Assemble Business blueprint
PM
February 9, 2009
Version No. 1.1
Tasks Complete Business blueprint Present business blueprint and obtain sign-offs Draft end user training and documentation plan
Responsi bility PM PM PM
Templates /Forms
Guidelines
Checklists (TMP23)
Standards
Refer to SAPs 1) End user training plan (TMP13)
Develop prototype Finalize end user training and documentation Set-up the development environment
PM PM & Tech lead PM & Tech lead
Refer to SAPs 1) IT Infrastruct ure document( TMP3)
Install and configure development system clients Configure and test transport system Document Dev clients section of the IT Infrastructure document
Tech lead & System administr ator Tech lead & System administr ator PM & Tech lead
Refer to SAPs 1) IT Infrastruct ure document( TMP3) Refer to SAPs 1) Checklist for system administra tion (TMP18)
Define system administration for development system
Tech lead & System administr ator
Define backup strategy Create implementation guide Review phase deliverables Sign off phase Outputs Trained project team Technical design created in
Tech lead PM & Tech lead DM, GPM & PM DM & GPM
February 9, 2009
Version No. 1.1
Page 22 of 43
Tasks IT infrastructure document Development System DEV, and other appropriate sections, documented in the IT Infrastructure Document System administration is setup and verified Implementation guide ready Documented organization structure of customer company Completed requirements document Completed business blueprint Management approved business blueprint End user training & documentation plan Sign-off on Sizing & Business blueprint phase 11.3 FUNCTIONAL DEVELOPMENT
Responsi bility
Templates /Forms
Guidelines
Checklists
Standards
The purpose of this phase is to implement business and process requirements based on the Business Blueprint. The objectives are final implementation in the system, an overall test, and the release of the system for production (live) operation. The project team receives relevant knowledge. Tasks Inputs Previous phase sign-off Project plan Business blueprint End user training plan Project charter IMG documentation Business process master list Conduct review meetings and publish periodic status reports Responsibili ty Templates /Forms Refer to iGate technical specificati on template (TMP43) Refer to SAPs 1) Weekly project status report template (TMP9) Refer to SAPs Golive template Guidelines Refer to estimation guidelines (TMP38) Checklists Refer to iGate Technical specificati on checklist( TMP42) Standards
Tasks
DM, GPM & PM
Perform Initial planning for production support and cutover
PM, BPA & Tech lead
Refer to iGates Functional specificati
Refer to SAPs 1) Cutover process
February 9, 2009
Version No. 1.1
Page 23 of 43
Tasks
Responsibili ty
Guidelines ons document (TMP41) Refer to SAPs 1) Final configurati on flow chart (TMP29)
Checklists checklist( TMP25)
Standards
Develop plans for baseline configuration
PM & SME/SPOC
Refer to SAPs 1) Sample baseline scope document( TMP26) 2) Case procedure template (TMP27) Refer to SAPs 1) Baseline scope document test plan (TMP28) 2) Refer to UTC template (TMP44)
Determine test cases & create test plan for baseline
Tech lead & developers
Refer to Code review document (TMP40)
Configure initial settings and organizational structure Configure and validate baseline Test baseline Document and resolve issues Refine business blueprint Prepare baseline confirmation
Tech lead & developers SME/SPOC Tech lead & SME/SPOC PM & Tech lead PM & SME/SPOC Tech lead & SME/SPOC
Refer to SAPs 1) Case procedure template (TMP27)
Perform baseline confirmation review and signoff Develop system test plans
SME/SPOC
Tech lead
Refer to SAPs 1) Volume & Stress test plan(TMP

Page 24 of 43
February 9, 2009
Version No. 1.1
Tasks Establish service level commitment Establish system administration functions Setup quality assurance environment Set-up Quality Server
Responsibili ty Tech lead Tech lead & System administrat or System Administrat or PM & System Administrat or PM, BPA & SME/SPOC PM, BPA & SME/SPOC
Templates /Forms 30)
Guidelines
Checklists
Standards
Commence final configuration and confirmation Develop plans for final scope configuration
Refer to SAPs 1) Final configurati on step by step guide (TMP31)
Refer to SAPs 1) Final configurati on flow chart (TMP29)
Conduct configuration workshops Document and resolve issues Configure and validate final scope Test final configuration
PM PM PM & SME/SPOC PM, SME/SPOC & End users PM, SME/SPOC & End users PM, SME/SPOC & End users Tech lead and developers
Prepare final confirmation scenarios Perform final confirmation
Prepare & co-ordinate ABAP development
Create conversion procedures
Tech lead and developers
Refer to SAPs 1) Data mapping form
Refer to ABAP Coding standards (TMP37) Refer to ABAP naming & coding standards
Page 25 of 43
February 9, 2009
Version No. 1.1
Tasks Test and migrate conversion programs Develop application interface programs Test and migrate interface programs Develop enhancement procedures Test and migrate enhancement procedures Create reports Test and migrate reports Create forms Test and migrate forms Create authorization detailed design Implement authorization concept Validate authorization concept Establish and create archiving management Define integration test scope
Responsibili ty Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers
Guidelines
Checklists
Standards (TMP39)
Refer to SAPs 1) Integration test procedure template (TMP33)
Refer to SAPs 1) Final integration test approach (TMP34)
Define test cases and integration plan Freeze system
Tech lead and developers Tech lead and

February 9, 2009
Tasks Conduct integration testing Finalize system Prepare end user documentation development plan Create end user documentation Develop end user training material Prepare & conduct end user training Define production system design Define production system management Setup production environment Review phase deliverables
Responsibili ty developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers Tech lead and developers System Administrat or Tech lead DM, GPM & PM
Templates /Forms
Guidelines
Checklists
Standards
Refer to SAPs 1) Realizatio n quality checklist (TMP35)
Outputs
Sign-off phase Baseline scope document Baseline configuration plan Baseline test cases Baseline test plan Documented configuration results Updated case procedures Recorded issues in the issue management system Refined Business Blueprint Confirmed scenarios out of the Baseline scope document Final test design List of failure scenarios and their impact Procedures for disaster
SME/SPOC
February 9, 2009
Version No. 1.1
Page 27 of 43
Tasks recovery Service level strategy System administration functions have been verified, tested and documented Quality assurance environment is ready for testing from development Production system design Production system administration procedures and environment Installed and technically configured production environment Final configuration plan Final configuration test plan Configured and tested system Final confirmation scenarios Project conversion plan Manual conversion procedures Automatic conversion programs Required conversion resources Test results Interface programs All enhancements, required by the business blueprint, are tested, approved, and migrated to the quality assurance environment Reports & forms created, tested and migrated Sign-off authorization design Final integration test report End user training documents and plan Phase sign-off 11.4 FINAL PREPARATION
Responsibili ty
Templates /Forms
Guidelines
Checklists
Standards
The purpose of this phase is to complete the final preparation, including testing, end user training, system management and cutover activities, to finalize your readiness to go live. The Final Preparation phase also serves to resolve all crucial open issues.
February 9, 2009
Version No. 1.1
Page 28 of 43
Tasks Inputs Previous phase sing-off Project plan Revised business blueprint Conduct review meetings and publish periodic status reports
Responsi bility
Templates /Forms
Guidelines
Checklists
Standards
Tasks
DM, GPM & PM
Refer to SAPs 1) Weekly project status report template (TMP9)
Prepare for end user training Conduct end user training Establish production system administration Train system administration staff Conduct volume, stress and system administration tests Conduct going live check
PM PM System administr ator System administr ator System administr ator PM & Tech lead Refer to SAPs 1)Go-live template (TMP24)
Review conversion timing and planning Create conversion checklist Determine production readiness Approval for cutover Refine production support plan Perform cutover to production system Approve the production system Secure production environment
Tech lead & SME/SP OC PM & Tech lead PM & Tech lead PM & SME/SP OC PM & SME/SP OC PM, Tech lead & SME/SP OC PM, Tech lead & SME/SP OC PM, Tech lead &
February 9, 2009
Version No. 1.1
Page 29 of 43
Phase deliverables review
Phase sign-off
SME/SP OC DM, GPM, PM & SME/SP OC DM, GPM, PM & SME/SP OC
Outputs
End user training logistics are finalized, the training environment is initialized, and training data is loaded into the training environment End users have completed training for Go Live System administration procedures configured in the production environment, trained ongoing technical staff The configuration of the system, and the procedures defined for the technical environment, are tested and validated Updated project plan as ready for going live for management approval Refined production support plan Ready production system Approval for go-live Phase sign-off
11.5 GO-LIVE & SUPPORT The purpose of this phase is to move from a pre-production environment to live production operation. You must set up a support organization for end users, not just for the first critical days of your production operations, but also to provide long-term support. During this phase, end users of the new system have many questions. There must be a solid end user support organization easily accessible to all end users. This phase is also used to monitor system transactions and to optimize overall system performance. Finally, the completed project is closed. Tasks Inputs Previous phase sing-off Responsi bility Templates /Forms Guidelines Checklists Standards
February 9, 2009
Version No. 1.1
Page 30 of 43
Tasks
Conduct review meetings and publish periodic status reports
DM, GPM & PM
Detect problems and issues
PM
Refer to SAPs 1) Weekly project status report template (TMP9) Refer to SAPs 1) Go-live and support phase agenda template (TMP36)
Manage and resolve problems Confirm live environment Get written approvals / signoffs Review and close open issues Summarize the review lessons learnt report Final sign off and close project Procedures for handling calls and questions from operational users are established and distributed to end users and support staff New system officially recognized as being in production Open issues resolved and closed Project sign-off and closure
PM SME/SP OC PM PM PM PM
Outputs
12. IMPLEMENTATION PROCESS SIEBEL PRACTICE For a detailed flow, refer to Process flow chart of the respective practice in Section 13 of this manual 12.1 SCOPING & ANALYSIS During Scoping & Analysis phase, the project management team plans the implementation project to define the Project Work Plan. The goals are to identify business and system requirements, propose the future business model, and propose the application and information technology architecture. The project team is organized and oriented. The team develops a plan to ensure team members receive the training and support necessary to perform their roles on the project. (Also refer to Project Initiation process & Quality Facilitation process in QMS)
February 9, 2009
Version No. 1.1
Page 31 of 43
Tasks Inputs Signed contract / SOW Package evaluation and selection completed Project organization and implementation team formed Prepare project scope statement Prepare project plan
Responsi bility
Templates /Forms
Guidelines
Checklists
Standards
Tasks
PM PM Project plan template in QMS
Staff project team Project communication and protocol setup Identify project stakeholders Identify the final SME/SPOCs for final sign-off on requirements and & UAT Identify change management team Prepare training plan
PM PM DM & PM PM & Tech lead PM & Tech lead PM & Tech lead
Applicatio n assessme nt & KA template
KA & KT Guidelines
Prepare quality guidelines Understand as is business flow
PM & Tech lead PM & BPA
Understand new requirements and reporting needs Perform business process mapping and Gap analysis Conduct requirements elucidation sessions Study the deployment requirements Understand satellite systems and integration requirements Get sign-off on the satellite system needs from the relevant owners.
PM & BPA
Applicatio n assessme nt & Knowledg e acquisition template in QMS Requirem ents & Solution document
Applicatio n assessme nt guidelines in QMS KA & KT Guidelines
PM & BPA PM & BPA PM & BPA PM & BPA PM & BPA
February 9, 2009
Version No. 1.1
Page 32 of 43
Tasks Identify the data migration requirements Prepare functional specification document for new requirements Sign off on the functional specification document Understand the existing network and security requirements
Responsi bility PM & BPA PM & BPA PM & BPA PM, System Administr ator & Network Administr ator PM, System Administr ator & Network Administr ator PM PM & Tech lead DM, GPM & PM DM, GPM & PM
Templates /Forms
Guidelines
Checklists
Standards
Perform the server sizing and get the sign-off
Place requests for hardware and software requirements Build the development environment Review phase deliverables Sign-off on phase Outputs Signed-off project scope document Project plan Communication plan Identified SME/SPOC Gap analysis Requirement specifications Identified data migration requirements Signed-off functional specification document Development environment
12.2 DESIGN During the Design phase, the project team collects management, technical, and end-user business process information and requirements. The project team develops a High level and low level design and obtains sign-off on the same. The project team also creates test strategy and test plans. Prototyping of business processes may begin in this phase to aid in analysis and demonstrate feasibility of design options. Tasks Responsibilit y
Version No. 1.1
Templates /Forms
Guidelines
Checklists
Standards
February 9, 2009
Page 33 of 43
Tasks Inputs Previous phase sign-off Signed-off requirements specifications Signed-off functional specifications Development environment ready Access to legacy systems for integration & DM tasks Prepare design documents (HLD & LLD) Get sign-offs on design documents (HLD & LLD) Prototyping Prepare integration HLD & LLD documents
Responsibilit y
Templates /Forms
Guidelines
Checklists
Standards
Tasks
PM & BPA PM & BPA PM & BPA PM & BPA
HLD Template LLD Template
HLD review checklist LLD Review checklist
Convert design into architecture Design migration plan and take sign-off Perform data mappings and prepare DM scripts Test strategy and test plan preparation
PM & Tech lead PM & Tech lead PM & Tech lead PM & Tech lead
Baseline Inventory template
Test report Requirem ents & solution document (Test plan part) Unit plan test
Testing guidelines
Deployment guidelines preparation and distribution Based on the FS prepare user guide with change management team Create CRP (Conference room pilot) Plan Review phase deliverables Sign-off on phase
PM & Tech lead PM & Tech lead PM DM, GPM & PM DM, GPM &
February 9, 2009
Version No. 1.1
Page 34 of 43
Tasks Signed off design documents Test strategy Test plans CRP Plan
Responsibilit y PM
Templates /Forms
Guidelines
Checklists
Standards
Outputs
12.3 CONFIGURATION & BUILD During the Build phase, the development team codes all custom extensions including application enhancements, conversions, and interfaces. Also the test scripts and test plans are prepared in this phase to commence testing after the build. Tasks Inputs Previous Phase sign-off CRP Plan Signed of design documents Development team & environment Conduct review meetings and publish periodic status reports Commence build on signedoff design documents Build interfaces and raise dependencies Support the development environment Ready test environments Test script preparation and review Responsibil ity Templates /Forms Guidelines Checklists Standards
Tasks
DM, GPM & PM Tech lead & Developers Tech lead & Developers Tech lead & Developers Tech lead & Developers Tech lead & Developers
Test environme nt setup checklist Test case developm ent checklist Test case review checklist Functional configurati on audit checklist
Perform unit testing
Tech lead & Developers
February 9, 2009
Version No. 1.1
Page 35 of 43
Tasks Conduct conference room pilot session Update data mapping sheets & DM Scripts Trial DM runs (1&2) based on new meta data Update deployment plan Trial deployment (1&2) Provide training to client ambassadors Review phase deliverables Sign-off on phase Outputs Application built as per design document Configuration document Reviewed test scripts Signed off CRP
Responsibil ity Tech lead & Developers Tech lead & Developers Tech lead & Developers PM & Tech lead PM & Tech lead PM & Tech lead DM, GPM & PM DM, GPM & PM
Templates /Forms
Guidelines
Checklists
Standards
Transition checklist
12.4 TESTING During the Testing phase, the development team tests all custom extensions including application enhancements, conversions, and interfaces. The team creates and executes performance, integration and business system tests. This phase of the project is focuses most heavily on quality control, testing and documentation of the solution. Whether the code is an extension of the packaged application or custom development quality is paramount to the success of this phase of the project. Tasks Inputs Previous phase sign-off Application built as per FS Reviewed test scripts Test environment and teams Testing tools (if needed) Conduct review meetings and publish periodic status reports Responsibi lity Templates /Forms Guidelines Checklists Standards
Tasks
DM, GPM & PM
Project review module in iQuest
Repository migration to test environments Support test environments
Trace ability matrix
Testing Guidelines
Functional testing checklist
February 9, 2009
Version No. 1.1
Page 36 of 43
Tasks Trial DM runs based on new meta data Perform integration testing
Responsibi lity PM & Tech lead PM & Tech lead
Templates /Forms
Guidelines
Checklists
Standards
Perform system testing Perform regressions testing
Perform UAT Generate test reports
PM, Tech lead & Users PM & Tech lead
Integration & Integration test plan System Test plan Multiple regression estimation template User acceptanc e test plan Test report form Defect Collection Defect Estimation template
Regressio n testing checklist
Bug fixing
Tech lead & developers
Handle the change requests Sign-off on testing reports Ready production and pre production environment Trial deployment on pre production environment Help ambassadors in training end users Review phase deliverables Sign-off on phase Outputs Test reports Signed off UAT Trained end users
Tech lead & developers SME/SPO C PM & System administrat or PM & System administrat or PM & Tech lead DM, GPM & PM DM, GPM & PM
February 9, 2009
Version No. 1.1
Page 37 of 43
12.5 DEPLOYMENT, SUPPORT & MAINTENANCE The purpose of this phase is to move from a pre-production environment to live production operation. During this phase, end users of the new system have many questions. There must be a solid end user support organization easily accessible to all end users. This phase is also used to monitor system transactions and to optimize overall system performance. Finally, the completed project is closed. Tasks Inputs Previous phase sign-off Signed off UAT Pre production & production environment ready Application users trained and ready Successful DM runs Go-live rehearsal & production back-ups Final data migration Deployment co-ordination Go-live Deployment support Warranty support enhancements Get written approvals / signoffs Review and close open issues Summarize the review lessons learnt report Final sign off and close project Outputs Successful deployment of application as per FS in production Open issues resolved and closed Stable application in production Knowledge documents handed over and completed KT sessions Lessons learnt report
Responsibili ty
Templates /Forms
Guidelines
Checklists
Standards
Tasks
PM & Tech lead Tech lead & Developers PM, Tech lead & SME/SPOC PM, Tech lead & SME/SPOC PM, Tech lead & SME/SPOC PM & Tech lead PM PM & SME/SPOC PM DM, GPM, PM & SME/SPOC
Transition checklist
Transition plan
Project analysis report
Project closure checklist
February 9, 2009
Tasks Signed off project closure document
Responsibili ty
Templates /Forms
Guidelines
Checklists
Standards
February 9, 2009
Version No. 1.1
Page 39 of 43
13. PROCESS FLOW CHARTS 13.1 PROCESS FLOW CHART ORACLE & PEOPLESOFT PRACTICE The following is a process flow illustrating the different phases of the implementation process for Oracle & PeopleSoft practice. (Note: Since the implementation steps are similar to Oracle & PeopleSoft, both practices will follow one single implementation process detailed below)
ES Implementation Process - ORACLE & PEOPLESOFT PRACTICE
Inputs Tasks
Client current technical architecture Client current financials & Operating structures Existing system architecture Current business model High level process designs
Output
Business process architecture Work management plans & procedures Production walk through by the client to project team Review & obtain signoff on Proj Plan & as-is biz baseline docs Project management plan Work managemetn procedures Current business baseline
Operational analysis Defenition phase phase
Current business baseline (as-is process)
Analyse current business operations
Define detailed function, data & Ops req
Design business processes
Business requirements mapping & gap analysis
Review & sign-off on future process model, gap analysis & rpts list docs Model design & apps setups Preparation conversion environment Define conversion strategy Design conversion programs
Future process model High level gap analysis document Master reports tracking list
Solution design phase
Current business base line Future process model High level gap analysis document Master report tracking report list
Data conversion
Conduct first CRP
Review & sign-off Apps set-up doc, Conversion environment, conversion program designs, FDD, TDD & Security profiles document Develop business system test plans & performance testing Perform unit, biz obj & validation tests
Application set-ups document Conversion environment Conversion program design Functional design document Technical design document Security profiles
Build phase
Application set-ups document Gap analysis document Development environment Conversion programs design Functional design document Technical design document & CRP comments
Develop conversion programs
Ensure to accomodate CRP comments
Conduct Secind CRP
Resolve CRP issues & migrate apps to UAT instance
Review test docs & obtain sign-offs
Design Prod supp infra & transition plan
System test script Conversion test templates Performance test scripts Performance test report Risk & issue form Prod supp infra document Transiton plan document
Transition phase
Solution design document Application set-ups document
Conduct user acceptance test
Prepare production environment
Setup applications & verify prod readiness
Implement prod support infra
UAT sign-off Production environment Go-live readiness checklist
Training phase
Application set-up documents Technical design document Functional design document Testing document
Identify key users & end users
Prepare training material
Provide training
Training documents Trained key & end users
Production phase
Refine production system Production issue resolution process flow Support resoruce plan
Resolve stabilization issues
Fix production bugs
Provide function support to users & tech team
Close Project
Issue resolution plan Project closure report Customer satisfaction survey
February 9, 2009
Version No. 1.1
Page 40 of 43
13.2 PROCESS FLOW CHART SAP PRACTICE The following is a process flow illustrating the different phases and the tasks to be carried out under each of the phase for a SAP ERP Implementation project.
ES IMPLEMENTATION PROCESS - SAP Practice
Inputs Tasks
SOW Data from sales cycle Project scope doc Documented customers objectives for implementation
Output
Roll out strategy Detailed Project plan Communication plan Change mgmt plan Training plan Test plan IT Infrastructuer doc
Project preparation
Initial project planning
Define implementati on standards & Procedures
Project kickoff
Technical requiremetns planning
Perform quality check & obtain approval
Sizing & Blueprint
Previous phase signoff Project Plan Training plan & Schedule
Create technical design
Initialize IMG
Define business organization structure
Business process defenition
Create Business blueprint
End user training & documentatio n plan
Trained project team Technical design Implementation guide Completed business blueprint document
Setup dev environment
Phase signoff
Functional development
Previous phase signoff Project plan Business blueprint End user training plan Project charter IMG documentation Business process master list
Baseline config & confirmation
Perform final configuration
Prepare & co-ordinate ABAP dev
Develop conversion programs
Develop interface programs & Enhancements
Develp reports & forms
Set-up Quality Server
Final integration testing
End user training material and phase sign-off Refine cutover & prod support plan
Set up production environment Perform cutover to production system
Baseline config plan Refined biz blueprint Service level strategy Production system design Final configuration Test results Final integration Phase sign-off
Final preparation
Previous phase signoff Project plan Revised Business blueprint
Conduct end user training
Establish production system
Conduct system tests
Go-live
Conduct quality check & obtain approval
Phase deliverables review & sign-off
Trained end users Configured production environment Production ready system Go-live User guidelines Phase sign-off
Go-live & Support
Previous phase signoff Live production system
Prepare golive & prod support
Provide production support
Manage & resolve issues
Validate live business process results
Confirm live environment
Resolve all open issues
Initiate project closure
Review performance & lessons learnt
Project closure report & signoff
Procedure for handling queries from end users Open issues resolved and closed Project sign-off and closure
13.3 PROCESS FLOW CHART SIEBEL PRACTICE The following is a process flow illustrating the different phases and tracks of the implementation process for SIEBEL practice. (Note: The Siebel practice has classified its implementation tasks into
February 9, 2009
Version No. 1.1
Page 41 of 43
Phases & Tracks and the same has been illustrated below. However the inputs, tasks and outputs in section 12 have been provided at a phase level and not at phase & track level)
ES Implementation process - Siebel Practice
Scoping & Analysis Phase
Project Management track
Project Scope Stagement Project Plan preparation Get signoffs on design document (HLD, LLD) Warranty Support guidelines signoff
Design

Configuration & Build

Resolve Issues & change control Manage Scope & Milestones Communications & Status reporting Stake holder management
Testing
Deployment, Support & Maint.
Staffing
Identify SME's for final sign-offs (UAT & Req.)
Identify project stakeholders
Project Communicati on protocol setup Peform biz process mapping & Gap analysis
CRP Sessions support
Handle CRs
Sign-off on Integration & system testing
Deployment support
Final project sign-off
Functional development
Understand as is business flow
Understand the new requirements
Prepare HLD, LLD & obtain signoff
Prototyping
Development on Signed-off design documents
Unit testing Bug fixing Deployment support Warranty support enhancements
Signoff on Funcional Specification
Prepare functional specification document for new requirements
Requirement s elucidation sessions
Conduct CRP
Integration
Understand satellite system & integration requirements
Get sign-offs on integration needs
Prepare integration HLD & LLD documents
Unit testing
Build interfaces Bug fixing Deployment support
Warranty support enhancements
Conduct CRP
Infrastructure & Admin
Understand existing network & security requirements
Perform server sizing & get signoff
Prepare development & test environments
Develop architecture from design documents
Support the dev environment
Ready test environment
Repository migration to test environment
Support testt environment
Place requests for HW & SW requirements
Go-live rehersal & production back-ups
Go-live
Build the development environment
Support the environments
Prepare prod & pre-prod environments
Data Migration (DM)
Identify data migration requirements
Desing migration plan & take signoff
Perform data mapping & prepare DM scripts
Update data mapping sheets & DM scripts
Trial runs (1&2) based on new meta data from Siebel
Trial DM runs based on new metadata from Siebel
Final data migration
Update deployment plan
Testing
Test strategy preparation
Test plan preparation
Test scripts template
Review template
Integration testing System testing Regression testing Performance testing
UAT support
Deployment Support
Deployment
Study the deployment requirements
Deployment guidelines preparation & distribution
Trial deployment (1&2)
Trial deployment on pre-prod environment
Deployment co-ordination
Training & Quality
Identify change management team
Prepare training plan
Based on FS prepare user guide
Provide training to client ambassadors Perform periodic quality audits
Quality reporting
Prepare training material
Help ambassadors in their training to end users
Help ambassadors in their training to end users
14. GLOSSARY
12.1 12.2 12.3
SOW Statement of Work DM Delivery Manager GPM Group Project Manager

February 9, 2009
12.4
12.5 12.6 12.7 12.8 12.9 12.10
PM Project Manager CM Configuration Manager CRP Conference Room Pilot UAT User Acceptance Testing QF Quality facilitator DM Data mapping BPA Business process analyst
REVISION HISTORY
# 1 2 Date 10 September 2007 th 9 February 2009
th
Version # 1.0 1.1
Section Changed Initial Version Section 9 RFPI 1613 Section 10.1 RFPI 1614 Section 10.1 RFPI 1615 Section 10.2 RFPI 1616 Section 10.3 RFPI 1617 Section 10.4 RFPI 1618 Section 10.7 RFPI 1619
Details of changes made
Approved By Elizabeth Koshy Elizabeth Koshy
- Removed OTD metrics - Tasks updated with the proper verbs. - Added Prepare project management plan in tasks - updated TPM to TMP - Prepare business requirements mapping and conduct gap analysis -updated the sentence Prepare /define Conversion standards - Project is focuses most heavily is rephrased as Project is focused mostly on. - Added initiate CSS in the tasks
February 9, 2009
Version No. 1.1
Page 43 of 43

ES Implementation Process

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ES Implementation Process

Diunggah oleh

Hak Cipta:

Format Tersedia

ES IMPLEMENTATION PROCESS

iGATE Global Solutions Limited Classification: Company Internal

iGATE Global Solutions Limited

REVISION HISTORY .................................................................................................................................. 43

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Scoping & Analysis

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Operations Analysis Solution Design Build Transition & Training Production

Business Blueprint Realization Final Preparation Training Go-live & support

Design Configuration Build Testing Deployment Support Maintenance

Classification: Company Internal

iGATE Global Solutions Limited

ORACLE & PEOPLESOFT PRACTICE

ORACLE: Project Start-up checklist (TMP3)

Prepare / procure the Business Process

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Resp onsib ility

Project progress report (TMP8)

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

PS: Business requireme nt gathering (TMP9)

PS: Fit-gap analysis (TMP2)

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

PM & Tech lead PM & Tech lead

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

PM & Tech lead Tech lead

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Responsi bility Tech lead & Develope rs

PM & Tech led PM & Tech lead PM & Tech lead

PM & Tech lead PM

Design Production support infrastructure

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Classification: Company Internal

iGATE Global Solutions Limited

Responsi bility PM & Tech lead PM & Tech lead

Identify Key Users and End users. Prepare training material

PS: Training Plan (TMP8)

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Templates /Forms Training manual(T MP12)

Classification: Company Internal

Version No. 1.1

iGATE Global Solutions Limited

Classification: Company Internal