Parallel testing overview
Embed Size (px)
Transcript of Parallel testing overview
- 1. Payroll Parallel TestingADP Implementation
2. PAGE 2Todays Purpose Introduce the Parallel Testing process Share what we have seen to date Explain why your input is so valuable Tell you what we need from you Tell you how you can learn more 3. PAGE 3Thank You Dedication Diligence Determination Desire Delivery All make ADP payroll a success for you and yourcompanys employees! 4. PAGE 4Keys to a Successful Parallel Detailed planning Setting expectations Good communication Positive attitude 5. PAGE 5Payroll Parallel Process Overview 6. PAGE 6What is it?What 3 people want to read this aloud?A payroll parallel is the process of verifying that our new ADP payroll system isas good as (or better than) the legacy payroll systems it is replacing. A set ofemployees and data is loaded onto the ADP payroll system so that it matchesthe legacy payroll system.A payroll period that has already been run on the legacy payroll system andused to pay employees is then recreated on the new ADP payroll system.The payroll results are then compared between the two systems down toemployee and pay element level. By proving that the new payroll systemmatches the legacy system, the business can have confidence that the newsystem has been configured and will pay its employees. 7. PAGE 7What is Parallel Testing and What is it Not? 8. PAGE 8OverviewWhat is Parallel Testing? Why do we perform the test? What time frame is being tested? What other testing has been performed? Unit testing Integration testing 9. PAGE 9Why do we perform the test? Verify data conversion mapping, data cleanup,cutover/ready-room procedures Validate System Configuration across the 5-companydata set Simulate our payroll jobs Validate the system known differences Attain processing results that meet projectexpectations for acceptable outcomes Confirm our readiness 10. PAGE 10OverviewWhat is Parallel Testing?Why do we perform the test? What time frame is being tested? What other testing has been performed? Unit testing Integration testing 11. PAGE 11What time frame is being tested?To the best of our knowledge - For exempts: This test uses time and personnel datafrom 3/15/2013 through 3/30/2013 For non-exempts: time entered from March 24 30 forpay date of 4/5/2013 Could change be flexible! 12. PAGE 12OverviewWhat is Parallel Testing?Why do we perform the test?What time frame is being tested? What other testing has been performed? Unit testing Integration testing 13. PAGE 13What other testing is performed? Unit Tests: Confirm individual configurations at companies as intended ona small scale Does not impact go-live until acceptable results are achieved Integration Tests: Connect the individual pieces of the system to test support ofbusiness process flow (example: interfaces) Validate accurate outcomes of specific scenarios 14. PAGE 14OverviewWhat is Parallel Testing?Why do we perform the test?What time frame is being tested?What other testing is performed? Unit testing Integration testing Misc information 15. PAGE 15Activities and Results Test and validate not only the configuration of thesystem, but also the processes, procedures, controls andconversions developed to produce Payroll results. Designed to create a comparison of the legacy payrollresults against the ADP payroll results. 16. PAGE 16Issue RegisterPriority(H, M,L)12DateResolvedResolution/CommentsIssue # Description CategoryReportedByAssignedToStatusRosalind & Barbara own the Issue Register 17. PAGE 17Preparing to run a Parallel The Parallel Test environment is established The foundation and translate tables are loaded into the parallel testenvironment. The team members have been identified and have dedicated time towork on the parallel test effort. Rosalind & Barbara have access to the ADP team. Discrepancies willarise that require ADP-specific knowledge and questions or issues needto be resolved in a timely fashion to keep parallel test on schedule. 18. PAGE 18Preparing to run a Parallel Construct the Payforce database Prepare payroll administrators for testing data Establish connections to Payforce Extract legacy data from the defined test period Map legacy values to Payforce values (paycodes, earn/ded codes, etc) Convert and validate data Load and validate collected data from spreadsheets If applicable, load and validate interfaced data into the system Load balances where required in the system Manually enter data (ex: lien & garnishment data) Load time data Run the payroll and address errors and variances Re-run and re-test 19. PAGE 19Things to Know Different systems sometimes have different values Some data does not exist in the legacy system Timing of payments Known differences 20. PAGE 20Items that could be different in legacy vs. PayForce: Imputed Income Deduction priorities Garnishments managed on a priority basis Accrual calculations are standardized 21. PAGE 21CAUTIONBusy Slide Ahead 22. PAGE 22Things to KnowHow will discrepancies be categorized?It is important to determine how discrepancies found between the legacy systemand new system outputs will be categorized. Below are some examples of thetypes of discrepancies found in Parallel Tests and how they can be categorized:Data entry/ Business Process errors: These discrepancies are defects, but not with the newsystem. They can be addressed by tweaks to the business processes; user training and/ or user guides.For example, slight discrepancies may be caused by differences in the respective systems method of rounding up ordown. These discrepancies require no action.Legacy system errors: Sometimes Parallel Testing reveals existing errors in the legacy system, corrected bythe new system. Stakeholders may wish to do nothing about these discrepancies, or they may wish to develop somecommunications to the employee population regarding this situation: - it will depend on the scale of the legacysystem error.Business Rule configuration errors: Many discrepancies will be due to the fact that there have beenslight errors in the configuration of business rules. For example, rules governing leave accruals. These discrepanciesare defects and will need to be corrected and the payroll re-run to ensure that these errors have been rectified.Unexplainable errors: These discrepancies are defects of the highest severity in a Parallel Test. Even adiscrepancy of 1 cent must be explainable. Otherwise, it represents an unacceptable risk to the business as there isno way of knowing why the engine is calculating 1 cent more/ 1 cent less. Moreover, there can be no assurance thatin subsequent runs the difference will not be of a greater magnitude. 23. PAGE 23Things we test Gross earnings Gross-to-net before tax, after tax, employer paid, etc. Taxes employees tax calculations: federal, state, local tax liability to agencies Benefit deductions 24. PAGE 24Why we need your help Gross Pay is determined at the company Much of the information related to what made up a specific paymentis held at the company level. Special payments may have been made for the period tested that werenot converted due to the one-time nature of the payment (e.g. bonuspayments). LOA may have been applicable and the value was not available forPayforce conversion. Overtime or other premium payments may have been paid for a periodother than that being entered for the test. 25. PAGE 25What to expect Most of the activities will require you to work at your facility. Hours to be arranged, but generally will be from 9:00am to6:00pm, Central time. Some overtime can be expected. Maintain a positive attitude. Remain flexible expect the unexpected. All team members will be a VERY integral part of the process. Focus of this work is to test; project deadlines do not permitredesign of functionality. 26. PAGE 26What to expect - 2 During testing, we hold daily status meetings at the samescheduled time. This meeting supports a communication processto inform the project team on the testing status, problems orissues, and changes. The Agenda will include a review of open high and medium issuesand any action items from the previous day. Meeting minutes will be taken that include a list of attendees,discussion points, and action items. 27. PAGE 27Exit Criteria All discrepancies have been explained or corrected, anddocumented. All earnings calculation discrepancies have been explained orcorrected, and documented. All deduction and garnishment calculation discrepancies havebeen explained or corrected and documented. All tax calculation discrepancies have been explained orcorrected and documented. 28. PAGE 28After the parallel The next step is to present the result of the Parallel Test to thesteering committee and request permission for go live to proceed. Once the steering committee has approved the go live, the projectcan move into the go live and post go live support phases. 29. PAGE 29Change Management You are a critical link to a successful implementation. Your input and expertise will help drive this project. Keep in mind that you may be seeing only a piece to a largerprocess. Reserve judgment! We need your positive outlook to help solidify change in yourcompany. 30. PAGE 30Questions?