When Workday releases updates of new features and improved functionality, companies often view the changes as daunting to implement. After all, Workday is integrated with so many overlapping systems and processes within an organization, a wrong move can have a disastrous domino effect. Updating your Workday system, however, is crucial to getting the most out of it for your large investment. With Workday 32 around the corner, here is how to perfectly plan for a Workday update and ensure it does not interfere with your day-to-day operations.

Think ahead

Your testing team should be prepping for the Workday update at least a month before the preview period for the update starts. During this time, an in-depth plan should be made on what is required to be tested and the potential effect it can have on departments and processes as well as a strategy as to how to go about testing.

Expand on the strategy

When you are planning your Workday testing strategy you need to set your testing tasks according to importance. For example, the testing that is most important will involve processes that affect the day-to-day functioning of your organisation. Think about the which operations would severely impact the business if something were to go wrong (processes related to security and finance, for example) – these are the most important areas your need to concentrate on in your testing schedule.

After accounting for these tests you can focus on feature updates that will impact other aspects of Workday in your current usage as well as new functionality that could help improve your operations.

Forming a testing team

Your staff in charge need to be briefed on why testing correctly and carefully is so important. Explain to them the integrated nature of Workday and the consequences of systems malfunctioning and how it can affect the whole organisation. Each testing team member should be keenly aware of their responsibilities and the timelines they have to adhere to, as well as who to go to in case of an escalation, in order for a smooth testing to take place.

Building a test plan

This is an in-depth plan which will include every aspect of your testing and responsibilities of those on your testing team. This plan will also set a timeline for each task to be prepared for, implemented, completed and checked. Once you have a detailed test plan ready, share it with stakeholders, getting everyone on board before proceeding. Don’t forget to anticipate some mishaps along the way and factor in some additional room for downtime should something not go according to plan. In cases like this, you’ll need additional hours for retesting and investigation. You don’t want to upset your whole schedule for small bumps in the road.

Plan for each test

Each test performed will require a specific set of information (also called a test script) for the tester to be fully prepared. For example, this information will include everything that is needed in order to perform the test, a description of the test, the tester or staff members in charge and involved, instructions on implementing the test and what results are anticipated. These guides will make it much simpler for your testing team.

Think about automation

Do away with the hassles of testing all together with modern automated testing that can run hundreds of tests in a matter of hours instead of the days and weeks that manual testing command. Manual testing also requires your staff to be occupied during that time it takes to oversee tests. With automated testing, you can eliminate the occurrence of human error and get in-depth error reports. The testing does not interfere in any way with ongoing processes as it is conducted independently, allowing day to day operations to proceed without a hitch.