WIXLIB

Workday R4Introduction to System Integration Test (SIT)TrainingOctober 2016

Table of ContentsProgram Test Schedule and StatusFacility and EnvironmentDaily AgendaRoles & ResponsibilitiesDefect Management TrainingAccess to Training Materials-2-

Overall Test Phase AprMayTest Planning6/20/16 – 8/30/16SIT Execution10/26/16 – 1/20/17UAT Kick-OffSIT Kick-OffUAT Prep3/20/17 –4/7/17Regression Prep1/23/17 – 2/24/17Performance ExecutionCycle 111/17 – 1/17Performance PrepCycle 19/16 – 10/16Performance PrepCycle 21/23/17 –2/15/17FDM ConverterPANDAFDM ValidatorRegression Execution2/27/17 – 4/6/17PerformanceExecutionCycle 22/16/17 – 3/21/17WD27 Execution8/2016 – 9/2016Payroll CostingCompareExecution4/10/17 –5/18/17GAP App Delivery8/1/16 – 1/23/17Integrations Delivery11/2/15 – 3/11/17Group 4Group 1Report Delivery12/14/15 – 3/7/17WD27 Planning6/2016 – 8/2016UAT Execution4/10/17 –5/18/17ISR Test Prep/Execution10/16/16 – 5/31/17Test Planning8/16 – 9/16P2JulGo-LiveSIT Prep9/7/16 – 10/04/16Group 2JunGroup 3Group 10Group 9 Group 6Group 7 / Group 8Group 5SIT HCM & ReportsUAT FIN & HCMWD28 Planning12/2016 – 2/2017-3-WD28 Execution2/2017 – 3/2017

Test PhasesSystem Integration Test (SIT)November2016 The process of testing all components of the application in a fully integrated testing environment that mimics the realworld use, including the interaction with external systems. This will involve executing end to end processes includingall the potential sub-processes, integrations to and from external systems and reports that may be run during theend to end process.Performance TestRegression Test (WD28 w/Financials)Impacted Systems Remediation (ISR) TestUser Acceptance Test (UAT)April2017 The process of completing the final validation of required business functions and flow of the system by end usersbased on business requirements. It is also an opportunity for the project to engage additional sets of end users in theproject prior to deployment and test the effectiveness of the training and documentation. UAT focuses on usercontrolled test scenarios and will provide insights regarding the understanding from the user community whether ornot the system is built to specifications, training enables the user to be successful, and the end product providesvalue.-4-

Table of ContentsProgram Test Schedule and StatusFacility and EnvironmentDaily AgendaRoles & ResponsibilitiesDefect Management TrainingAccess to Training Materials-5-

Test FacilitiesPlanningStagingAccommodations Location Command Center Kitchen Network / Power / Printer / Phone Training Center Bathroom Huddle / Meeting locations Projector / Screen Command Center Tables / Chairs Communications Zones LaptopsMeeting Rooms White / Black boards Snacks and Water Music Skype25 SP 1st floor1) Financial Accounting / ISP / PayrollCosting2) Financial ManagementLobby3) HCM / Payroll4) Procure to Pay5) Gifts6) Assets / Non-Sponsored A/R7) Integrations / Reports / Security8) Sponsored AwardsWinchester Ave.-6-

SIT tmld Workday tenant, Yale2Data as of August, 2016July payroll closedSecurity Access via SSO for self Testers have Proxy Native login for testing-7-

Table of ContentsProgram Test Schedule and StatusFacility and EnvironmentDaily AgendaRoles & ResponsibilitiesDefect Management TrainingAccess to Training Materials-8-

Daily RoutineSIT Welcome and Kick-Off (Day 1 only)MorningBriefing8:30AM – 9:00AMTest Execution9:00AM – 5:00PMDaily Status &Next Day PrepDaily Morning Meeting Distribution of materials Overall test status Blockers – existing and newly impacting Current days execution schedule Defect TriageMorning MeetingStatus& PrepTest Scenario ExecutionPost execution activities Enter manually submitted defects Update execution status Run daily metrics reports Develop and distribute daily status Prepare agenda for next morning meeting Prepare defect triage report------------------------- Rinse and Repeat -----------------------9-TestExecution

ManagementProgressMorning Briefing Sub-Team leads will meet with QA every morning to review current progress against the program schedule. Tactical plans will be discussed to resolve delays or prepare forescalation and support. QA and Sub-Team leads will pro-actively monitor scenario execution, program blockers, defects, and system dependencies discussing and communicatingforeseeable risks.Daily Summary Program status reports are developed and distributed daily after the close of the current days SIT execution window. Reports will summaries the current days activities and providean overview of the programs accumulative test progress. Information will be distributed by email to all program management and supporting staff.DefectsIn Session Issue Tracking Sub-Team leads will determine if issues reported by testers are defects or change requests and summarize details during the sessions in conjunction with the tester. The summaryand all supporting detail including the test number, and required HP-ALM fields will be emailed to QA for logging into HP-ALM.Triage When possible, ticket assignment will be made during testing sessions and provided to QA . This will be done when the Gatekeeper is available in the testing session to discuss andreview assignments. Otherwise assignments and ticket details will be updated by the Gatekeeper in advance of the triage meeting scheduled for the following day. Ticketassignment will follow the defined matrix.Defect Review & Tracking HP-ALM defect triage meetings will be held daily and will focus on defect tickets as follows: New ticket review beginning with the most critical issues Aging defects review beginning with the most critical issues Open questions and requests for assistance coordinating resolution on defects from the team leads- 10 -

