Quarterly Objectives Help
Hello there everyone,
This is my first post as I just joined today. I have used the search feature in attempt to find something along these lines, to no avail. QA is a pretty new unit at my company (only consisting of myself). The only method that we currently use is a testing matrix in a Google spreadsheet that contains all of our test cases. I make a fresh copy every week, input results, and save it in my Drive every week. Now to the purpose of this post. Each employee here comes up with personal quarterly objectives. However, with our lack of deep knowledge of QA, I am having some trouble thinking of some good objectives for myself and QA. Side note, any sort of objective along the lines of I would like less than X number of bugs in this quarter are considered too simple. We are looking more for ways to improve the quality or efficiency of the QA process or workflow or even implementing some new method or tool. We are not quite on the level yet to look into automation and any bug tracking tools that I have looked into seem to be way too much for what we need. Any tips or advice are much appreciated, just sort of looking for somewhere to start. Thank you.
Any sort of objectives along the lines of "less than X number of bugs" or "execute X number of test cases" are not the type of things you want to be adding - you're not responsible for putting X number of bugs in the code (or for fixing the bugs, for that matter!) and KPIs along those lines tend to become something management will use to measure you, you end up gaming, and it becomes a vicious circle.
This is where you need to head, in my opinion. Take a look/forecast at where the system-under-test and the product team is going to be in 6 months or 1 year (perhaps in conjunction with the product owner or project manager). Perhaps you're not ready for automation yet, but this may give you an opportunity to be ahead of the development curve and start to investigate tool options and implement some training in your objectives so that you're ready in six months' time. The same goes for bug tracking tools and efficiency processes - if the project is growing, do you need a more efficient structure for your test cases? Would something like an internal Wiki be useful? Can you move into test environment setups? Do you want or need to implement a better test preparation plan and release schedule?
Originally Posted by tsmothersocv
You'll have some boring objectives that you need to meet every quarter, but look for other opportunities so that you're in a position of personal growth in 6 to 12 months' time; it's not "what do I need to do right now", but "where would I like to see myself / the team in 6 months".
Thank you so much for the reply this really helped me pick a good direction for my objectives and I believe next quarter will be an extremely exciting one for me! Much appreciated