ASAP Methodology: SAP Implementation Guide
Uploaded by
Subodh KantASAP Methodology: SAP Implementation Guide
Uploaded by
Subodh KantWhat is the ASAP Methodology?
ASAP Methodology (Accelerated SAP) is a standard SAP related project preparation and
systems implementation method, developed and updated by consultants that are involved in
implementing SAP software products. This methodology is also useful for project managers and
others who implement systems that support business processes.
The purpose of ASAP is to help project management design SAP implementation in the most
efficient manner possible, by effectively optimizing time, people, quality, and other resources.
Using the ASAP methodology, project management provides the roadmap for optimizing and
continuous implementation of SAP systems in business processes. This solution was developed
to guarantee a successful, cost-effective and on-time delivery of all project solutions. Developed
by SAP (System Applications and Products) in order to optimize business suites, this framework
streamlines the use of methods, tools, accelerators, and templates that were originally developed
for SAP projects.
What is the ASAP Methodology Framework?
The Accelerated SAP methodology framework consists of five phases of implementation; each
phase of the roadmap provides detailed plans to assist in documentation, recommendations, and
implementation of SAP systems. Each phase of the process ends with a quality check that helps
monitor the deliverables and other factors of critical success. Below is a brief description of each
phase of the ASAP methodology roadmap
Phase 1: Project Preparation
This phase focuses on the initial planning and preparation to set ASAP goals. The phase typically
follows these three steps:
1. Clarify scope of implementation
2. Establish the team — committees, teams (core, project and consulting)
3. Define the sequence of project implementation
Phase 2: Business Blueprint
The aim of this phase is to arrive at a common understanding concerned with the procedures
intended to support the project. The Business Blueprint is a detailed document containing all
requirements derived during initial brainstorming and initiation meetings. This is also where the
project team revises its objectives and goals while setting a schedule for each.
Phase 3: Realization
This phase builds on Phase 2; it’s focused on implementing all business process requirements. In
this phase, project managers should attain signoff from stakeholders. Two work packages define
the system configuration methodology:
1. Baseline, concerned with the major scope.
2. Final Configuration, concerned with the remaining scope.
Phase 4: Final Preparation
The final preparation involves testing, system management, cut over activities, end-user training,
and all other tasks that are required to go live. Successful completion of Final Preparation
ensures that the organization is ready to begin using the new system.
Phase 5: Go Live and Support
This phase is the journey from a pre-production environment to a live project operation. The
most critical elements in this phase are related to production support setup, monitoring system
transactions, and optimizing system performance.
Advantages of ASAP Methodology
The ASAP Methodology covers the entire project lifecycle from the initial evaluation through
post-project management. The ASAP roadmap also ensures a transparent value delivery system
that consistently reflects upon business care while acting as a guide for SOA (Service Oriented
Architecture) and BPM (Business Process Management).
Proven, transparent approach that facilitates the project team to collaborate efficiently—
reducing implementation costs, time, and risks
Sensible risk management
Better knowledge management: ASAP helps project management organize, implement,
and meet business objectives
Steering committee tools
Better results because ASAP methodology is based on the experience of others—the
roadmap requires both soft skills and hard facts
Project times may be reduced
Better communications planning
Combination of best practice tools including ITIL, PMI, Internal SAP, and others
Conclusion
ASAP is increasingly being used in project management practices. To learn more about project
management, consider Simplilearn’s world-class project management courses. Our project
management training is facilitated by industry professionals with at least 10 years of experience.
ASAP is an approach that is followed while Implementing regular SAP Projects. Still there are
other methodologies like ASAP FOCUS in implementing Rapid Deployment Solution sought of
projects.
According to SAP redefined ASAP methodology follows below 6 phases.
ASAP Implementation Phases
The individual phases of the ASAP Implementation Methodology are:
Phase 1: Project Preparation
During this phase the team goes through initial planning and preparation for SAP project.
Phase 2: Business Blueprint
The purpose of this phase is to achieve a common understanding of how the company intends to
run SAP to support their business. In Standard ASAP 8 the result is the Business Blueprint, a
detailed documentation of the results gathered during requirements workshops. In Agile ASAP 8
the result is a Baseline Build and Project Backlog
reflecting the solution requirements prioritized by business value.
Phase 3: Realization
The purpose of this phase is to implement all the business process requirements based on the
Business Blueprint or Project Backlog. The system configuration in Standard ASAP is done in
two work packages: Baseline configuration (major scope); and Final configuration (remaining
scope). In Agile ASAP project team splits Realization phase into multiple releases with number
of time-boxed iterations focused on building up the functionality.
Phase 4: Final Preparation
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 critical open issues. On successful completion
of this phase, you are ready to run your business in your live SAP System.
Phase 5: Go Live Support
The purpose of this phase is to move from a project-oriented, pre-production environment to live
production operation.
Phase 6: Operate
The primary goal of this phase is to ensure the operability of the solution.
Each phase has a set of deliverables that are produced during the duration of the phase and serve
as the input to follow-up phases. Each deliverable provides list of Outputs it consist of and
Methods that are used to produce the deliverable.
