The idea of implementing a new test management tool and migrating all of your test data can be daunting. But more often than not, what gives our customers pause is the idea of rolling out this new tool to hundreds, or sometimes even thousands, of testers. QA leaders may fear that users will be resistant to change, or that learning a new tool will cause delays in time to market. But there are several steps you can take to ensure a smooth test management tool rollout process and minimize workflow interruptions.
3 Tips for a Successful Test Management Tool Rollout
1. Define QA Training Needs
Team leads should define training needs for administrators, end users and collaborators before migration begins and be sure everyone who touches the tool is aware of any changes in workflow or process. It’s also a good idea to set up a central location for adding and sharing training materials.
Tricentis offers training that allows qTest administrators to both learn the new tool and discuss best practices for rollout and onboarding the rest of their team. During training, Tricentis’s experts give administrators tools, recommendations and best practices for training the rest of the team. Tricentis also provides recordings of each of these one-on-one training sessions, which can be shared with testers or kept on file for future reference.
2. Centralize Information About the New Test Management Tool
Before QA leaders at a large financial services company rolled out qTest, they set up a web portal that includes training materials, resources and guidelines for getting started. Managers shared the web portal with their teams in advance of migration, which gave testers easy access training videos, links to relevant pages on the qTest support site and an FAQ section, which helps testers across different teams share knowledge, get help and see how others are using qTest.
Tricentis’s monthly training schedule is also accessible from the web portal, and users are encouraged to attend each training webinar or watch the recordings, which are posted as mp4 files after each event. The web portal is updated regularly with new materials and updates to the FAQ. The section is open and editable, so both testers and managers can ask and answer questions
3. Host a Training Event for All Testers
To create a clear migration path for all users, leaders of large-scale QA and development organizations should consider hosting a town hall or in-person training session. The event can serve as the official retirement of the old tool and kick-off of the new platform. Making it a formal event can help create excitement about new capabilities and opportunities for collaboration, which in turn helps drive adoption.
An Australia-based financial services organization with more than 3,000 testers recently hosted a town hall to introduce testers and developers to qTest. The official event was planned well in advance, so teams had plenty of time to RSVP and plan their schedules around it. Tricentis product and migration experts attended the event to meet the team, demonstrate key qTest features and answer questions.
However you plan the transition, it’s best to ensure users are prepared in advance of migration, understand how their workflows will be affected, and have access to the materials they need to begin making the most of the new tool.