ASAP Methodology OR Roadmap
Who needs to know about ASAP ?
Both project managers and team members. ASAP methodology gives theproject managers the requisite technology and management roadmap toimplement an SAP project following global standards and wellacknowledged strategies. This approach also greatly reduces the riskand improves project timelines by giving the project manager tools tomonitor and maintain metrics necessary for a successful implementation.Team members should be conversant with the general implementationroadmap as well as the specific accelerators that should be used tospeed up the implementation.
How is ASAP different from the standard Project Management Principles ( from PMI ) ?
If the project manager is well versed with the principles of PMP,then he/she should feel right at home. ASAP was developed by SAP ( incollaboration with its implementation partners ). The idea is toleverage this extensive experience and knowledge base to share the bestpractices specific to SAP implementations and apply them to theprinciples of PMI. So roughly speaking
PMI + SAP’s Inside Knowledge = ASAP
What are the advantages of using ASAP ?
- Project time cut down in half.
- Lower Risk
- Reduced Costs.
Are there any other roadmaps that I should be aware of ?
Yes. ASAP is the roadmap proposed by SAP to implementations. Thereare other methodologies and roadmaps (also proposed by SAP) toeffectively do other things in SAP like upgrades, support activitiesetc. The official details from SAP are available here .(http://service.sap.com/alm-methodologies)
What is ASAP Methodology ?
ASAP stands for Accelerated SAP. The word “Accelerated” refers tothe many so called “Accelerators” ( Tools & Information ) availablein SAP to expedite the implementation of SAP in an enterprise. So,simply put , ASAP is a methodology/ step-by-step approach used toeffectively and efficiently implement SAP
ASAP is divided into 5 phases.
(Courtesy – SAP©)
- Project Preparation: During this phase, the project goes through the initial planning and preparation phase .
- Business Blueprint: During this phase the implementing team and thebusiness comes to a common understanding on what needs to be done. Thisis achieved through workshops and meetings with the key users andgathering the requirements. The key deliverable of this phase is anapproved blueprint.
- Realization: The bulk of the work is done in this phase. The actualblueprint is broken down into functional specifications and furtherinto technical specifications to be worked on the functional andtechnical teams. The various teams go about with the actualconfiguration and customization of the SAP system to suit therequirements as highlighted in the blueprint. Each of the componentsare further unit tested.
- Final Preparation: This is a crucial phase of the project. Apartfrom system testing and integration testing, the users are heavilyengaged for the User Acceptance Testing ( UAT). Users are also trainedon how to perform the various business functions on the new system (User Training ). Also, various master data and transactional datatransfer requirements are evaluated to a much finer level of detailand the actual data migration is also performed.
- Go-Live and Support : Now you are ready to go live. This stepinvolves successfully planning the various go-live operations andstrategies and subsequent support activities as well.
Except for some jargon, anybody who is familiar with the generalprinciples of software engineering would be very familiar with thesteps involved.