The University of Texas at Austin is following a five-stage approach to implement Workday for our administrative human resources and payroll needs.
In this article, we explain the five stages of Workday implementations and where we are now in that process.
Where We Are Now
At the end of February 2018, the campus is at the tail-end of the Configure & Prototype Stage and is moving into the formal testing stage, which will begin in April 2018. In the Testing Stage all Workday processes will be tested from end to end, including integrations, reports, and downstream systems. Members of business process offices, technical system owners, and campus subject matter experts from colleges, school, and units will be engaged in testing.
It is in this stage that colleges, schools, and units (CSUs) will identify “Super Users” from their areas who will take part in End User testing. End User Testing not only ensures that the system is working properly, it will also ensure Super Users are confident in their ability to perform their daily tasks in Workday and can in turn explain the system to other users in their unit. Learn more about Super Users.
Workday’s Implementation Stages
Plan: The Plan Stage is devoted to activities like defining project scope, creating a charter and communications plan, and defining the roles and responsibilities throughout the project.
Architect: The Architect Stage is focused on gathering requirements for the new software, documenting current business processes, and hosting Design Workshops with Subject Matter Experts (SMEs) from across the organization. It is in the Architect Stage that the first prototype of the software is built.
Configure & Prototype: The Configure & Prototype Stage is an iterative Stage and is devoted to building consecutive prototypes of the new system and fixing any bugs or glitches along the way. The design decisions made during the Architect Stage are implemented while reports and integrations are developed and designed. If a design decision does not play out as expected when actualized in the system, Workday recommends changes that can be incorporated into a subsequent prototype. It is in this stage where training materials begin to be developed.
Test: The Test Stage is where End to End testing, End User testing, and Performance testing are performed. This means that the system functionality is evaluated to see if business processes operate as expected by the designers, tested by potential users, and the system is flooded with data to ensure it can handle the traffic anticipated after Go Live.
Deploy Stage: This final Stage leads to go live and is dedicated to rolling out training, preparing for go live, and making sure the organization experiences a smooth transition from the legacy system to the new system. The Deploy Stage does not end on the specific date identified for go live. It extends past go live with strategic plans and support mechanisms in place to help the organization adapt to the new system. A sustainment model is implemented, which will include support for campus after go live.
Related:
Preparations and Training for Workday to Ramp Up Throughout Spring 2018