Over the past few years some seriously amazing testers have joined the uTest community, and today we have one of the most talented and diverse testing communities in the world. Some of our testers have taken us by surprise with their skills in areas like load automation, usability testing, and even general leadership. It’s that last area that has us most excited and is the reason behind today’s release of the uTest platform.
Test Team Lead
For a while, we have experimented with giving select and trusted members of our community additional privileges to help make our projects run more smoothly. Testers have been quietly helping our project managers with tasks like answering questions on projects, keeping testers focused and in scope, and making sure bugs match the customer’s expectations. With version 3.7 of the uTest platform, we have formalized that experiment into a new role within the community – the Test Team Lead (or TTL for short).
The TTL is not a replacement for a uTest project manager and their role will be mostly behind the scenes from a customer point of view. However, their contributions will be instrumental in helping to deliver high-quality testing results. Project managers will rely on the TTL to handle background tasks necessary to keeping a diverse community of testers in-line and on-task. This will free up the project managers to better help customers manage their test cycles, understand their bugs, and get the most from the uTest community.
Test Team Leads are select members of the uTest community who undergo an extensive training process. Among our best testers they are the best, but it is more than just their testing skills that qualify them as a TTL. They must also demonstrate leadership, communicate clearly, and be effective at organizing and motivating other testers.
Changes in 3.7
Starting in v3.7 of our platform, uTest project managers will be able to invite a Test Team Lead to projects of their choosing. The Test Team Lead will join the project just like any other uTest project, but their role will be different. Instead of reporting bugs or completing test cases, they will be helping other testers, answering questions, and keeping the project in scope.
TTLs will have a greater degree of privilege within the uTest platform, including the ability to use Tester Messenger to communicate with other testers and the ability to use Customer Notes to leave comments for project managers and customers. A TTL will not be able to approve or reject bugs, and project managers will still be responsible for the overall success of a test cycle as well as be the primary point of customer contact. Not every test cycle will require a TTL, and project managers will use their discretion to decide when a TTL will be needed.
While version 3.7 enables this new role, this is a much bigger evolution for our crowdsourced testing platform. We’re excited that our community will be taking a more active role in organizing itself, and we think this is a great way to inspire and deliver excellence.
While we have some good ideas in our product pipeline, we’re always looking for more. Do you have an idea for future product releases? uTest community members can join our tester forums and check out our Platform Feedback section. Customers can contact their project manager directly or drop us a line.