Table of ContentsProgram Test Schedule and StatusFacility and EnvironmentDaily AgendaRoles & ResponsibilitiesDefect Management TrainingAccess to Training Materials- 11 -

Roles & ResponsibilitiesStakeholders involved in the defect management process should be aware of their respective roles and responsibilities, as indicatedbelow, to ensure that key activities within the defect management process are accounted for.General ResponsibilitiesRolesTesterALM Gate KeeperTest Execution Support(Yale and Deloitte TeamMembers) Responsible for the execution of test scenarios Raise issues and defects found during testing Review the defects logged within the last 24 hours. Triage defects to appropriate technical and functional teams for resolution Report the defect status on a daily basis to Test Lead Assist testers with completing test cases by providing guidance on WD functionality andnavigation during the testing sessions Coordinate with testers to define and document defects during the testing sessions Review, fix, and/or reject defects Proactively participate in defect triage meetings and tracking defect statusProject Test Lead Coordinates defect triage meetings and monitors defect resolution progress Serve as the point of contact on test execution status and reviews defects for validity andseverity Coordinate with development team on progress of defect fixes and escalates issues Coordinate and communicates upstream and downstream defect consequences Accountable for overseeing defect fix progress among Development and Business teamsSub-Team Lead Accountable for the execution of test scenarios within their domain Provide domain knowledge necessary to assist testers with the execution of test scenarios Validate the integrity of defects within their functional area- 12 -

ALM Support Team ALM Tickets will be categorized by Functional Area / Business Process Names highlighted in Red will be the primary assignee of all ALM Tickets Deloitte Support team members will also monitor ALM Tickets by Functional Area to ensure ALM Assignees have support towork through and resolve issuesWorkstreamWorkstream LeadsYale Sub-Team LeadsDeloitte Sub-Team LeadsFinancials Jacqueline Tucker-- Jeffrey BeechamFinancials – Banking and Settlement Jacqueline Tucker Agnes Siniscalchi David LaneFinancials – Non-Sponsored A/R Jacqueline Tucker Deb Armitage Yuji SuzukiFinancials - Business Asset Account Jacqueline Tucker Courtney Connors Yuji SuzukiFinancials – Procure to Pay Jacqueline Tucker Rob BoresTracy StricklandNicole Riccitelli N/AFinancials – Financial Accounting / ISPs Jacqueline Tucker Andy Sgambato David LaneFinancials – Gifts Jacqueline Tucker Keith Della Rocco Sandra StorrodFinancials – Payroll Costing Jacqueline Tucker Michele Greenhouse Charles WilliamsonFinancials – Sponsored Awards Jacqueline Tucker Bob Davis Sashi GolaganiFinancials – Effort Certification Jacqueline Tucker Sandy Vitale Marnie FultonFinancials – Financial Management Jacqueline Tucker Shirley Chock David LaneFinancials – FMD / COA Jacqueline Tucker Liz Bilodeau N/AFinancials – Security Jacqueline Tucker Steven Fielding N/A- 13 -

ALM Support Team (cont.) ALM Tickets will be categorized by Functional Area / Business Process Names highlighted in Red will be the primary assignee of all ALM Tickets Deloitte Support team members will also monitor ALM Tickets by Functional Area to ensure ALM Assignees have support towork through and resolve issuesWorkstreamWorkstream LeadsYale Sub-Team LeadsDeloitte Sub-Team LeadsHCM Ron LipkinsAnna-MariaHummerstone HCM and ACM Teammembers N/ATechnology Darrell Cook Arun DarwarKevin Quigley Brad CobbsReporting Kathleen Broderick Tzu-TzuPoojithaMichael N/AData Warehouse Angela Chen Erin TotzRobert Scott N/ASecurity (HCM) Ron Lipkins Ron Lipkins N/ASecurity (Financials) Steven Fielding Steven Fielding TBDTesting Jason Shuff Jason Shuff N/AOrganization Management Kathy Byington Sarath Kraus Tomislav BeslicWorkday Setup Data (HCM) Ron Lipkins Ron Lipkins N/AWorkday Setup Data (Financials) Troy Morris Troy Morris Jeffrey BeechamConversion Rodney Brunson Rodney Brunson Andrew DininImpacted System Remediation Linda Faust System Owner N/A- 14 -

Table of ContentsProgram Test Schedule and StatusFacility and EnvironmentDaily AgendaRoles & ResponsibilitiesDefect Management TrainingAccess to Training Materials- 15 -

ALM Process Flow- 16 -

Defect Management OverviewDefect Review & Tracking through HPALM Testers / team members involved in testing will be trained for ALM prior to testing and will be given access to ALM. HPALM defect triage meetings will be held daily and as and when needed. will focus on defect tickets as follows:‒ New ticket review beginning with the most critical issues‒ Aging defects review beginning with the most critical issues‒ Open questions and requests for assistance coordinating resolution on defects from the team leadsTriage When possible, ticket assignment will be made during testing sessions and provided to QA . This will be done when the Gatekeeper is availablein the testing session to discuss and review assignments. Otherwise assignments and ticket details will be updated by the Gatekeeper inadvance of the triage meeting scheduled for the following day. Ticket assignment will follow the defined matrix.In Session Issue Tracking WD functional workstream SMEs will determine if issues reported by testers are defects or change requests and summarize detai ls during thesessions in conjunction with the tester. The summary and all supporting detail including the test ID, test name, and required HPALM fields will beemailed to QA for logging into HPALM.Resolution Management Functional leads in conjunction with their team leads are expected to track and manage the resolution of issues/tickets and t o proactively updateHPALM comments and status. The Test Lead in conjunction with the PMO when needed will assist with the coordination of issues that crossworkstreams.- 17 -