McCain ANZ Testing & Training Strategy_v1.0.pptx

[Audio] Implementation Timeline. Implementation Timeline.

[Audio] DMS Project Timeline(as per revised timeline).

[Audio] CRD Project Timeline(as per revised timeline).

[Audio] Entry Criteria for Testing. Entry Criteria for Testing.

[Audio] Entry Criteria - System Integration Testing (SIT) ERP Data CRD Loads Build & Functional Testing are Credit Master Blocked Order Updates/Creation (API) Credit Updates (HighRadius Outbound) Blocked Order Release (HighRadius completed by all parties HighRadius, McCain, Third AR - Open and Closed Summary Extract Customer Master Customer Contacts Partner Extract Parties as required DMS Loads Outbound) **AI Extracts (one time)-Order header(OTL and Delta) Order Change History(OTL), Credit Change History(OTL) CLS Loads Closed AR (2 years) Sales Invoice PDFs Test ERP System has Production Equivalent Data Inbound Material Master Item Cross Reference Sales Invoice Header Sales Invoice Item POD Extract - CPA Return Order Creation Header Return Order Creation Item Return Order - Update Vistex Agreements & Partner Promotion Condition Header Promotion Condition Item Customer Hierarchy Migration for close & open disputes Outbound Resolution Extracts Split Extract Return Order Billing Block Reason Code Update 7.

[Audio] Testing Phases. Testing Phases.

[Audio] - SIT Testing System User Integration Testing Acceptance Testing Validate all Inbound and Outbound data transfer Data loading and Processing Validate User's access to HRC System 9.

[Audio] Testing Phases - UAT Testing User System Acceptance Testing Integration Testing Validate User Journey Workflows Validate Specific Use Cases 10.

[Audio] Entry Criteria - User Acceptance Testing (UAT) 1 Test Scenarios based on Different User Personas and User Journeys are finalized 2 System Integration Test Users are Identified and Informed Testing Sign Off to spend dedicated time for UAT 3 Exit Criteria and Change Management Process is Agreed 11.

[Audio] SIT Testing Approach. SIT Testing Approach.

[Audio] Testing Approach - SIT McCain to send all the Inbound Integration data HighRadius to load and process Inbound Integration data HighRadius to provide access to McCain Users McCain Business Users to perform actions in the HighRadius application to create data for outbound files HighRadius to send Outbound Integration data Cases are fixed based on Case Classification and Criticality 13.

[Audio] Proposed Testing Plan - SIT - DMS Start Date End Date Activities 21-Jun 25-Jun McCain shares the Extracts from the Test ERP environment with refresh as of test system refresh date 26-Jun 27-Jun HighRadius validates the extracts, process data in the HRC System 28-Jun 28-Jun HighRadius validates the HRC systems - Internal Testing 4-Jul 9-Jul McCain reconciles the data in the HRC system for SIT validation, Report cases DMS shares output file with Mccain and Mccain posts it in ERP and validates. 10-Jul 12-Jul Review results/test cases executed, sign off on SIT For SIT Testing Test environment refresh date (D) = 10-06-2024 Worklist generation date = (D) + 1 14.

[Audio] Proposed Testing Plan - SIT - CRD Start Date End Date Activities 8-Jul 9-Jul McCain shares the Delta Extracts from the Test ERP environment with refresh as of test system refresh date 10-Jul 12-Jul McCains validates the extracts(CM, AR, CREDIT) and downstream Calculations 15-Jul 15-Jul McCains test the Order release from HighRadius 16-Jul 17-Jul McCain reconciles the data in the HRC system for SIT validation, Report cases CRD shares outbound files for Credit Updates, Blocked order release and New Customer Onboarding to ERP. 18-Jul 19-Jul Review results/test cases executed, sign off on SIT ** Requesting extracts (CM, AR,Credit Master,AI Order Extracts) by 28th June 2024 to prevent any data loading failure and time spill from the planned SIT testing. For SIT Testing Test environment refresh date (D) = 10-06-2024 Worklist generation date = (D) + 1 15.

[Audio] UAT Testing Approach. UAT Testing Approach.

[Audio] Testing Approach - UAT Replicate the User Journeys on the Production Equivalent Data from UAT environment Worklist will be generated considering the Users. Users should test the User Journeys End to End Report Scenario Execution and the cases in the Tracker Cases are fixed based on Case Classification and Criticality Same steps and process will be followed in the following weeks of UAT. 17.

[Audio] CRD- UAT Plan. CRD- UAT Plan.

[Audio] Proposed Testing Plan - UAT Cycle (CRD) Start Date End Date Activities 22-Jul 22-Jul Training of Test Users 23-Jul 23-Jul Training of Test Users 24-Jul 24-Jul Training of Test Users 25-Jul 25-Jul UAT starts, follow the approved User Journey based test scenarios 26-Jul 26-Jul Continue the UAT, Case reporting and Defects Fixing 26-Jul 26-Jul UAT test cases execution and issue resolution Test Users should perform actions based on the User Journeys and report cases HighRadius will look at the cases and work on Critical and High priority Defects 19.

