(ASAP) Roadmap, which originated in 1996, is still the backbone of more advanced and similar

project methodologies it can be downloaded as a PDFHere Or referenced as an overview below:

Phase 1: Project Preparation Phase 2: Business Blueprint Phase 3: Realization Phase 4: Final Preparation Phase 5: Go Live & Support

Phase 1: Project Preparation

In this phase of the ASAP Roadmap, decision-makers define clear project objectives and an efficient decision-making process. Here Project Organization and roles are defined and implementation scope is finalized. System landscape and Technical Requirement Infrastructure need (Hardware/interfaces) System Landscape High level strategies for client Archiving strategy Issues Database: Issues must be resolved before phase completion ot before beginning of the next phase. The issues can be Unanticipated tasks Normal tasks that can not be completed External factors that need to be dealt with. Issues database allows the project team to enter, track and report on project issues.

Phase 2: Business Blueprint

In this phase scope of the R/3 implementation is defined & Business Blueprint is created. Business Blueprint is a detailed documentation of companys requirements. Various tools are used in this phase. AcceleratedSAP Implementation Assistant Question & Answer Database (Q&Adb) Business Process Master List (BPML)

R/3 Structure Modeler Business Navigator and external modeling tools Project Management: Activities in this work package are:

Conducting Status meeting for project team Conducting steering committee meetings General project management Addressing organizational issues relating to organizational change management. Other activities include:

Project Team Training Developing the System Environment Defining Organizational Structure Defining the Business processes R/3 reference model can be used for

Comparing the standard functionality with your companies own organizational requirements Creating documentation for the conceptual design Optimizing business processes Training the project team and users Writing user documentation Question and Answer Database can be used to determine

The Baseline Scope Cycle Plan Integration test Plan

Phase 3: Realization
The purpose of Phase 3 is to configure the R/3 system. The configuration is carries out in two steps; baseline configuration & Final configuration. Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. It is used to identify, plan, schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. BPML is feeds all business information to all subsequent worksheets. Implementation Guide (IMG): It is the main tool for setting the parameters to configure or Customize

R/3 during the realization phase. IMG reflect the chronological order in which the customizing activities are carried out. The following aspects of configuration are also to be considered: Defining authorizations in the R/3 system Defining workflows Creating user documentation System Manager Procedures Developing system test plans Defining service level commitment Establishing system administration functions Setting up Quality Assurance environment Defining the design of the productive system Defining system management procedures for the productive system Setting up the productive environment At the end of this phase, Project Manager must check the status of deliverables for completeness and accuracy. This internal quality check should be carried out in addition to an external, independent third party Quality Audit. Preparation for end-user training needs to be gone through and approved at and of this phase.

Phase 4: Final Preparation

The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes testing, user training, system management and cutover activities, to finalize your readiness to go live. In this phase the R/3 system is handed over to individual departments for productive operation. This includes preparation of end-user documentation and training the end-users. The technical environment is installed on production system & is tested. Project managers prepare plans for going live, transfer of legacy data and support at early stages. End-user training is a critical activity for success of the project. InfoDB may be used to plan for the User Training activities. Computer Center Management System (CCMS) must be set at this time. Simulation of productive operation system & testing the same is of great important. The test plan contains the following activities Testing conversion procedures and programs. Testing interface programs

Conducting volume & stress testing Conducting final user acceptance testing Developing a final go-live strategy. The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes. Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. Disaster downtimes are verified and details on de-escalation.

Phase 5: Go Live & Support

This phase is concerned with supporting and optimizing the operative R/3 system. Following activities are carried out Production support facilities are defined. Validation of business processes and their configuration. Follow-up training for users Signoffs etc. During phase 5, the first EarlyWatch session should be held, where experts from SAP analyze the systems technical infrastructure. The aim is to ensure the system functions as smooth as possible. Version upgrades should be planned whenever found necessary. AcceleratedSAP contains a continuous roadmap, with standard activities necessary after implementation. The tasks in that structure provide solutions for all known types of continuous change: Business changes, technology changes or changes in user community. Post to Facebook Post to Twitter Add to LinkedIn Add to Google Bookmarks Send via E-mail program Post to Pinterest Post to StumbleUpon

