1. Twenty Tips for a successful SAP Upgrade John Beaumont VP, SAP Field Operations Intelligroup, Inc

2. It May be Obvious to you! The instructions are clear! But then what happens? (even after training): Models and make-up artists use it! Glamour Magazine reported that Miss USA contestants used the product to smooth their skin even around the eyes. E TV's Behind the Scenes at the Miss USA Pageant reported contestants using it to reduce cellulite on their thighs. Can Users Really Be Trusted?

3. 1. Hey! This is a project too. You will get the success you plan for An Upgrade is a project and treated as such Involve the business Get help if you need it Get an experienced project manager 2. Take me to your leader! Before we set off – we need to know who is driving Empower your project manager Don’t manage by committee 3. Spend a dollar to save ten. Lower Risk, Save Money – Impress the Boss. Plan before you go The realization phase is the most costly Emphasize learning and discovery before the project Use planning and analysis tools (Uptimizer) 20 tips and tricks

4. 4. Get the GUI out early. Reduce the impact: Get users used to the look and feel 5. Target training. Get the users involved: Classroom training, especially if you are introducing new functionality or processes Lunch time learning – most users will turn up if you order pizza Super user – train the trainer Newsletters, posters, web sites On line context sensitive help And don’t forget the project team! 20 tips and tricks

5. 6. Get a fix on your development The ABC of “Z’s and “Y”s… The upgrade minefield Know before you go Repair/Replace/Redesign Strategy 7. Give equal emphasis to all components These are the major areas – someone should own them. Business: Activities that are directed to the business or organization Technical: Activities that involve systems, hardware or their environment Functional: Activities that relate your SAP functionality Development: Activities that relate your custom developments for SAP 8. Look for helpful tools & services There are a lot more tools and services for Upgrades. Uptimizer from Intelligroup Upgrade assistance services from SAP Web based learning

6. 20 tips and tricks 9. Final cut over should be a non-event Practice makes perfect. Practice Test Practice…. 10. Cooling down the system When freezing is a good thing. The less concurrent development the better If there are parallel projects they must be planned to the upgrade You must freeze as much as possible after Integration Testing 11. Is this really a “technical upgrade”? Not such much as you think! The bigger the jump the more functional involvement Low hanging fruit – stay away from lemons

7. 20 tips and tricks 12. You may not get a prize for being first. When SAP releases a major new release there are normally three waves of uptake: True believers (first shipments); “that one power point slide has really convinced me, send the CD’s” Followers (early adopters); “I’ve seen the web demo, and I know a true believer, send the CD’s” Observers (the rest); “Great – let’s wait and see, but no need to send the CD’s just yet” 13. Spread the load! Cut over quickly, rehearse the timings Special plans for highly available environments Lots of data could equal lots of time See what can be done to cut down the data & time 14. Selecting test data Don’t – rely on test data Use real data if possible Remember volume and stress testing Batch and interface testing is vital

8. 20 tips and tricks 15. Supporting your current system while upgrading Do you have enough staff to do both the upgrade and support Cut back on other projects Focus your team Use consultants – consider using consultants for support rather than upgrade tasks 16. Start insider trading You need all the supporters you can get. Senior management must be on board Lobby users for their support Selling an upgrade may be difficult But it must be done 17. (a) Is there such a thing as an ROI for an upgrade? NO!!

9. 20 tips and tricks 17.(b) Management insists that there is an ROI See 17(a) or look at the upgrade in the wider sense. Post Upgrade projects – competitive advantage Removal of high maintenance workarounds SAP discontinues support (pay extra to a 3 rd party)System more efficient 18. Beyond “low hanging fruit” – adding functionality Two projects = four times the problems. Manage critical path timing Reduce or eliminate dependencies AVOID scope creep 19. Network OK being here is a start Unless you are really the first!! - Find the ones that have gone before

10. 20 tips and tricks 20. Don’t forget the obvious! “I thought you were telling the users/customers/vendors/management/auditors!” “What do you mean the hardware lead-time is 12 weeks?” “What vacation!” “We don’t need change management/training/documentation” “Doesn’t everything work on 64bit?” “I thought that was standard with this version” “Who could have guessed that we had 3 year old PCs” “What other things need upgrading?” “We have more hardware so why do we need a stress test?”

11. Thank you for attending! Please remember to complete and return your evaluation form following this session. Session Code: 2903