Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
ASAP Methodology- 1st Phase- Project Preparation

ASAP Methodology- 1st Phase- Project Preparation

|Views: 562|Likes:
Published by bdkumar_684437085

More info:

Published by: bdkumar_684437085 on May 05, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





ASAP Methodology for Implementation 7.2
ASAP methodology
for implementation
is a phased, deliverable-oriented methodology that streamlines implementation projects, minimizesrisk, 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 withtemplates, tools, questionnaires, and checklists, including guidebooks and accelerators. ASAP empowers companies to exploit the power of theaccelerated 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
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 strategyis 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 arevalidated, and all initiation activities are documented in the
project charter 
2. Business blueprint
During this
business blueprint
phase, solution and technical designs are documented in the business blueprint. Leadby 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 arereviewed and discussed with SAP experts. All functional and technical requirements, coupled with project issues andgaps, are documented in the SAP Solution Manager application management solution.
3. Realization
In the
phase, the SAP software system is configured and tested in a number of cycles. Initially, the baselineconfiguration, which represents the core business process settings, is performed, tested, and confirmed. This isfollowed with a series of configuration and development cycles, to implement the entire end-to-end solution. Thesolution is tested in a number of cycle tests and in a focused end-to-end integration test. Configuration is documented inSAP Solution Manager. All development such as enterprise services, interfaces, data conversion programs, reports, andany required enhancements are built and documented in SAP Solution Manager. Legacy data conversion programs arecreated 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. Thecustomer support organization is put in place. The production system is set up with transports and customer data. At theend of this phase, the production system is switched on and business operations start in the new environment.
5. Go-live support
The purpose of the
go-live support
phase is to move from a preproduction environment to live production operation. Aneasily accessible production support organization must be in place to support the end-user community, not just for thefirst critical days of production operations, but also for long-term support.
6. Run
The primary goal of the
phase is to ensure the operability of the solution. Operability is the ability to maintain ITsolutions in a functioning and operating condition, guaranteeing systems availability and required performance levels to
support the execution of the enterprise’s 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 solutionoperations to be established or improved in the phase. The central operation platform is SAP Solution Manager, with thedocumented solution based on the transferred project documentation.
 Work Streams
The ASAP methodology is structured around the
key project work streams
that are outlined in the picture below. For each work stream, themethodology 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 breakdownstructure
(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 definingimplementation 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 effectivelymanaging and completing SAP solution implementation projects.
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 theexpress 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 andInformix 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 Incorporatedin the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registeredtrademarks 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 WebConsortium, 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 servicesmentioned 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 SAPFrance in the United States and in other countries.
 All other product and service names mentioned are the trademarks of their respectivecompanies. 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 respectto the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statementsaccompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
1. Project Preparation
project preparation
phase provides initial planning and preparation for the project. Although each project has its own unique objectives,scope, and priorities, the deliverables outlined below assist in completing the initiation and planning steps in an efficient and effective manner.
Work Streams
The major work streams for this preparation
Project management
Organizational change management (OCM)
Data management
Business process management
Technical solution management
Integrated solution readiness
Project Management
The purpose of the
project management
is to provide essential methodology for the requirements planning for and execution/controlling of an SAP software implementation project.
Team Identification, Allocation, and Coordination
During subsequent phase start-up activities, the project manager coordinates the allocation of resources identified for the project phase using theproject schedule and the resource plan. This ensures the proper timing of resource assignments needed to complete project work. The projectmanager validates the participation and ongoing commitment of the steering committee members at the phase start-up.
Kickoff Meeting
The scale of this task varies with project size and complexity. For small, low-risk projects, the kickoff meeting may be an informal review of theprocess by the project sponsor and the program or project manager. For larger projects, you should consider a formal kickoff of the project toachieve a common understanding of the objecti
ves of the planning process and to clarify the various participants’ roles. The project manager 
clearly defines the
objectives of each phase kickoff meeting and designs the agenda to achieve that objective. Consider conducting the followingtypes of meetings:
should be focused on the team to ensure alignment around the work (definition and approach for outputs) to beperformed during the phase.
should be focused more on communications across the organization, bringing the project sponsor and key stakeholders together to reinforce commitment to the project and raise awareness across the organization. This type of kickoff 
could be an important part of the project’s organizational change management approach.
The project manager balances these different types of kickoff meetings to ensure that stakeholder time is optimized and project communicationsneeds are met
both at a team level and an organizational level.
Project Schedule
The project manager expands and updates the project schedule. At a minimum, the schedule should include the following components:
Phase deliverables and tasks
Estimated effort (work) and duration
Task dependencies such as predecessors and successors

Activity (4)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
Libero Petringa liked this
barber bob liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->