WIXLIB

ASAP ImplementationRoadmap

Methodology – why? ASAP OverviewASAP Roadmap StructureProject Management in ASAPASAP Content OverviewHow to access Roadmap

Projects from another perspective“An estimated 68% of corporate IT projects areneither on time nor budget, and they don’tdeliver the originally stated business goals.Some even claim that during the last twoyears, 100 billion to 150 billion of U.S. ITprojects have failed altogether.”Mark Jeffery and Ingmar Leliveld: Best Practices in IT Portfolio Management,MITSloan Management Review, Spring 2004 SAP America 2004, PM Methodology Web Session Page 3

Typical questions when you starting the projectHow to best use selectedsolution capabilities?How and wheredo we start?How to buildinternalexpertise?Do we have internalcapabilitiesand capacity tostaff the project?Who does whatin this project?How to manageproject and businessrisks involved? SAP America 2004, PM Methodology Web Session Page 4How expensive willthis project be? Howdo we keep the costs low?How do we assuresuccess?

Industry Best Practices to mitigate project failure riskTOP 10 MOST UTILIZED PRACTICES in IT projects1. Regularly use project management methodologies: 96%2. Conduct regular strategic planning meetings to achieve alignment: 93%3. Conduct internal customer satisfaction surveys: 86%4. Create and use performance metrics: 81%5. Regularly use portfolio management or other project prioritization methodology: 80%6. Perform financial audits: 79%7. Use leadership development programs: 79%8. Make the CIO a member of the corporate board or executive committee: 76%9. Employ internal relationship managers/account executives to work with the business: 75%10. Conduct post-implementation audits: 74%(Percentages refer to number of respondents using this practice.)Source: Richard Pastore and Lorraine Cosgrove Ware: The Best Practices, CIO Magazine May 2004 SAP America 2004, PM Methodology Web Session Page 5

Delivering Successful SolutionsAcceleratedSAP MethodologyDescriptionAcceleratedSAP methodology is proven, repeatable and successfulapproach to implement SAP solutions across industries andcustomer environments.AcceleratedSAP provides content, tools and expertise fromthousands of successful implementations.More infohttp://service.sap.com/asap SAP America 2004, PM Methodology Web Session Page 6

Key components for successAcceleratedSAP - proven methodologyProject Management expertiseManagement of the implementation projectAligned with industry standards and procedures (PMI PMBOK )Specific to implementation of SAP solutionsAcceleratedSAP toolsetSAP Solution ComposerSAP RoadmapsSAP Solution ManagerAligns customer’s businessrequirements to SAPsolutionsOffers AcceleratedSAProadmap composed to fitspecific project needsFacilitates efficient solutiondesign, documentation,configuration, testing andoperations SAP America 2004, PM Methodology Web Session Page 7

Key components for successAcceleratedSAP - proven methodologyAcceleratedSAP methodology Provides proven, comprehensive, repeatable and rich implementationmethodology to streamline projectsValueSAP ToolsetNew Toolset PMI aligned framework with templates and tools for performing effectiveproject managementSAP Solution ComposerSAP RoadmapsSAP Solution Manager Aligns customer’s businessrequirements to SAP solutions Delivered offline in SAP ServiceMarketplace and in SAP SolutionManager Facilitates efficient solutiondesign, configuration, testingand operationSAP Solution MapComposerImplementationAssistantQ&Adb, BPML, DiagramExplorerEvolved to SAP America 2004, PM Methodology Web Session Page 8Evolved toReplaced by

SAP ConsultingWhere Methodology fitsAchieve yourimplementationgoals throughleveraging SAPexperts, services,methodology,content and ogyContentandTools SAP America 2004, PM Methodology Web Session Page 9

Content:AcceleratedSAP RoadmapsGuidance and navigation for your implementation teamDefinitionASAP roadmaps outline the activities involved inimplementing, upgrading, or enhancing SAP solutionsenriched with set of deliverables, accelerators, roledescriptions and additional guidesUsageProvide content (work packages, activities, tasks,deliverables, accelerators) that can be used during theentire project lifecycle.Target GroupCustomers, Partners, SAP ConsultingAvailabilityThe roadmaps are made available through: SAP SolutionManager and SAP Service MarketplaceBenefits Transparent, proven approach helping the project team to really work as a team and to reduceimplementation time, costs and risks Achieve better results since you base your project on the experiences others made before. Both hard factsas well as soft skills are addressed Knowledge management - use the Implementation Roadmap for SAP solutions to gather knowledge on howto organize and run your implementation projectsMore infohttp://service.sap.com/roadmaps SAP America 2004, PM Methodology Web Session Page 10

AcceleratedSAP Implementation MethodologyPhase 1: Project PreparationDuring this phase the team goes through initial planning and preparation for SAPproject.Phase 2: Business BlueprintThe purpose of this phase is to achieve a common understanding of how thecompany intends to run SAP to support their business. The result is the BusinessBlueprint, a detailed documentation of the results gathered during requirementsworkshops.Phase 3: RealizationThe purpose of this phase is to implement all the business process requirementsbased on the Business Blueprint. The system configuration methodology is provided intwo work packages: Baseline (major scope); and Final configuration (remaining scope).Phase 4: Final PreparationThe purpose of this phase is to complete the final preparation (including testing, enduser training, system management and cutover activities) to finalize your readiness to golive. The Final Preparation phase also serves to resolve all critical open issues. Onsuccessful completion of this phase, you are ready to run your business in your live SAPSystem.Phase 5: Go Live & SupportThe purpose of this phase is to move from a project-oriented, pre-productionenvironment to live production operation. SAP America 2004, PM Methodology Web Session Page 11

