PO 1C SIT2 v. 1.2

1. PO 1C SIT2v. 1.2

2. Content • 1. SIT2 Governance Structure • 2. How to design Test Scenarios for SIT2 • 3. Execution of SIT2 • 4. Defect Management on SIT2 • 5. Compliance and Audit on SIT2 • 6. SIT1 / SIT2 Transition

3. Organisation of SIT2 • 8 SKU testing groups + BI, APO & CONTR • Permanent, testing groups • Permanent dislocation (desk or room) • Created as OTC/FICO/SFA groups • Scenarios are scoped by SI Leads, coordinated by Business Experts • SI leads chose Test Scenarios in scope for SIT2 • Business Experts coordinate testing, ensure flow and execution • SKU groups each test their own Test Cases within the scenairos • PMO leads and Functional consultants support test • PMO leads scope week-by-week and help BEs to plan testing • Functional Consultants support SKUs with execution • BEs, BI, APO and CONTR leads participate on the daily SIT2 standup • Standups continue • Business Experts maintain a ATC board of Scenarios • Progress measurement • Progress is measured with same metrics as SIT1, but by SKU team

4. SIT2 Governance Structure Execution Support • Legacy • GCOE Tech • Data Migration • Functional Consultants • ?

5. 1. SIT2 Roles and Responsibilities

6. SIT2 Coordination in practice

7. 2. Organisation of SIT2 • Scenario scoping • Scoping is done week-by-week • Scope / scenarios are set by PMO leads per group weekly • Negative testing • Negative test scenarios are tested by Consultants • Day-in-the-life • Day-in-the-life test is not done • Reporting • Same reporting as on SIT1, same metrics

8. 2. How to design Test Scenarios for SIT2 • Scenario developmen in Excel • Scenarios are written as on SIT1 in Excel • Scenarios are divided into Test cases by SKU group • More detailed step description and test data • Will be tested by SKUs • Will be the training material for SKUs • therefore • Scenarios must be described in adequate detail • Test data must be specified for each scenario but in ONE file • New test types in scope for SIT2 • Negative Test Scenarios must be developed • Archiving test scenarios and/or test steps must be written • SIT2 test scenarios are to be uploaded to e-room • A SIT2 folder is created on e-room • A folder is created for each test scenario to load Test Cases • RICEFs and Archiving enable RICEFs • Test lead to verify/audit that all RICEFs are at least once in SIT2

9. 3. Execution of SIT2 • Execution in ALM • Each SKU has access and is trained in use of ALM • Test scenarios are executed in ALM • Control steps are executed by SKUs but passed/failed by Controls group • Legacy steps • Legacy resources are secured by Int. Leads with S.Somov • Defects are raised in ALM by SKUs

10. 4. Defect Management on SIT2 • Dedicated defect manager is assigned with the following tasks • Ensure compliance of raised defects with guidelines (description, screenshot, RICEF required?) • Ensure that consultants raise TPR/CRF/Config doc where required; add TPR/CRF/Config doc name to defect • Find&Kill duplicates • Help/correct assingnee to speed up resolution • Group defects for daily defect meeting • Daily defect meeting • Eeach evening a 1hour call is conducted 17.00-18.00 • Mon and Thur with all members of all teams • Other days with core team • Critical and High defects are actioned daily

11. 5. Compliance and Audit on SIT2 • ”Compliance manager” role is assigned with daily check of • Correct setting of status of test step • Actual result filled in – always • Doc numbers registered • Screenshots for Control and last steps are taken • Defects are raised for failed steps • No defects are raised for passed steps • No new runs are started accidentially • Daily follow up • Business experts to receive reports from Compliance manager daily • Follow up with own teams to correct mistakes day-to-day