SAP_PRODUCT IMPLEMENTATION PROCEDURE
Name of the document : SAP_Product Implementation Procedure
Document Number : QMS-40418-V1.4
Maintained by : Quality Management Representative
Release date : 01-Jan-06 Expiry Date: 31-Dec-08
Revision History
| Sr No | Date of Revision | VER | Section Number | DESCRIPTION OF Change | Car No | Change made by |
| 1 | 15-05-04 | 1.0 | All | First Release | NA | Jyothi.K |
| 2 | 21-06-04 | 1.1 | Revision History 6 5.4, 5.2.6.3 | All cells are filled in the Revision History. Added Version Number. Project initiation Document is changed to Project Charter New document names added | Internal Audit Observation | Jyothi.K |
| 3 | 20-08-04 | 1.2 | Page-1 5.2.1.3 5.2.10.2 5.2.12.6 5.2.3.9 5.2.7 | Version number changed Added Marketing Revised Object Release Criteria Added few lines in END PES Meeting Re-review 0f FS & TS during code-review added Sub headings added | Error identified Improvement Improvement Improvement Improvement Improvement | Jyothi.K Jyothi.K Jyothi.K Jyothi.K Jyothi.K Jyothi.K |
| 4 | 10-11-04 | 1.3 | 1, 2, 5 & 6 5.2.1.1 | Revised to include the process for Application Support & Upgrades. Handover from Marketing & Project Initiation added | Improvement Improvement | Jyothi.K Jyothi.K |
| 5 | 01-01-06 | 1.4 | 3 5 & 6 | Quality Manual, Training & SEPG Procedures are added Process Asset references are updated. Quality Assurance Section added. Defect logging & Document Approval revised. Sentences restructured. Outputs updated | Error identified Improvement | Jyothi.K |
CONTENTS
1.......... PURPOSE..........................................................................................................................................................................
2.......... APPLICABILITY...............................................................................................................................................................
3.......... REFERENCES....................................................................................................................................................................
4.......... RESPONSIBILITY.............................................................................................................................................................
5.......... PROCEDURE.....................................................................................................................................................................
5.1....... INPUTS.............................................................................................................................................................................
5.2....... PROCESS STEPS.............................................................................................................................................................
5.2.1.... PROJECT PREPARATION.................................................................................................................................................. 4
5.2.2.... BUSINESS BLUE PRINT..................................................................................................................................................... 7
5.2.3.... Realization.................................................................................................................................................................... 8
5.2.4.... Final Preparation...................................................................................................................................................... 13
5.2.5.... Go-Live & POST GO-LIVE Support............................................................................................................................. 14
5.2.6.... APPLICATION MANAGEMENT Support (AMS)............................................................................................................. 14
5.2.7.... Project Monitoring & Control.............................................................................................................................. 16
5.2.8.... Requirement Change Management........................................................................................................................ 18
5.2.9.... Review Procedure...................................................................................................................................................... 18
5.2.10.. TRAINING procedure................................................................................................................................................... 19
5.2.11.. Release Mechanism.................................................................................................................................................... 19
5.2.12.. quality assurance................................................................................................................................................... 19
5.2.13.. COMPLETION & ACCEPTANCE CRITERIA........................................................................................................................ 19
5.2.14.. Project Closure........................................................................................................................................................ 20
5.3....... Exit Criteria.................................................................................................................................................................. 21
5.4....... Output........................................................................................................................................................................... 21
5.5....... Measurements.............................................................................................................................................................. 22
5.6....... Verification.................................................................................................................................................................. 22
6.......... QUALITY RECORDS....................................................................................................................................................... 22
1 PURPOSE
The purpose of this document is to help the SAP team to understand the process to be followed for execution of the projects handled by them.
2 APPLICABILITY
This process is applicable to all domestic as well as foreign projects managed by SAP Implementation team, Upgrade team, Application Management Support team as well as Offshore ABAP development team.
3 REFERENCES
ASAP Methodology
Quality Manual
Procedure for Life Cycle Activities
Procedure for Project Planning
Procedure for Process Tailoring
Procedure for Reviews
Procedure for Quality Planning
Procedure for Acceptance
Procedure for Configuration Management
Procedure for Testing
Procedure for Document & Data Control
Procedure for Project Organization
SAP_Training Procedure
SAP_SEPG Procedure
4 RESPONSIBILITY
Project Manager is responsible for the execution of the project. However, the responsibilities for different roles in detail are defined in the Project Organization & Staffing Document.
(Refer: SAP_ Project Organization Structure)
5 PROCEDURE
5.1 INPUTS
Request for Proposal
Estimation Work Sheet during contract phase
Contract or Customer Accepted Proposal or Purchase Order
Any other available inputs
5.2 PROCESS STEPS
5.2.1 PROJECT PREPARATION
5.2.1.1 PROJECT INITIATION
5.2.1.1.1 Handover from Marketing
After the receipt of the signed Contract / Purchase Order, the Marketing Manager along with SBU Head / Systems Manager and the Commercial Manager reviews it. The signed Contract along with the supporting documents if any is handed over to the Commercial Manager and a copy is forwarded to the Systems Manager for future reference.
5.2.1.1.2 Project Initiation
Systems Manager identifies the Project Manager & the Project Quality Manager and is formally communicated to them with a copy to SBU Head, Account Manager, SBU Quality Coordinators, HR Manager, System Administrator, Financial Controller, Technical Controller other stakeholders if any as per requirement or conducts a formal meeting with all stakeholders as required.
5.2.1.1.3 Project Charter Preparation:
Once the project is initiated, Project Manager (PM) reviews the Contract / Purchase Order and prepares the Project Charter. In case all the required information is not available in the Contract / Purchase Order, the same has to be clarified from the SBU Head, Customer or Account Manger. If the Contract / Purchase Order information is adequate enough to execute the project, Project Charter can be waived.
For Upgrade Projects, the Project Charter outlines the Upgrade Strategy.
(Refer: SAP_Project Charter)
5.2.1.1.4 Define Service Level Agreement (Applicable to AMS Projects)
Service Level Agreement (SLA) is defined & agreed with the customer. SLA can be waived depending on the type / requirement of the Customer. It can be maintained as annexure to Project Charter / Contract / Purchase Order also.
5.2.1.1.5 Project Charter / SLA Approval:
Project Charter / SLA is reviewed & approved by the Systems Manager. This may be shared & agreed with the Customer.
5.2.1.1.6 Project Standards and Procedure Preparation:
Project standards and procedures are defined, discussed with customer and finalized, to establish the basic standards and procedures for the project, such as, Project monitoring and status reporting, Meeting schedules for core team and extended project team, Overall project communication methods and processes, Project documentation. Unless there is any change from customer side, standards & document templates defined at this phase shall remain un-altered till the end of the project
5.2.1.2 PROJECT PLANNING
5.2.1.2.1 Project Plan Preparation
Effort estimation shall be done based on the inputs from the contract phase. Based on the scope of the project, estimation & the past experience, the team, H/W, S/W and infrastructure resources to start the project are identified.
The PM in consultation with the Project Quality Manager (PQM) prepares the Project Plan with all constituent plans like Quality Plan, Configuration Management Plan, Risk Management Plan &Training Plan. Test Plan can be part of Project Plan or can be separately maintained.
For Upgrade Projects, the Project Plan comprehensively details the Upgrade Strategy.
Project Plan supported with Project Report, Project Organization Structure and Project Test Plan if applicable completes the project plan preparation.
(Ref: SAP_Offshore ABAP_Project Plan, SAP_Implementation_Project Plan, SAP_Upgrade_Project Plan & SAP_AMS_Project Plan, SAP_Implementation_Project Report, SAP_Project Report, SAP_Implementation Test Plan, SAP_Project Organization Structure , SAP_Implementation Delphi Estimation Sheet)
5.2.1.2.1.1 Quality Plan Preparation
Project Life Cycle activities are identified. Goals for the projects are set from the SBU level defined goals. (Ref: SAP_Goals). QA activities for the projects are identified from the Quality Assurance Table. The process is tailored to suit the project needs using the tailoring table. Deviations if any from the standard are addressed in the Quality Plan. Processes, methods & standards used in other projects are referred, discussed & adopted if found suitable. List of documents & Project Quality Records are identified. Project Standards, Document Formats & numbering are decided.
(Ref: SAP_Reference Documents)
5.2.1.2.1.2 Project Definition
The Project Plan outlines scope, objectives, deliverables, phases/milestones, project organization, staffing, hardware, software required, project management methodology, assumptions, dependencies, constraints etc. Based on the schedule of deliverables, a detailed schedule of tasks is prepared for the whole project or for phases or for specific milestone / deliverable. Responsibilities of Client as well as SISL are clearly identified and reflected in the Project Plan.
In case of Offshore ABAP projects and Application Management Support, there could be multiple objects for each project. The detailed schedule shall be created for each object at the time of its receipt.
5.2.1.2.1.3 Configuration Management Plan Preparation
Configuration Management Plan defines the Configuration Management activities planned for the project. Configurable items are identified. Baseline criteria, responsibility for identified CM activities etc. are defined. Configuration Audits are planned.. Project directory structure is defined to maintain all the Project Documents / Quality Records.
(Refer: SAP_Reference Documents)
5.2.1.2.1.4 Risk Management Plan Preparation
The estimation, schedules, resource requirements and development environment identified at the time of proposal are validated and the new risks are identified. Risk Management Plan is prepared for the project.
Risk escalation Level is identified for the projects as applicable.
(Ref: SAP_Risk Escalation Level Calculator Tool)
5.2.1.2.1.5 Training Plan Preparation
Training requirements for the team members are identified if any.
In case the member does not possess the required skill & the training can not be conducted due to practical reasons, training may be waived. In such cases, Waiver has to be approved by SM.
5.2.1.2.1.6 Test Plan Preparation
The goals, approach, schedule, start /stop criteria, test environment etc. are identified in the Test Plan. For offshore ABAP projects, only Unit test Plan is applicable & it is combined with the project plan where as for Implementation Projects, a separate Test Plan is prepared by Project Manager / Functional Team Lead with detailed planning for Unit / Baseline & Integration testing. Unit test responsibilities are identified along with test specification.
5.2.1.2.1.7 Project Monitoring & Tracking Mechanism
Project Status Reporting & Review Frame work, Escalation Methodology, Handover procedures, Issue Resolution Procedure etc. are defined in the Project Plan.
5.2.1.2.2 Project Plan Review & Approval
Draft Project Plan along with Project Organization Structure, Project Report and Test Plan as applicable is forwarded to the review team for review as defined in the Project Plan. Usually Walkthrough is conducted & the observations are documented, Project Plan Review Checklist may be used for reference.
Closure of review findings is verified by PQM. Project Plan is approved by SM & Technical controller (TC). The same is released as version 1.0. This is uploaded in the Livelink or maintained in the Project directory. This is made available to the team for reference. This Project Plan acts as the basis for further Project Management activities throughout the life cycle of the project.
Project Plan can be updated as per the requirement. But changes to the Project Plan will be through the controlled manner. The same review procedure needs to be followed for all major revisions if suggested by SM / TC. Else review by PQM to be ensured.
5.2.1.3 START PES MEETING
Start PES Meeting is scheduled either after the formal approval of the Project Charter / Project Plan or when a draft Project Charter / Project Plan is ready depending on the nature of the project. Invitation for start PES meeting is forwarded to the targeted participants defined in the Project Plan, by the Project Manager. Representatives of Marketing, Finance, Admin, Human Resources as well as SM, PQM, TC, SBU Quality coordinators and System Administrator along with the project resource identified can participate in the meeting as per the requirement. SBU Head also may be invited in the meeting as per the requirement. Start PES Meeting is conducted. Project Charter / Project Plan is presented in the meeting. Commitments are taken from the support team. Internal go ahead for the project is decided. PES Decision Sheet is circulated to all participants. PES Decision Checklist may be used for ensuring smooth coordination.
(Ref: SAP_PES Decision Sheet,)
5.2.1.4 PROJECT KICK OFF
Project start is formally announced by the SM to the team as well as the customer. The minutes shall be prepared by the PM and circulated. Alternately the PM can forward an e-mail to announce the project start. Depending on the type of the project, kick off meeting can be conducted prior to the start PES meeting also.
(Ref: SAP_Minutes of Meeting).
5.2.2 BUSINESS BLUE PRINT
5.2.2.1 BUSINESS BLUE PRINT PREPARATION
(Applicable for Implementation and Upgrade Projects)
In this phase the Business Blueprint is created, which is a detailed documentation of the results gathered during requirements study. Business Blueprint documents the business process requirements of the company. On this basis, a common understanding of how the company intends to run its business within the SAP System is achieved. Similar Project documents are referred from the repository and reused as applicable. Blue print is prepared by the Project Team Member (Functional Consultants).
The Business Blue Print contains, Business Process Master List, Business Process Questions (From Q.A. Database of ASAP), and Customer Input Template (C.I.Template). Questions are taken from Q&A DB provided by ASAP. The decision to include answers to process related questions from the Q&A database for reference shall be project specific.
For Upgrade Projects, wherever a new Business Process is introduced or an existing Business Process is changed, Business Blueprint should be prepared.
(Ref: SAP_Implementation_Blue Print)
5.2.2.2 BUSINESS BLUE PRINT REVIEW & APPROVAL
(Applicable for Implementation and Upgrade Projects)
Blueprint is reviewed by the nominated team identified for the review in the Project Plan. The review findings are closed. Closure of review findings is verified. Blueprint is approved (Sign-off) by the PM and the customer & is released as version 1.0. Reviewed document and the review documents are uploaded in the Livelink or maintained in the Project directory. This is made available to the team for reference. This Blue Print acts as the basis for further engineering activities throughout the life cycle of the project. Changes to the same shall be through controlled manner.
For Upgrade Projects, wherever a new Business Process is introduced or an existing Business Process is changed, Business Blueprint should be reviewed.
(Ref: SAP_Review Report).
5.2.2.3 PREPARATION OF CUSTOMER ABAP OBJECT LIST
(Applicable to Upgrade Projects)
Custom developed ABAP objects are identified by the ABAP Team Lead and the decision of which ABAP objects to retain in the new Release is made by the Customer. The ABAP objects and the decision of the Customer are recorded in the Customer ABAP Object List. ABAP Object List is uploaded in the Livelink or maintained in the Project directory.
5.2.2.4 REVIEW CUSTOMER ABAP OBJECT LIST
(Applicable to Upgrade Projects)
Customer ABAP Object List is reviewed by the nominated team identified for the review in the Project Plan and is signed off by Customer. Customer ABAP Object List and the review document is uploaded in the Livelink or maintained in the Project directory.
(Ref: SAP_ Review Report)
5.2.2.5 TECHNICAL UPGRADE OF DEVELOPMENT SYSTEM
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
A Target Release System Landscape is created by upgrading either a homogeneous copy of the Source Release Development System or the Source Release Development System itself, based on the Upgrade Strategy defined in the Project Plan. The Upgrade is performed using the SAP Upgrade Tool R3UP. Technical Upgrade Document is prepared by the Basis Team Member and is uploaded in the Livelink or maintained in the Project Directory.
(Refer: SAP_Upgrade_Document)
5.2.2.6 REVIEW OF THE TECHNICAL UPGRADE OF DEVELOPMENT SYSTEM
(Applicable to Upgrade Projects)
Technical Upgrade Document for the Development System is reviewed by the nominated team identified for the review in the Project Plan and are signed off by Customer and is uploaded in the Livelink or maintained in the Project directory.
5.2.2.7 IDENTIFICATION OF ADJUSTMENTS TO SAP STANDARD OBJECTS
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
Adjustments to SAP Standard Objects modified in the Customer’s System Landscape are identified using transaction codes SPDD and SPAU (during the Technical Upgrade) by the Basis Project Team Member (TM). The SPDD / SPAU Object Lists are uploaded in the Livelink or maintained in the Project directory.
5.2.2.8 REVIEW OF SPDD / SPAU OBJECT LISTS
(Applicable to Upgrade Projects)
The SPDD/SPAU Object Lists are reviewed by the nominated team identified for the review in the Project Plan and are signed off by Customer. SPDD / SPAU Object Lists and the review documents are uploaded in the Livelink or maintained in the Project directory.
(Ref: SAP_Review Report).
5.2.3 Realization
In this phase business and process requirements are implemented 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
Configure the system in two work packages, Baseline (major scope), and Final (remaining scope such as enhancements). This lets the team work on the other work packages after Baseline confirmation.
5.2.3.1 OBJECT CREATION
The development requirement is identified as an object for development, by the Team Lead (Functional Consultants) / On site coordinator.
For SAP Implementation projects, Effort Estimation is revisited and fine tuned if required depending on the quantum of development requirements. Test Plan is also revisited & schedules are updated. Project Plan is revised if required.
5.2.3.2 FUNCTIONAL SPECIFICATION PREPARATION
Functional Specifications are created with business process details, the changes required and the desired result by the Team Member (Functional Consultants) / Onsite Coordinator (OC). Similar projects are referred from the repository. Reusable objects and documentation are identified. Functional Specifications are generated in co-ordination with the respective Consultant of the customer. Completed FS is uploaded in the Livelink or maintained in the project directory. FS is sent to ABAP Team Lead for review and analysis.
(Ref: SAP_ABAP_Functional Specification).
For Upgrade Projects, Functional Specifications are prepared for adjustments to source code based on the SPDD/SPAU Object Lists and Customer ABAP Object List.
5.2.3.3 FUNCTIONAL SPECIFICATION REVIEW
Functional specifications shall be reviewed by the nominated team identified for the review in the Project Plan and if there are any questions, clarifications are taken from the Onsite coordinator / Functional Consultant. The reviewed functional specification is signed off for development by Team Lead (ABAP). Reviewed Functional specification is sent to the ABAP Team Member (TM) for the preparation of Technical Specification preparation. Reviewed document and the review documents are uploaded in the Livelink or maintained in the Project directory. SAP_ABAP_Functional Specification Review Checklist may be used to ensure complete review.
(Ref: SAP_Review Report)
5.2.3.4 ESTIMATION
(Applicable for Offshore ABAP and AMS Projects)
The reviewed FS forms the basis for the effort estimation for each object. The effort required to complete the object is calculated by the ABAP Team Lead (TL) using the Delphi method.
(Refer: SAP_ Delphi Estimation Sheet)
5.2.3.5 ESTIMATION REVIEW
(Applicable for Offshore ABAP and AMS Projects)
The estimation is reviewed by the nominated team identified for the review in the Project Plan. The reviewed estimation is informed to the customer. In case the customer has given the estimation and the same is different from the internally calculated estimation, the estimation is negotiated with the customer and an agreed effort is arrived at. Effort estimation is uploaded in Livelink or maintained in the project directory
5.2.3.6 TECHNICAL SPECIFICATIONS PREPARATION
After the approval of effort estimation, the ABAP Team Member will develop Technical Specification based on the Functional Specification. Clarifications at this level will be sorted out with the ABAP Team Lead. Technical Specifications are uploaded into Livelink or maintained in the Project directory.
(Ref: Technical Specifications for different type of objects e.g. SAP_ABAP_Technical Specification_BAPI)
For Upgrade Projects, Technical Specifications are prepared for adjustments to source code based on the SPDD/SPAU Object Lists and the Customer ABAP Object List.
5.2.3.7 TECHNICAL SPECIFICATIONS REVIEW
Technical Specification is reviewed by the nominated team identified for the review in the Project Plan. The reviewed Technical Specification is signed off for development by On site Coordinator / Customer / Functional Consultant. Reviewed document and the review documents are uploaded in the Livelink or maintained in the Project directory. SAP_ABAP_Technical Specification Review Checklist may be used to ensure complete review.
(Ref: SAP_Review Report)
5.2.3.8 ADJUSTMENTS TO SAP STANDARD OBJECTS
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
Adjustments to SAP Standard Objects based on the signed off SPDD/SPAU Object Lists and appropriate FS and TS are performed using transaction codes SPDD and SPAU (during the Technical Upgrade of the Development System) by the Basis Project Team Member and the ABAP Project Team Member (TM). SAP Change Requests for the SPDD/SPAU adjustments are created, released, exported and collected for binding in the subsequent Technical Upgrades.
5.2.3.9 REVIEW OF ADJUSTMENTS TO SAP STANDARD OBJECTS
(Applicable to Upgrade Projects)
Adjustments to the SAP Standard Objects based on the signed off SPDD / SPAU Object Lists and appropriate FS and TS are reviewed by the nominated team identified for the review in the Project Plan. The corresponding Code Review documents are uploaded in the Livelink or maintained in the Project directory.
(Ref: SAP_ABAP_Review Report).
5.2.3.10 CODING
The ABAP Project Team Member (PT) shall complete Coding based on FS & TS. Agreed Development Standards are used for the Development.
(Ref: SAP_ABAP_R3_Development Standard)
For Upgrade Projects, adjustments to source code based on the Customer ABAP Object List are completed by the ABAP Project Team Member based on FS and TS.
5.2.3.11 CODE REVIEW
Code review is done by the nominated team identified for the review in the Project Plan to ensure that the code is in line with the agreed programming guidelines and conforms to signed off FS & TS. FS & TS are again reviewed to ensure that all the changes suggested by the customer after the initial reviews are incorporated so that FS, TS & Code are in synchronization. Review documents are uploaded in the Livelink or maintained in the Project directory under baseline folder. Code Review Checklists for different types of objects may be used to ensure complete review.
(Ref: SAP_ Review Report)
For Upgrade Projects, code review of adjustments to source code based on the Customer ABAP Object List is limited to the actual adjustments performed.
5.2.3.12 UNIT/BASELINE TEST SPECIFICATIONS
Unit / Baseline Test specifications are developed by the Project Team Member (PT) to achieve actual result required by the customer. In the specifications all the combinations of the testing is checked to suit the requirement of the end customer. Test specifications are uploaded into Livelink or maintained in the Project directory.
(Refer: SAP_ABAP_Unit Test Specification & Result / SAP_Implementation_Test Specification & Result)
5.2.3.13 UNIT / BASELINE TEST SPECIFICATIONS REVIEW:
Unit / Baseline test specifications are reviewed by the Project Quality Manager (PQM) and Team Lead (TL) / PM. Reviewed document & review documents are uploaded in the Livelink / maintained in the Project directory. Test Specification Review Checklist may be used to ensure complete review.
(Refer: SAP_Review Report)
5.2.3.14 UNIT / BASELINE TESTING
Project Team member (TM) does the unit / Baseline testing with the help of test specification. Test results are updated in the Test Specification & Result
(Refer: SAP_ABAP_Unit Test Specification & Result, SAP_ABAP_Test Details & Error Log; SAP_Implementation_Test Specification & Result)
5.2.3.15 UNIT/ BASELINE TEST RESULT REVIEW
Test results are reviewed by the nominated team identified for the review in the Project Plan. Test result is uploaded into Livelink or maintained in the Project directory.
5.2.3.16 PROGRAM DOCUMENTATION
Program documentation is prepared by the Project Team Member (PT). Program Documentation is uploaded into Livelink or maintained in the Project directory.
(Ref: SAP_ABAP_Program Documentation)
5.2.3.17 PROGRAM DOCUMENTATION REVIEW:
Program Documentation is reviewed by the nominated team identified for the review in the Project Plan. Reviewed document & review documents are uploaded in the Livelink or maintained in the Project directory.
(Ref: SAP_ Review Report)
5.2.3.18 OBJECT RELEASE
The Team Lead releases the object to the Customer / Functional Consultant for carrying out any additional testing.
5.2.3.19 TECHNICAL UPGRADE OF QUALITY AND / OR TEST SYSTEMS
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
Target Release Quality and / or Test Systems are created by upgrading either a homogeneous copy of the Source Release Quality and / or Test Systems (if any) or the Source Release Quality and / or Test Systems themselves (if any), based on the Upgrade Strategy defined in the Project Plan. The Upgrade is performed using the SAP Upgrade Tool R3UP. SAP Change Requests for the SPDD / SPAU adjustments done during the Development Upgrade are bound into the Technical Upgrade. Technical Upgrade Document is prepared by the Basis Team Member and is uploaded in the Livelink or maintained in the Project Directory.
(Refer: SAP_Upgrade_Document)
5.2.3.20 REVIEW OF THE TECHNICAL UPGRADE OF QUALITY AND/OR TEST SYSTEMS
(Applicable to Upgrade Projects)
Technical Upgrade Document for Quality and/or Test Systems is reviewed by the nominated team identified for the review in the Project Plan. The reviewed document is signed off by Customer and is uploaded in the Livelink or maintained in the Project directory.
5.2.3.21 MIGRATION TO QUALITY ENVIRONMENT
Master Data templates are prepared (these are project specific) to collect the data for migrating into the Quality environment. Quality environment is set up. Customizations as well as developments are transported from Development system to Quality system. Quality testing Data is migrated to Quality environment.
5.2.3.22 INTEGRATION TEST SPECIFICATION PREPARATION
(Applicable to Implementation and Upgrade Projects)
Integration test specifications and test scenarios are prepared by the customer with the help of Functional Consultant. These are uploaded into Livelink or maintained in the Project directory.
(Refer: SAP_Implementation_Test Specification & Result)
5.2.3.23 INTEGRATION TEST SPECIFICATION REVIEW
(Applicable to Implementation and Upgrade Projects)
Integration test specifications and test scenarios are reviewed by the nominated team identified for the review in the Project Plan. Reviewed document & review documents are uploaded in the Livelink or maintained in the Project directory. Test Specification Review Checklist may be used to ensure complete review.
(Refer: SAP_Review Report)
5.2.3.24 INTEGRATION TESTING
(Applicable to Implementation and Upgrade Projects)
Functional Team Lead does the Integration testing with help of test specification. Test results are updated in the Integration Test Specification & Results
(Refer: SAP_Implementation_ Test Specification & Result)
5.2.3.25 INTEGRATION TEST RESULTS REVIEW
(Applicable to Implementation and Upgrade Projects)
Issues / Defects observed are listed and resolved by the assigned person. The closure is verified by the PQM. Test results are reviewed by the nominated team identified for the review in the Project Plan. Test results are signed off by the PM & Customer. Test result is uploaded into Livelink or maintained in the Project directory.
(Refer: SAP_Implementation_Test specification& Result)
5.2.3.26 SYSTEM ACCEPTANCE
(Applicable to Implementation and Upgrade Projects)
Realization phase is signed off at the completion of Integration Testing and system is accepted.
5.2.4 Final Preparation
(Applicable to Implementation and Upgrade Projects)
In this phase the final preparation (including testing, end user training, system management and cut-over activities) is completed, to finalize customer’s readiness to go live. The Final Preparation phase also serves to resolve all crucial open issues. On successful completion of this phase, customer is ready to run business in Live SAP system.
Production environment is set up. All the developments as well as configuration are transported to Production environment. Customization Document is prepared. Cutover to Production System is planned & performed.
(Ref: SAP_Customization Document)
Sign off on Go Live of project is obtained at the end of this phase.
5.2.4.1 IDENTIFICATION OF CHANGES FOR SYNCHRONIZATION
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
Changes are identified between the Source Release System Landscape and Target Release System Landscape for Synchronization by the Basis Team Member with the help of the customer. The List of Changes is generated and signed off by the Customer. Synchronization List of programs is uploaded in the Livelink or maintained in the Project directory.
5.2.4.2 REVIEW OF LIST OF CHANGES IDENTIFIED FOR SYNCHRONIZATION
(Applicable to Upgrade Projects)
Synchronization program List is reviewed by the nominated team identified for the review in the Project Plan. The reviewed document is signed off by Customer. Reviewed document and the review documents are uploaded in the Livelink or maintained in the Project directory.
(Ref: SAP_ Review Report)
5.2.4.3 TECHNICAL UPGRADE OF PRODUCTION SYSTEM
(Applicable to Upgrade Projects based on the Upgrade Strategy defined in the Project Plan)
After the System Acceptance from the customer, Target Release Production System is created by upgrading either a homogeneous copy of the Source Release Production System or the Source Release Production System itself, based on the Upgrade Strategy defined in the Project Plan. The Upgrade is performed using the SAP Upgrade Tool R3UP. SAP Change Requests for the SPDD/SPAU adjustments done during the Development Upgrade and tested in the Quality Assurance System are bound into the Technical Upgrade. Technical Upgrade Document is prepared by the Basis Team Member and is uploaded in the Livelink or maintained in the Project Directory.
(Refer: SAP_Upgrade_Document)
5.2.4.4 REVIEW OF THE TECHNICAL UPGRADE OF PRODUCTION SYSTEM
(Applicable to Upgrade Projects)
Technical Upgrade Document for Production System is reviewed by the nominated team identified for the review in the Project Plan. The review document is signed off by Customer and is uploaded in the Livelink or maintained in the Project directory.
5.2.4.5 SYNCHRONIZATION OF CHANGES
(Applicable to Upgrade Projects)
All Changes carried out in the Realization Phase and recorded in SAP Change Requests are merged in a Transport of Copies and delivered to the Production System by the Basis Team Member and the Transport Document is generated.
5.2.5 Go-Live & POST GO-LIVE Support
(Applicable to Implementation, Offshore ABAP & Upgrade Projects)
In this phase after moving to live production operation from a pre-production environment, support is given to end users in the initial phase of production operations.
At the end of this phase Offshore ABAP / Implementation / Upgrades project is closed.
(Refer Section: Project Closure)
5.2.6 APPLICATION MANAGEMENT Support (AMS)
(Applicable to AMS Projects)
In this phase after end of “GO-LIVE AND POST GO-LIVE SUPPORT”, support is given to end users for production operations enhancements and bug fixing.
The following major activities are carried out in the Application Support phase.
5.2.6.1 KNOWLEDGE TRANSFER & HANDHOLDING
If implementation is done by SISL then respective ‘Implementation Project’ documents are referred to from Live Link, else customer is asked to provide the necessary documents for future reference.
This activity may be done during the Project Preparation phase also.
5.2.6.2 RECEIVING MAINTENANCE REQUESTS
Maintenance Requests (MR’s) are communicated by the customer to the SISL Helpdesk via email, Fax or over telephone. Helpdesk support is an email ID created specifically to capture customer requests.
Alternately maintenance requests are entered by the customer in a call management tool (Remedy) through internet.
5.2.6.3 LOGGING OF MAINTENANCE REQUESTS
When the Maintenance Requests are received through E-mail, telephone or Fax, the Helpdesk agent manually enters the details of request in the call management tool (Remedy). The system generates unique identification code for every Maintenance Request created (MR’s) in the system.
The call management tool is internet enabled and can also receive MR’s directly initiated by customer if they intend to use internet interface.
5.2.6.4 MAINTENANCE REQUEST ACKNOWLEDGEMENT
An acknowledge mail is sent to the customer informing about the receipt of MR with unique maintenance request identification number.
5.2.6.5 MAINTENANCE REQUEST ASSIGNMENT
Maintenance Request is assigned to a Team Lead by Helpdesk through Remedy. The Status of MR is changed from “New” to “Assigned”. Response time will be calculated based on the “New” to “Assigned” status change. A mail will be sent to the respective Module Lead who is assigned to the problem & Project Manager for information and future follow ups.
5.2.6.6 MAINTENANCE REQUEST ANALYSIS
Team Lead / Team Member verify whether the Maintenance request is within the scope of the Contract. The request is categorized primarily to “Incident” or “Change”.
Change Requests - Any Configuration changes, modifications to existing ABAP objects as well as new functionality developments & new object developments.
Minor Configuration Changes & modifications to existing objects are part of incident management process where as any new functionality development or object development will be considered under change management process.
Incident – All MR’s other than Change Requests which refer to new functionality developments or object development.
MR’s are categorized as,
L1: Simple Query
L2: Master Data Change
L3: Customizing or ABAP Development
L4: OSS
The Module lead after analysis of the MR’s, re assigns them to one of the team members.
In case of Incidents, remedy is used to keep log of communication, suggestion made, solution provided etc. In case of change requests which fall under change management process, the Team Lead analyzes the Request and effort required to resolve the Request is calculated using the Delphi Estimation method. This is reviewed by the PM & communicated to the Customer for his approval. (Refer: SAP_ Delphi Estimation Sheet). In case of Change Requests, approval is taken from SM.
5.2.6.7 MAINTENANCE REQUEST RESOLUTION
Based on the priority of the MR, Team Member changes the status of the issue in Remedy to ‘Work in progress’ & carries out the appropriate actions to resolve the MR.
During resolution if additional information from the customer is required, Consultants use Remedy and its interface with mail to communicate with the customer. During the period when information is expected from the customer, the status of the MR is changed to ‘Pending’
In case of change requests categorized as Incidents, the changes would be updated in Remedy with a reference to the test document.
For change requests having configuration changes, following documents would be maintained: FS, Test Plan, Test results & Customization Document shall be maintained. (Ref: SAP_Customization Document). Review of these documents is carried out by the PM & the reviewed documents & review documents are uploaded in Livelink or maintained in the directory structure.
For new developments, all steps applicable for Offshore ABAP projects from Object Creation till the Object Release shall be followed.
Start and End date of resolution, Total Resolution time (in hrs), etc. are captured in Remedy.
After successful Resolution, the consultant changes the status of the MR to ‘Resolved’ and makes his comments in the system. Thus, user is intimated by E-mail through Remedy, about the resolution of the issue. The solution provided & the documents are to be referred are also communicated to the Customer.
5.2.6.8 MAINTENANCE REQUEST CLOSURE
Customer on approval of solution provided shall send E-mail to Helpdesk about the acceptance and thus the help desk shall formally close the Maintenance Request.
In case the customer fails to respond by the predefined time period, the PM shall deem the MR as closed and an email to that effect shall be sent to the customer. The status of the MR will be updated as “Closed” in the Remedy Tool by the Team Member.
In case the customer is not satisfied with the solution provided during the pre-defined period, the case can be re-opened.
On receipt of the failed resolution, the MR will be reopened and assigned to the Team Member and the same cycle is followed.
Calculation of resolution time is based on the time lapsed between the “Assigned” to “Resolved” status.
5.2.7 Project Monitoring & Control
5.2.7.1 MONITOR PROJECT PLANNING
Project plan is maintained on ongoing basis. On completion of Business Blue Print / Functional Specification and subsequently on review of project progress / on a periodic basis, the project plan is validated. The Project Manager reassesses the estimated size, effort and schedule.
Issues related to technical, quality, infrastructure, manpower, customer, finance etc. if any are escalated as defined in the Project Plan.
5.2.7.2 MONITOR COMMITMENTS
As part of their routine, the Team Members maintain time sheets on a daily basis. This is monitored by the respective Team Lead for ascertaining daily progress and status of the jobs assigned to the team members.
Project team meetings are conducted as per the frequency defined in the project plan to review the progress of the work. Minutes of the meetings are prepared.
(Ref: SAP_Minutes of Meeting)
Periodical or need base meetings with customer if any are conducted and the minutes of the meetings are circulated. These meetings may be through telecon / video conference etc.
(Refer: SAP_Minutes of Meeting)
The PM conducts the project status review meetings with team members and PQM as per the frequency defined in the Project Plan. SM and TC also may participate in the meeting as per the requirement. The proceedings are recorded. Phase end review meetings can be combined with the periodic status review meeting.
(Ref: SAP_Project Report)
In case of scheduled deviations or effort deviations beyond the planned limit or any major issues, the issues are discussed in greater details and arrive at corrective & preventive actions for the project to proceed in the right direction. The Project Manager will follow up, whether the corrective & preventive actions arrived at is actually implemented.
In case of anticipated delays or effort overruns, the level of reporting may be increased as per the escalation procedure outlined in the Project Plan. The Project Plan may be revised accordingly after approval from SM.
Statuses of risks identified are evaluated & further mitigation and contingency plans are discussed.
Commitments from support groups are monitored & corrective actions are initiated as necessary. Additional support if required is requested. Approved changes to the commitments are communicated to the team during the review meetings
Customer complaints if any are addressed. Customer feedback if any received for the period is analyzed.
5.2.7.3 MONITOR QUANTITATIVE DATA MANAGEMENT
The Project Manager updates the Metrics in the Project Report on a monthly basis and the variance is analyzed during the Project status review.
The Project Quality Manager reviews the Project Report and the corrective & preventive actions are suggested based on the analysis on the variances / trend / information. This is forwarded to TC & SM for further analysis & escalation / approval on different issues. This forms an input to the monthly Status Review Meeting.
(Ref: SAP_Project Report, SAP_Project Implementation Report)
5.2.7.4 STATUS REPORTING
The PM- may use tools such as MS-Project, Spreadsheet and / or any other specially designed formats for monitoring the progress of the project.
The report is based on the actual progress of the project with respect to deliveries made, work completed, resources utilization, training, quality, risks, issues pending resolution and new issues / concerns including customer complaints.
The Project Manager updates these parameters in the Project Report on a monthly basis and forwarded to PQM for review. The Project Quality Manager reviews the Project Report and the corrective & preventive actions are suggested based on the analysis on the variances / trend / information. This is forwarded to TC & SM for further analysis & escalation / approval on different issues. This forms an input to the monthly Status Review Meeting. The Project Status can be forwarded to the client as applicable.
(Ref: SAP_Project Report, SAP_Project Implementation Report)
5.2.7.5 PROJECT HANDOVER
Any team member including the PM, leaving the Project permanent or temporary should hand over the documents & other details of the project in a controlled manner.
(Ref: SAP_Responsibility Transfer Format)
5.2.8 Requirement Change Management
5.2.8.1 REQUIREMENT TRACKING
(Applicable to Implementation, Offshore ABAP Projects, Upgrade Projects in case of Functional Upgrade, Application Management Support Projects in case of New Developments)
Requirements are tracked through out the Life cycle of the project with the help of Traceability Matrix updated by project team and reviewed and controlled by Team Lead. This is updated in the monthly Project Report.
Changes if any to the requirement after the integration testing are treated as change requests. Change Requests internal as well as external shall be communicated through e-mail / Livelink. For external originated changes, On site coordinator / customer forwards the change requests to Project Manager / Team Lead. For internal originated changes, the originator forwards the change request to the Project Manager (PM) / Team Lead (TL).
(Ref: SAP_Project Report, SAP_Implementation_Project Report)
5.2.8.2 CHANGE CONTROL
(Applicable to Implementation & Offshore ABAP Projects)
Change requests are analyzed by the nominated team identified for the same in the Project Plan. Impacted items and the effort required to do the change are identified. Change Control Log is updated. Based on the Project Manager’s / Team Lead’s approval / remarks on the Change Control Log, the Project Team Member (PT) carries out the change. The details are updated in the Change Control Log. This is updated in the monthly Project Report.
(Ref: SAP_Project Report, SAP_Implementation_Project Report)
5.2.8.3 CONFIGURATION AUDITS
Configuration Audits are conducted as per the periodic frequency identified in the project plan to ensure the configuration & change management activities. The findings are documented in the monthly Project Report and are tracked to closure through Problem, Issue & Open Points in the Project Report. Configuration Audit Checklist may be used to ensure complete audit. Basis Checklist may be used to audit the basis related activities.
(Ref: SAP_Project Report, SAP_Implementation_Project Report)
5.2.9 Review Procedure
5.2.9.1 REVIEW
Project Manager identifies the work products to be reviewed in the project plan. It includes choosing the appropriate peer review technique, resource allocation, approval authority etc. Depending on the type of the review, review materials may be distributed to the reviewers in advance so they can adequately prepare for the peer review. Checklists may be used to identify criteria for the review of the work products in a consistent manner. Reviewers examine the work product individually to detect defects. Minimum Required participants for the review meeting phase include the author, and reviewer. Moderator and recorder may be present if required. The same review procedure needs to be followed for all major revisions if suggested by SM / TC. Else review by PQM to be ensured.
5.2.9.2 DEFECT LOGGING & CLOSURE
Defects and issues affecting the work product are discussed in the review meeting to attain common understanding except in offline review. In offline review the review is independently done by the reviewer. Review findings are marked as track changes or entered in the review report sheet maintained in the Project report as applicable. For technical deliverables, reviewers classify each defect detected into major & minor and document any issues regarding the work product / suggestions in the Review Report. The Author of the product corrects all the defects identified & agreed in the review. Suggestions may be incorporated as appropriate. PQM / Reviewer verify that the defects are closed.
(Ref: SAP_Project Report, SAP_Implementation_Project Report)
5.2.10 TRAINING procedure
Trainings within SBU are coordinated by SBU Training Coordinator as defined in the Training Procedure.
(Ref: SAP_Training Procedure).
5.2.11 Release Mechanism
5.2.11.1 DOCUMENT APPROVAL & RELEASE
Documents are deemed to be approved after the closure of review observations are verified by PQM / Reviewer The document shall be uploaded in Livelink or maintained under directory structure after formal approval. Release of new documents will be communicated either in meetings or vide e-mail / phone. Access rights will be set in such a way that only latest documents will be available for use at any point of time for all concerned
In the case of Livelink, only the latest document can be fetched for use from Livelink. History of the obsolete documents is maintained in Livelink.
5.2.11.2 OBJECT RELEASE FOR OFFSHORE ABAP PROJECTS
The object is released internally to the Onsite Coordinator by ABAP Team Lead by setting the status as completed in Livelink and informing OC through Discussion Channel in Livelink. After performing the integration testing, OC releases the object to the customer by setting the status of the task Release or Delivery after User acceptance as completed.
5.2.12 quality assurance
PQM ensures the adherence to the Quality Assurance activities planned in the project. QMS non-compliance observed is reported in the monthly Project Report. Configuration Audits are conducted as planned & the findings are also reported in the monthly report.
Formal Process audits are ensured by PQM on a periodic basis / end of each phase./ before each internal audit. TC verifies the correctness of the process audit conducted by PQM
(Ref: SAP_Process_Audit_Checklist)
Internal / external audits are conducted as per the organizational level guidelines. Audit observations are tracked to closure through QMS Portal.
5.2.13 COMPLETION & ACCEPTANCE CRITERIA
For offshore ABAP Projects, the Project Completion & Acceptance criteria will be as follows unless specified otherwise by the customer:
The project will be considered as completed if
In an object based project: Each object will be considered as completed under the following cases- formal acceptance of the object by the customer or two weeks after the release of the object which ever comes earlier, unless otherwise specified in the contract by the customer or agreed in the Project Initiation Document.
In a timeline based project: If the timeline has expired.
After the completion of all objects, customer carries out the Integration testing. Any bugs in the program communicated to the offshore team are to be corrected by the Team Member. PM / Onsite Coordinator (OC) gets the final Acceptance / Sign off from the customer.
For Implementation & Upgrade Project, sign off of each phase will be considered as acceptance of that phase & sign off of all phases is considered as closure of the project.
For Application support projects, the project is considered to be closed at the end of the contract period.
5.2.14 Project Closure
5.2.14.1 RESOLVE OPEN ISSUES
The Project Manager shall ensure that the customer has agreed to conclude and close down the project. The customized solution is handed over to the client after the acceptance criteria have been met.
5.2.14.2 CUSTOMER FEEDBACK
The customer’s acceptance / sign off are received. A formal letter is forwarded to the customer to obtain the Customer Feedback.
The customer satisfaction is obtained on a scale of 1-6. The feedback received from the customer is analyzed by P & Q to recommend methods for improvement. These also form inputs to the Management Review Meeting.
Customer Feedbacks in any format are suggested to take during the course of the AMS Operations Project in view of ensuring good service to the customer. However it is mandatory to take once during the project lifecycle in the prescribed format.
(SAP_Customer Feedback)
5.2.14.3 COMPLETE PROJECT METRICATION
The Project Manager updates the Metrics in the Project Report at the end of the project and the variance is analyzed during the End PES Meeting.
The Project Quality Manager reviews the Project Report and the corrective & preventive actions are suggested based on the analysis on the variances / trend / information. This is forwarded to TC & SM for further analysis & escalation on different issues. This forms an input to the End PES Meeting.
(Ref: SAP_Project Report, SAP_Project Implementation Report)
5.2.14.4 ARCHIVE PROJECT AND DOCUMENTATION
The Project Manager transfers all the Project Quality Records, client communications, meeting minutes, etc. which may be considered necessary to retain in the long run to the Livelink / Repository. PM ensures that only read access is available for these documents. Retention period for these records will be as per the decisions taken by the SEPG.
5.2.14.5 RELEASE PROJECT RESOURCES
All equipment/s received from client for the project as specified in the project plan are disposed off / returned as the project plan. All leased equipment/s for the project as specified in the project plan are returned to supplier and receipts are solicited. The Project Manager identifies the required team members, on the basis of the requirements of the contract for maintenance / backup support of system developed, and releases the remaining staff from the project. Skills database(Resume) is updated for the project team members for the skills used on the project and same is validated by the Project Manager or SM.
5.2.14.6 ORGANIZE END PES
The Project Manager organizes the END PES meeting. Invitation for END PES meeting is forwarded to the targeted participants defined in the Project Plan, by the Project Manager. Representatives of Marketing, Finance, Admin, Human Resources as well as SM, PQM, TC, SBU Quality coordinators and System Administrator along with the project resource identified can participate in the meeting as per the requirement. SBU Head also may be invited in the meeting as per the requirement.
Lessons Learnt in the project is documented. Evaluation of success of project, Extent of customer satisfaction, Extent of conformity to standards / processes stated in project plan, and any deviations, Outstanding Issues, Accomplishments, Major Events influenced project progress / execution, Requirements, if any, for amendments to current Quality processes, Any other issues as felt appropriate by the Project Manager, Analysis report of project and process measures and metrics collected are discussed during the End PES meeting. Closure of the project is agreed. PES Decision Checklist may be used for ensuring smooth coordination.
(Ref: SAP_Lessons Learnt-Projects, SAP_PES Decision Sheet)
5.3 Exit Criteria
Acceptance / Sign Off from customer / Completion of Contract Period
5.4 Output
ABAP Specific Documents: Engineering documents for ABAP related work applicable to Offshore, SAP Implementation, Upgrades & Application Support
SAP_ABAP_Functional_Specification
SAP_ABAP_Technical_Specification_BAPI
SAP_ABAP_Technical_Specification_BDC
SAP_ABAP_Technical_Specification_Class
SAP_ABAP_Technical_Specification_CRM_HTML
SAP_ABAP_Technical_Specification_CRM_Landscape
SAP_ABAP_Technical_Specification_CRM_Scripts
SAP_ABAP_Technical_Specification_CRMIS
SAP_ABAP_Technical_Specification_Enhancements
SAP_ABAP_Technical_Specification_Function_Module
SAP_ABAP_Technical_Specification_IDOC_ALE_EDI
SAP_ABAP_Technical_Specification_Info_Types
SAP_ABAP_Technical_Specification_Layout
SAP_ABAP_Technical_Specification_Module_Pool
SAP_ABAP_Technical_Specification_Port_Defn
SAP_ABAP_Technical_Specification_Report_Painter
SAP_ABAP_Technical_Specification_Report
SAP_ABAP_Technical_Specification_Search
SAP_ABAP_Technical_Specification_Table_Views
SAP_ABAP_Technical_Specification_Workflow
SAP_ABAP_Code_Review_Checklist_ALE
SAP_ABAP_Code_Review_Checklist_BAPI
SAP_ABAP_Code_Review_Checklist_BDC
SAP_ABAP_Code_Review_Checklist_Business-Addins
SAP_ABAP_Code_Review_Checklist_Function_Module
SAP_ABAP_Code_Review_Checklist_Infotype
SAP_ABAP_Code_Review_Checklist_Layout
SAP_ABAP_Code_Review_Checklist_MODULE_POOL
SAP_ABAP_Code_Review_Checklist_Reports
SAP_ABAP_Code_Review_Checklist_User_Exits
SAP_ABAP_Program_Documentation
SAP_ABAP_Functional_Specification_Review_Checklist
SAP_ABAP_Technical_Specification_Review_Checklist
SAP_ABAP_Unit_Test_Specification_Result
SAP_ABAP_Test_Details_Error_Log
SAP_ABAP_R3_Development_Standard
SAP Common Documents: Common documents applicable for Offshore ABAP, SAP Implementation, Upgrades & Application Management Support
SAP_Goals
SAP_Project_Charter
SAP_Project_Organization_Structure
SAP_Customer_Feedback_Form
SAP_Customization Document
SAP_Reference Document
SAP_PES_Decision_Sheet
SAP_Minutes_Of_Meeting
SAP_Responsibility_Transfer_Format
SAP_Risk_Escalation_Level_Calculator_Tool
SAP_Lessons_Learnt_Projects
SAP_Test_Specification_Review_Checklist
SAP_Process_Audit_Checklist
SAP_Basis Activities Checklist
SAP Implementation Specific Documents: Documents specific to SAP Implementation / Upgrade projects where functional upgrade is under scope.
SAP_Implementation_Project_Plan
SAP_Implementation_Project _Report
SAP_Implementation_Blue_Print
SAP_Implementation_Project_Test_Plan
SAP_Implementation_Test_Specs _Result
SAP_Implementation_Delphi_Estimation_Sheet
SAP_Upgrade_Project_Plan
SAP_Upgrade Document
Offshore ABAP & Application Management Support Documents: Documents applicable for Offshore ABAP / Application Management Support
SAP_Project_Report
SAP_Offshore_ABAP_Project_Plan
SAP_Delphi_Estimation_Sheet
SAP_AMS_Project_Plan
5.5 Measurements
Schedule
Effort
Customer Satisfaction Index
5.6 Verification
Verification by SM/PQM/TC
Process Audits / Internal Audits / External Audits
6 QUALITY RECORDS
Estimation Sheet
Project Plan
Test Plan
Business Blue Print
Functional Specifications
Technical Specifications;
Test Specifications & Logs
Review Reports
Upgrade Documents
Customization Document
No comments:
Post a Comment