Page History

Lessons learned notes (SAPbiz session held 02/09/2011)

Project Organization

• Steering Committee
  • Important that Steering Committee not be 99% IS&T.  Having additional Business worked well.

Planning/Schedule

• System Preparation
  • QC setup – For some business users, preparation to use the tool was last minute, should have been set up earlier.  People in VPF are not administrators of their machines and cannot install themselves – so anything which needs to be installed needs to be scheduled ahead of time.

•  
  • Access to sh3 for testing – the SAP GUI was not up to date for all users.  Need to prepare that everyone has up to date version and access.
  • Prepare that remote access is tested before cutover.

Testing

• SIT/UAT Testing
  • QC
    • Disappointed that the Business not able to edit and control changes on their own.
    • Is there a constraint on the number of people involved?  We now have 25 concurrent licenses.  Concerns over if this is enough during testing.
    • Would like expand the use of the QC with the business.
    • Those who could set up on their own found it initially difficult, once in was ok.
    • Many of the test cases need to be reworked – use SAP biz as a way for training, testing, and organization.
    • Automated testing

• Eager to have more scripts automated (HR:chair titles in particular would be great).
• Really liked having QC as a central repository for test scripts, even if printing them out was a bit of a challenge.
• Would be nice if there were a way to view the automated test scripts directly in QC, rather than having to request a printout from Don.
• New test scripts formats – business needs help with new template.  Training should be sooner rather than later.
• Going forward, coordination should be between functional areas, Business Analysts and QA.
• There was confusion about which Benefits test scripts Diane should perform.  Did she actually need to come up with scripts of her own, or was just showing up to key the HR Payroll transactions sufficient?  Diane needed to be included on Leslie’s list of testers.
• Next year we can have Diane do all of the validation testing in production, as opposed to having Riley do one tiny piece in ESS and Diane doing the rest

•  
  •  
    •  
      • No information concerning the content of the automated tests was shared with the business. 
      • Automated tests reviewed by some business groups, not others.
      • Going forward, automating testing should be part of SAP Biz to expand knowledge and usage.

•  
  • Need more people for testing, especially students.  Maybe we can involve the help desk and their students.  Especially important for testing authorizations and different hardware/software – Mac and PC testing.  Would like the community to get involve a little bit.
  • Testing with SAP alias is not effective, especially for certain apps like APR.
  • Run trial balance before the freeze is introduced.
  • Closing testing on Dec 6 – would like to do earlier to leave more time for other testing.  Want to do it end of November, rather than wait.
  • Calendar date changes cause issues with FI testing – need to test within the correct calendar month.
  • HR-Payroll testing:

Communication

• Testing coordinators communicated with business well, responses were quick.
• If WebEx is used in future, make sure people are familiar with process.

Cutover

• Communication
  • Emails appreciated in place of the phone line.  Fine line with emails – some want more, some want less.
• Execution
  • As expected.

Lessons learned notes (Steering Committee session held 02/01/2011)

...