How to write OKR for test engineers to improve quality?

As a test engineer , Want to improve the quality of the products they are responsible for , It should be done mainly in two directions , The first direction is to improve test coverage , Another direction is to improve the efficiency of collaboration with development . But those who really do the test know , Completing the testing work that must be done in an iteration has taken up most of our time , Therefore, in order to better improve the quality, we can only do it in spare time , If you don't plan well, it's easy to put it on hold . Based on this situation , We suggest you use OKR Objective management method to plan the daily work , To improve themselves and bring greater benefits to the team , So the first step is to learn to set up these OKR, Let's share some cases .

Test engineers improve the quality of OKR How to write ？
Improve test coverage ：

O： Improve test case coverage , To ensure product quality

KR1： Review the common test cases of all basic components

KR2： Finish sorting out all general test scenarios of the product

KR3： Share and test the test method at least three times

O： Improve the working ability of basic function test engineers

KR1： Complete the test case sorting of all modules of the whole product

KR2： Complete at least two rounds of testing of the whole product

KR3： Conduct at least three experience sharing meetings for senior test engineers

O： Reduce two rounds of testing new bug Number , To ensure the project cycle

KR1： Complete at least two iterations of the function to evaluate the impact points of the existing functions

KR2： The missing scenario of the test case shall not exceed 3 It's about

KR3： One round of omission occurred in the second round of test bug The quantity cannot be more than 5 individual

Improve collaboration efficiency ：

O： Improve the efficiency of the test team , In order to guarantee product quality more efficiently

KR1： Determine a set of online affairs promotion system without implementation problems

KR2： Sort it out at least 30 Solutions to common problems

KR3： In this cycle, there are no online transactions that have not been advanced and resolved on that day

O： Build an efficient R & D team

KR1： Improve a complete set of iteration process specifications

KR2： In the second quarter, there was no delivery delay due to team cooperation

KR3： In the second quarter, there were no online transactions caused by team cooperation

If you are still bothered and want to make a promotion, but you are always not on the agenda , You can use OKR Start planning your quarterly improvement goals now . If you haven't learned to set OKR, You can refer to Tita OKR Templates in the case base , All walks of life OKR There will be cases for reference , Act now ！

Of this picture alt Attribute is empty ; The file named 1624809652-20210628000052169.png

Learn more about how customers use Tita The platform achieved results , Apply now 《 Product presentation 》 .