Beruflich Dokumente
Kultur Dokumente
October 2007
AcceleratedSAP Methodology
Description AcceleratedSAP methodology is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. AcceleratedSAP provides content, tools and expertise from thousands of successful implementations.
More info
http://service.sap.com/asap
AcceleratedSAP toolset
SAP Solution Composer SAP Roadmaps SAP Solution Manager
Phase 3: Realization
The purpose of this phase is to build & test the solution defined in the Business Blueprint. The system configuration is delivered in two groups: Baseline (core scope); and Final configuration (remaining scope). This is then followed by Integration Testing.
Realization
Final Preparation
1
Project Charter Project Plan Mgmt. Plans Project Team Org
Standards & Procedures
2
Solution Requirements
3
Solution Build
Developments Authorizations Portal
(Content, Structure, UI)
4
Cut Over Plan Technical Operations Manual
5
Solution Information & Support
Test Plans
(Unit, Scenario, & Integration Tests)
Test Execution
Technical
Requirements
Documents
& Design
SAP Solution Manager
Learning Maps
Key Deliverables
Project Charter
Project Budget Change Management Strategy
Milestones
Business case approved QA gate 1 successfully achieved Project kick-off Project Team Training completed Project Team On-boarding Project logistics finalized QA gate 2 successfully achieved
Blueprint Phase
Description
The purpose of this phase is to gather business requirements, understand any design gaps and determine how to resolve these. The result is the Business Blueprint, a detailed documentation of the business design for SAP.
Key Deliverables
Project Scope Document
Blueprint Design Document List of Development Objects Configuration Spreadsheets Functional Specifications for DEV objects To-Be System Landscape
Milestones
Completion of Design Workshops Sign-off Blueprint Design QA Gate 3 successfully achieved
Blueprint Approach
4 - 6 hours
2 - 3 days
1 2 hours
Core Team
Detailed Analysis
Working Sessions
Working Sessions
Present proposed Blueprint process to group.
Cover Bootcamp material Introduce key decisions required High-level Global Template review
Thorough walk thru of Global Template process; Deeper dive on Fit GAPS, etc.; Gain detailed understanding on Master Data, Processes & Configuration data
Final Review
Areas to be Completed
WOF Draft, Finalization & Distribution All Actions Items Closed All Deliverables Revised Playback Held
Realization Phase
Description
The purpose of this phase is to build & test the business requirements defined in the Business Blueprint.
Key Deliverables
Cutover Plan is finalized
Stress/Volume testing is completed Training Plan is finalized and Training material is prepared Integration testing is executed and results are signed off Organizational impacts have been analyzed and a plan developed to address issues
Milestones
Completion of Build sub-phase Completion of Integration Testing Completion of User Acceptance Testing
What is Realization?
Realization is a project phase that begins with the development of a detail design based on the requirements defined and approved in Blueprinting. As the detailed design is approved, it will be translated into software configuration and programs which will be unit, functional and integration tested. Complementary deliverables such as training courseware will be built. Major areas of work and deliverables are: Configuration, scripting (BPPs) and unit testing Development and testing of enhancements, interfaces, forms and reporting Developing and testing of data conversion programs Design and execution of functional testing Design and execution of integration testing
Design, configure and test end-user security roles and profiles Project communications and change readiness assessments Development of role based courseware
Build
1. Unit Test Global Template on local Dev in local language 2. Configure local processes in DEV 3. Development Objects created in Dev system 4. Unit test local design 5. Solution Manager project has been updated with all in scope scenarios, processes and steps 6. Build end-user security profiles 7. Create test scripts for local development/ configuration/ processes 8. Creation of all BPPs 9. All transports have been logged and identified for transport to QA environment 10. Project manager approval of transports to QA environment
Functional Test
1. Short Process Chains 2. Test performed at Process and Process Step level with Solution Manager Test Workbench 3. Timing of processes during functional test can help with test master data 4. User-exists, workflows, load programs and Security profiles have been unit tested in DEV 5. Testing performed in QA system 6. All transports from DEV to QA complete 7. Test data has been identified and loaded into the test client
Integration Test 1
Integration Test 3
1. User Acceptance Test 2. Site or Super users perform test locally 3. Stress test of network 4. Full volume production data load required for testing 5. End-user roles have been created and unit tested and are available in the QA environment 6. Production data has been converted to the QA test client 7. End-users have been properly trained for test execution (Basic Navigation, SAP specific training)
1. Value Chains (End to End 1. Integrated process/Test scenarios) have been finalized and loaded into Solution Manager Project 2. Synchronized with Solution Manager: Scenario within 2. Solution Manager= Value Chain process flow in ARIS 3. All interfaces ready for integration testing (on completion of Unit and Functional Test) 4. All functional tests have been 3. executed with 90% of test scripts passed and no major open issues related to testing remain 5. Integration testing scenario variations have been defined and scripts have been prepared 6. Integration Test plans are generated 7. Full data conversions completed more than once successfully
Key Deliverables
Milestones
Training complete Cutover simulation test executed Approval to begin cutover attained PRD Support model implemented QA Gate 5 successfully achieved
Key Deliverables
Go-Live achieved
Post-Implementation review completed
Milestones
Go-Live achieved Completion of 1st month-end close System stabilized and handed over to long-term support group QA Gate 6 successfully achieved
Each ASAP phase has Phase Start, Deliverable Creation/Acceptance and Closure tasks
Quality Gates
PMO QA Objectives
The PMO Quality Assurance process intends to measure and manage the status, risk and quality of SAP projects across AES consistently SAP implementation projects are high in complexity and are high risk for potential failure. The success of the AES program involves the identification and management of these implementation risks across all projects Detailed quality reviews for each project phase provides accurate information for making conscious decisions to timelines, scope and designs Confirmation of design at key project stages ensures that individual projects meet the original goals defined and the AES goals for improved financial controls and reporting The QA process will be proactive and performed during and at the start/end of each project phase. The QA process will provide information to the projects in a timely manner to make decisions in order to mitigate risk and be successful.
This is not a Quality Audit but a useful tool to make projects successful
PMO QA Approach
The approach uses gating criteria for entering and exiting phases of the SAP implementation projects Each gate will have different criteria based on the phase, e.g.:
Deliverables that need to be complete for this phase Pre-requisites for the next phase Open items or issue management
Projects will report progress against the ASAP methodology deliverables and the criteria specified for the gate on a weekly basis using the project reporting template To deliver the proactive approach, Gate Meetings will be scheduled prior AND on the scheduled time to pass through the gate Each Gate criteria will be judged to be Red or Yellow or Green (High Risk/ Manageable Risk/ Low Risk) Risk mitigation plans will be created and project resources can be focused appropriately for Red and Yellow criteria. Project Leadership Team (PLT) and Genesis Global PMO will agree on necessary changes to the project approach, as necessary, to mitigate the identified risk Key Gates will require the sign off of both local business sponsors and Global Business Owners to ensure the project is SOX compliant, delivering the solution stated in the business case/project charter and in the AES global project goals
Project Preparation
BluePrint
Realization
Final Prep
Support
The intent of a Gate is to measure the readiness of a project to start or end a phase of an implementation project
The status of the project when the project when passing through the gate will determine the project risk
The amount of project risk will determine if the project should continue to the next phase or continue and fix problems by extending a phase
Each Gate has been numbered and has its own criteria
Each SAP project will follow the same phases and will pass through the same gates at different times