Tags:ASAP , Project Methodology , SAP Tricks

ASAP Methodology for Implementation

Purpose
The ASAP methodology for implementation is a phased, deliverable-oriented methodology that streamlines implementation projects, minimizes risk, and reduces total cost of implementation. ASAP takes a disciplined approach to project management, organizational change management, solution management, and other disciplines applied in the implementation of SAP solutions. The methodology supports project teams with templates, tools, questionnaires, and checklists, including guidebooks and accelerators. ASAP empowers companies to exploit the power of the accelerated features and tools already built into SAP solutions. Benefits of ASAP include: Faster implementations with streamlined and focused methodology More reliable projects, thanks to proven tools, accelerators, and best practices Lower risk More efficient use of resources Reduced costs Effective project management based on Project Management Institute standards

Phases
The ASAP methodology delivers the following phases:

1. Project preparation

In the project preparation phase, the project team defines project goals, a high-level scope, and a project plan. Executive sponsorship is secured, and the project standards and organization are set up. The implementation strategy is defined and approved. At the same time, the project procedures, standards, organization, and staffing are finalized. Roles and responsibilities of the entire project team are agreed upon and documented. The objectives of the project are validated, and all initiation activities are documented in the project charter. During this business blueprint phase, solution and technical designs are documented in the business blueprint. Lead by solution and industry experts from the SAP Consulting organization, a series of structured process workshops are planned and executed to arrive at the to-be delivered" SAP enterprise solution. All available documentation for standard, delivered support for SAP business scenarios and all relevant preconfigured support for best practices are reviewed and discussed with SAP experts. All functional and technical requirements, coupled with project issues and gaps, are documented in the SAP Solution Manager application management solution. In the realization phase, the SAP software system is configured and tested in a number of cycles. Initially, the baseline configuration, which represents the core business process settings, is performed, tested, and confirmed. This is followed with a series of configuration and development cycles, to implement the entire end-to-end solution. The solution is tested in a number of cycle tests

2. Business blueprint

3. Realization

and in a focused end-to-end integration test. Configuration is documented in SAP Solution Manager. All development such as enterprise services, interfaces, data conversion programs, reports, and any required enhancements are built and documented in SAP Solution Manager. Legacy data conversion programs are created and tested. The production system is installed during realization. 4. Final preparation Within the final preparation phase, all systems are known to function correctly following the approved integration test. Technically, all integration issues should now be resolved. Detailed transition and cutover plans are created. The customer support organization is put in place. The production system is set up with transports and customer data. At the end of this phase, the production system is switched on and business operations start in the new environment. The purpose of the go-live support phase is to move from a preproduction environment to live production operation. An easily accessible production support organization must be in place to support the end-user community, not just for the first critical days of production operations, but also for long-term support. The primary goal of the run phase is to ensure the operability of the solution. Operability is the ability to maintain IT solutions in a functioning and operating condition, guaranteeing systems availability and required performance levels to support the execution of the enterprises business operations. The recommended starting point of the phase is an assessment of solution operation after the go-live support phase to identify the relevant SAP standards for solution operations to be established or improved in the phase. The central operation platform is SAP Solution Manager, with the documented solution based on the transferred project documentation.

5. Go-live support

6. Run

Work Streams
The ASAP methodology is structured around the key project work streams that are outlined in the picture below. For each work stream, the methodology lists the number of deliverables that are to be produced in each phase of the project.

The deliverables in later phases leverage or build upon deliverables completed in earlier stages. The roadmap is structured as a work breakdown structure (WBS) that represents a complete list of deliverables that need to be completed by the project team. The ASAP methodology for implementation projects represents a standardized work breakdown structure that provides the foundation for defining implementation project work in a deliverable-oriented, hierarchical manner and managing the project work to completion. ASAP methodology contains a standard set of templates, samples, accelerators, guidelines, and checklists for use by project teams in effectively managing and completing SAP solution implementation projects.
SAP Copyrights and Trademarks
2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.