After your technical upgrade is completed, it is always advisable to conduct a dry run. By upgrading a copy of your live site you can identify any potential issues and resolve them prior to going live. In addition, make sure that adequate support resources are in place should a sudden demand on their time arise after release of your upgrade.
Stage 2: Testing
At this stage, an experienced testing team evaluates whether a software system satisfies functional and non-functional requirements, known as user acceptance testing (UAT). Quality Assurance Engineers set up an environment that replicates business use scenarios; unit tests are then run before more complex combinations of units are tested in the system itself. Finally, test reports detailing test results are issued and shared with developers and stakeholders.
At the outset of this stage, QA engineers create test cases – detailed accounts of how to assess specific features such as preconditions, input data and actions to be taken, expected outcomes as well as expected preconditions and actions taken against that feature. One of the main outputs at this point is an RTM which connects requirements with associated test cases.
Stage 3: Deployment
Once all code and database issues have been addressed, a new version can be fully implemented. This requires an all-out effort from users in order to overcome their natural resistance to change and adopt the new software and processes. It may also be prudent to keep running your existing ERP alongside it temporarily as a safety net against missing any critical processes when transitioning data between environments.
As with the installation and testing stages, risk management during an upgrade process should be managed proactively. This begins by identifying potential threats, followed by their assessment and mitigation planning. These may include risks such as:
Stage 4: Go-Live
The go-live, or deployment, phase of any technology project is unquestionably of the utmost importance. It marks the time when new products or services transition from development and testing into actual use and deployment in real life – often after months or even years of preparation, planning, execution, monitoring, control and feedback loops with internal and external stakeholders.
Start thinking ahead to ensure a smooth transition from go-live to maintenance and support phases, including creating a transition or handoff plan and closing all User Acceptance Testing items or notifying for further action. Also establish an emergency contact list in case urgent issue resolution or escalated situations arise during go-live period.
As part of this step, it is also essential to assess what impact an upgrade will have on users – this may range from system shutdown to altered workflow in specific departments – and ensure all affected parties understand its implications. This information must then be communicated back out.
Once the transition to a new Digital Asset Management system has begun, it’s essential that ongoing issues be monitored and supported as they arise. One effective method is scheduling regular wrap-up meetings during the go-live period to address issues as they arise and share lessons learned for improvement during future upgrades. Involving your project team members during these meetings is also advised in order to share any lessons learned and identify areas for development for next time around.
At this post-go-live stage, it may also require additional support resources – depending on the scope of your upgrade – in order to address any unexpected issues that may arise. These could include technical support for high priority issues; subject matter experts to assist with process decisions; and super users/champions for new or inexperienced users.