SAP Standard Roadmaps (1/2)Roadmap TypeImplementationDescriptionImplementation Roadmap for SAP Solutions provides themethodological framework for the project team to leverage in theimplementation of a SAP solution. It covers, among other things, thenecessary project management, requirements gathering, design,configuration of business processes, technical implementation, testprocedures, training and organization change management.In this roadmap deliverables represent the main objects within aproject. Each deliverable then provides outline of the Outputs(components creating the deliverable) and relevant Methods thatrepresent the activities and tasks the project team conductsGlobal TemplateThe Global Template Roadmap describes how to organize and howto run a project in which a corporate template is developed. TheGlobal Template Roadmap is geared to more compleximplementation or harmonization projects, typically involving morethan one kind of SAP solution, and a variety of sites, possibly indifferent countries. The corporate template is rolled out to other sitesin a follow-up project. SAP America 2004, PM Methodology Web Session Page 12

SAP Standard Roadmaps (2/2)Roadmap TypeDescriptionUpgradeThis roadmap is designed to help you carry out the customizingactivities required for an upgrade. These customizing activities areessential if you want to continue to use the same functions in yourbusiness application components after an upgrade.Solution ManagementThe Solution Management Roadmap provides a methodology for theimplementation of the technical infrastructure and its operation. TheSolution Management Roadmap complements the ImplementationRoadmap. SAP America 2004, PM Methodology Web Session Page 13

Roadmaps Add Value to the ImplementationWhen used properly, a roadmap will provide guidance on the following:Why you should do itand how to do itWhat to do,and when todo itWho does itAccelerators SAP America 2004, PM Methodology Web Session Page 14

Enforcing standardsMethodology alone will not make your projectsuccessful. You need to enforce it – appointmethodology champion for the project. SAP America 2004, PM Methodology Web Session Page 15

Methodology – why? ASAP OverviewASAP Roadmap StructureProject Management in ASAPASAP Content OverviewHow to access Roadmap

Source: Implementation Roadmap – Activity based (ABR)StructurePhase(Level 1)Each Roadmap is divided into severallarge phases, each of which representsa major milestone in the project plan.Work Package(Level 2)Each ASAP Roadmap phase is made upof several work packages with topics.The work packages are designed torealize the main objectives of eachRoadmap phase. Work packages aremade up of activities and tasks.Activity(Level 3)Each work package comprises severalactivities. Activities contain the tasksthat project team members need to carryout, in order to fulfill the project goals. Atthis level, you can find more acceleratorscontaining information relevant for yourimplementation project.Task(Level 4)Each activity is made up of severaltasks. The task describes the stepsProject team members are required toperform the tasks.Level 1Level 2Level 3Level 4 SAP America 2004, PM Methodology Web Session Page 17Description

Source: Implementation Roadmap – Deliverable based (DBR)StructureDescriptionPhase(Level 1)Each Roadmap is divided into severallarge phases, each of which representsa major milestone in the project plan.Deliverable(Level 2)Each phase is made up of severaldeliverables with topics. Thedeliverables represent the main objectswithin a project. A deliverables are furthercomprised of outputs.Output(Level 3)Each deliverables comprises severaloutputs. Outputs are document ortangible items that are results of aprocess. The output supports thecompletion of a desired deliverable as astandalone component.Level 1Level 2Level 3The Deliverable-based Roadmap will also have a ‘references’tab to provide a link to the activities & tasks (method)associated with creating the deliverable. SAP America 2004, PM Methodology Web Session Page 18

Improved Implementation RoadmapActivity based Impl. RoadmapImplementation RoadmapDeliverable Based Impl. Roadmap SAP America 2004, PM Methodology Web Session Page 19

Implementation Roadmap - StructurePhaseDeliverable Group 1DeliverableO: Output α.1Deliverable consistsof several outputsO: Output α.2M: Activity 1.1Task 1.1.1Task 1.1.2M: Activity 1.2Task 1.2.1Deliverable Group 2Milestone A SAP America 2004, PM Methodology Web Session Page 20Methods (activitiesand tasks) thatcreate or contributeto creation of thedeliverable

Easy navigation in the roadmap Attributes used to classify roadmap nodes and accelerators to enable easynavigation and user specific views. Following attributes are used Flavors – represents SAP Solutions (mySAP ERP, mySAP CRM, .) Subject Areas – knowledge domains in the implementation project (Project Management,Org. Change Management, Technical Implementation, ) Project Roles – filter activities, tasks or outputs Showing only relevant areas of the roadmap (by user preference) Activity based view Deliverable based view SAP America 2004, PM Methodology Web Session Page 21

ReferencesRelationship between Outputs and relevant Activities or TasksPhaseDeliverable Group 1DeliverableO: Output α.1O: Output α.2M: Activity 1.1Task 1.1.1Task 1.1.2M: Activity 1.2Task 1.2.1Deliverable Group 2Milestone A SAP America 2004, PM Methodology Web Session Page 22References point from Tasks or Activities(where tasks are not available) to the relevantOutputs that are being produced (orcontributed to) by the performed task oractivity.

Deliverable: Methods and Outputs relationship

ERROR: stackunderflowOFFENDING COMMAND: STACK:

ASAP roadmaps outline the activities involved in implementing, upgrading, or enhancing SAP solutions enriched with set of deliverables, accelerators, role descriptions and additional guides Usage Provide content (work packages, activities, tasks, deliverables, accelerators) that can be used during the entire project lifecycle. Target Group