Project Designees and SMEs Friday completed the second week of Workday Prototype 1 Unit Testing for Human Capital Management (HCM) and the first week for Finance.
General observations about this stage of testing:
- Because Unit Testing is designed to aggressively test our configuration, testing is conducted looking for both successes and failures of the Business Processes. At this stage of the Prototype process, it is normal to experience failure rates of approximately 40%.
- Testing is guided by “test scenarios,” previously developed, pre-defined scripts that test our configuration and show which processes are working as designed and which processes need adjustment.
- Test scenarios designated as “closed” either have passed or been “removed.” Removed scenarios have been determined to be invalid for our testing needs.
Statistical highlights of Week 2 of testing:
HCM
- HCM has a total of 4,742 test scenarios for all prototypes and stages of testing.
- Of that total, HCM’s goal was 1,307 scenarios by the end of Week 2. It achieved 96% of that goal by closing 1,249 scenarios.
- The failure rate for Week 2 of HCM testing was 32%.
Finance
- Finance has a total of 1,540 test scenarios. (The number is smaller than HCM’s because our HCM Workday configuration has more Business Processes to test, and also includes the Payroll function.)
- The goal for Finance’s Week 1 of testing was 214 test scenarios. A total of 158 were closed, or 74% of the goal.
- The failure rate for Week 1 of Finance testing was39%.
Integrations Underway
Integration is the process that connects different, often dissimilar, information systems (like the ones across our institutions and System Administration), so that the data in each can become part of our larger, comprehensive Workday configuration, and will correctly share data and work together. We are working on more than 50 integrations across our Workday configuration.
We have begun gathering requirements and design documents to govern the 29 separate employee benefits integrations. We also have started work on the interface we’ll need to ensure that Workday recognizes the User IDs used in PeopleSoft Campus Solutions, our student system.
The Team this week also began gathering necessary requirements and designing integrations to accommodate our banking and journal/voucher data.
Upcoming
The remaining testing schedule for Prototype 1 is:
- P1, Phase 1
- Jan. 25-28
- Feb. 1-4
- P1, Phase 2
- Feb. 8-11
- Feb. 16-19
- Feb. 22-25
Beyond P1, the anticipated testing timeline is:
- System/End-to-End Testing (Spring-Early Summer): Testing of all of our Business Processes in Prototype 2. Business Processes are the sequence of tasks employees complete to accomplish a business objective, such as hiring an employee or paying an invoice. This stage of testing will seek to confirm that notifications, approvals, accounting, etc., work correctly. It will involve the Project Team, and the Project’s Designees, Subject Matter Experts and implementation consultant Sierra-Cedar, Inc. (SCI).
- User Acceptance Testing (UAT) (Mid-Summer-Early Fall): Executing end-to-end test scenarios in Prototype 3. It will involve campus employee-representatives, the Project Team and SCI.