[Audio] Proposed Testing Plan - UAT Cycle (CRD) Start Date End Date Activities 29-Jul 29-Jul HighRadius keeps generating the CRD worklist 30-Jul 30-Jul Perform UAT on the new Worklist 31-Jul 1-Aug Continue the UAT, Case reporting and Defects Fixing 2-Aug 2-Aug Review UAT Results and defect tracker resolution. Test Users should perform actions based on the User Journeys and report cases HighRadius will look at the cases and work on Critical and High priority Defects 20.

[Audio] Proposed Testing Plan - UAT Cycle (CRD) Start Date End Date Activities 5-Aug 5-Aug Now that User Journey's are complete, Users should test remaining Use Cases 6-Aug 7-Aug Continue the UAT, Case reporting and Defects Fixing 8-Aug 9-Aug Continue the UAT, Case reporting and Defects Fixing 12-Aug 16-Aug Placeholder for any additional UAT scenarios, to sign of on UAT by 16 Aug 2024 Third week will focus on Special Use Cases like: 1. Reports 2. Delta File Testing 3. Outbound 21.

[Audio] Proposed Testing Plan (CRD) Start Date End Date Phase Pre-requisites 1. HRC System Readiness 24-Jun 28- Jun HRC Internal Testing 2. Mccain to perform test system refresh and send data by 28-Jun. 1. HRC Internal Testing is completed and closed 8-Jul 19-Jul Integration 2. All Interface code changes moved to Testing environment Testing 3. Daily updates are sent to HRC 22-Jul 26-Jul UAT Week 1 1. User Training 2. Integration Testing is completed and closed 29-Jul 2-Aug UAT Week 2 1. Continuing executing all the test cases and resolving the defects as per the criticality from the tracker. 5-Aug 9-Aug UAT Week 3 1. Continuing executing all the test cases and resolving the defects as per the criticality from the tracker. 12-Aug 16- Aug UAT Buffer Buffer period to complete UAT - UAT sign off 19 - Aug 30-Aug Cutover HighRadius Internal Test to Prod Movement 2-Sep 2-Sep Go-Live 1. Smoke Testing Sign Off 2. Successful Cutover 3. Hypercre Commencement *Assumption : These dates have been derived as per the planned timelines.

[Audio] DMS- UAT Plan. DMS- UAT Plan.

[Audio] Proposed Testing Plan - UAT Cycle#1 (DMS) Start Date End Date Activities 22-Jul 22-Jul Training of Test Users 23-Jul 23-Jul Training of Test Users 24-Jul 24-Jul Training of Test Users 25-Jul 26-Jul UAT starts, follow the approved User Journey based test scenarios 29-Jul 2-Aug Continue the UAT, Case reporting and Defects Fixing Review UAT Cycle 1 Results and Prepare for Cycle#2 Test Users should perform actions based on the User Journeys and report cases HighRadius will look at the cases and work on Critical and High priority Defects 24.

[Audio] Proposed Testing Plan - UAT Cycle#2 (DMS) Start Date End Date Activities 5-Aug 5-Aug HighRadius generates the Worklist again 6-Aug 7-Aug Perform UAT on the new Worklist 8-Aug 14-Aug Continue the UAT, Case reporting and Defects Fixing 15-Aug 16-Aug Review UAT Results and Prepare for Cycle#3 For UAT Cycle 2 Testing Test environment refresh date (D) = 31-Dec-2023 Worklist generation date = Test Users should perform actions based on the User Journeys and report cases HighRadius will look at the cases and work on Critical and High priority Defects 25.

[Audio] Proposed Testing Plan - UAT Cycle#3 (DMS) Start Date End Date Activities 19-Aug 19-Aug Now that User Journey's are complete, Users should test remaining Use Cases 20-Aug 21-Aug Continue the UAT, Case reporting and Defects Fixing 22-Aug 23-Aug Continue the UAT, Case reporting and Defects Fixing 26-Aug 30-Aug Placeholder for any additional UAT scenarios, to sign of on UAT by 30 Aug 2024 Cycle 3 will focus on Special Use Cases like: 1. Reports 2. Delta File Testing 3. Regional Language Templates 4. IR Scenarios (if in scope) 26.

[Audio] Proposed Testing Plan (DMS) Start Date End Date Phase Pre-requisites 1. HRC System Readiness 10-Jun 14- Jun HRC Internal Testing 2. Mccain to perform test system refresh and send data by 17-Jun. 1. HRC Internal Testing is completed and closed 24-Jun 12-Jul Integration 2. All Interface code changes moved to Testing environment Testing 3. Daily updates are sent to HRC 22-Jul 2-Aug UAT cycle 1 1. Integration Testing is completed and closed 5-Aug 16-Aug UAT cycle 2 19-Aug 23-Aug UAT cycle 3 26-Apr 30- May UAT Extension Buffer period to complete UAT. 2 - Sep 20-Sep Cutover UAT sign off 23-Sep 23-Sep Go-Live 1. Testing Sign Off 2. Successful Cutover *Assumption : These dates have been derived as per the planned timelines.

[Audio] Case Classification Defects and Change Requests.

[Audio] Categorization of Defect and Change Request Defect Change Request Any case that is a result of deviations from the approved design (PDD) Any case that is a result of system not performing to the approved design (PDD) Missed or Wrong Configurations by Consultants Modification to correspondence templates Environment down New Custom/Product Features Incorrect Data sent/processed Usability related requests 29.

[Audio] Prioritization of Defects Medium Critical Case that causes minor loss of service or has a manual work around Case that does not allow using the System completely or a major functionality is not working Environment down or Users not able to access System Layout field is missing, Template content/layout incorrect Worklist is not available High Low A reported anomaly in the System which does not impact to necessary business functionality Case that reduces the ability to use the system for business process effectively and has high impact on the efficiency Field names are not as per PDD, Fields order in UI Ageing is Incorrect, Delinquent Customers not coming in the Worklist, Users unable to create P2P, Emails not going to Customers 30 Payments not loaded correctly in CAA Or Global rules aren't working as per agreed design.

[Audio] Types of Defects Subcategory Definition An issue, error, or bug in the HighRadius product. For example, the data was not correctly displayed when a user clicked on a workflow. Product Defect Infrastructure Defect Disruption in business flow due to hardware issues like memory, storage, or server problems. For example, a few users were not able to perform daily activities because the HighRadius product was slow. Operations Defect Unable to perform day-to-day operations because of a HighRadius, Client, or third-party operational failure. This typically happens when data is not transferred within the scheduled time or in the correct format. For example, customer master extract was supposed to be received by 9 PM. But, it was not received until the following day. As a result, the users could not work with the latest Customer master data. Service Disruption A defect that results in most users being unable to access the HighRadius product and/or service. For example, multiple end-users were not able to access or log into the HighRadius products. Consulting Defect A defect that results in a specific functionality not working as per the agreed Design during the implementation. For example, output API was sent in wrong format compared to design 31.

[Audio] Types of Change Requests Subcategory Definition Administrative Task A request for a one-time activity that can be performed by the end-user or admin but is being requested to be done by the HighRadius team. For example, Mccain requested HighRadius to create a new user. New Implementation Request A request to change the existing configuration or add a new configuration. It may also include any one-time configuration setup which increases the automation rate. For example, add a new credit agency. Past Implementation Issue This will not be applicable for net new product implementations Training Request A request for end-user or admin training. For example, The McCain requested HighRadius for training or a demo for the team on how to add a new user. A request for new product features or functionalities. For example, in the Product Feature Request Credit Cloud, a McCain requested a new feature to forecast the credit scores of their Customers. 32.

[Audio] Issue Reporting Issues need to be logged on Mccain's HP ALM for UAT Details to be provided as below: Case description including data/steps to replicate Priority Issue Type.

[Audio] Exit Criteria for Testing. Exit Criteria for Testing.

[Audio] Exit Criteria 1 2 3 User Training and All Critical and High User Journey Defects Closed RCA and ETAs provided for Medium and Low validation completed Defects 35.

[Audio] Training Strategy Test & Go-Live. Training Strategy Test & Go-Live.

[Audio] Training Approach SME Training (Train the Trainer) Onsite/Remote Training Continuous training over interface testing & UAT Self Learning through testing End User Training Training sessions lead by business SME and supported by HighRadius Training Exercises.

[Audio] Implementation Framework Project Governance Preparation (2 weeks) Deploy (3 weeks) Test (6 weeks) Design (7 weeks) Realize (8 weeks) Hypercare (4 weeks) Hypercare Support Hypercare support Blueprint Demo using best Train the Trainer End to End Introduction As-Is sessions Data collection for practices Configuration Write Functional Specs Develop testing / tests/results End user training Cutover activities Share support info Go-Live analysis training strategies Setup batch jobs in test environment Blueprint Preparation Setup program Design review Value alignment Conversion & governance deployment strategies System demo Develop interfaces Develop cutover plan ERP Data load and UAT test/results Issue fixing Share training material Finalize design plan Draft implementation Interface testing plan Design approval Baseline project plan Prepare test scripts (SIT/UAT) Create End user Training Manual Hypercare strategy Go Live Data Analysis Design Sign-off Testing Readiness Go / No-Go Project Closure Scope changes are managed through change order process 38.

[Audio] SME Training (Train the Trainer) Logistics Scope Preparation Execution SME Training End to end System Location: Remote Schedule: DMS: 22nd July - Demo System access Training data 24th July Training on HRC provides CRD: 22nd July - 24th July application navigation customized training material based on design Participants Training through Business SMEs HighRadius test script execution Consultants.

[Audio] End User Training Scope Logistics Execution Preparation Mccain to update the End User Training Business SME to train the end users HighRadius to support HRC provided material from Mccain business perspective SME during the training sessions Training data Setup User access End users complete exercises Location: Remote Schedule: CRD: 19th Aug - 30th Aug DMS : 2nd Sep - 20th Sep Participants Business SMEs (Lead) End Users HighRadius Consultants.

[Audio] Q & A. Q & A.