1

We have around 8 projects and 8 testers in our organisation. The testers are usually aligned to the Development manager and report to him.

There is no proper process by which the testing can be stream lined. What happens is the developer managers forces the tester to test according to the developers schedule and the manager comes to defend them.

How can a process be set up in a small organisation which ensures good utilization of testers and also helps testers to learn new technology.

Faiz
  • 809
  • 4
  • 18
  • 32
  • @TESTasy, the question is totally different. Here 'which tool i should use for test management' is not the question, rather how should i organize team separately where they are not being managed by the same managers which are managing the developers. – Faiz Nov 21 '16 at 09:40
  • http://sqa.stackexchange.com/questions/18538/how-to-organize-a-qa-process-department

    http://sqa.stackexchange.com/questions/13917/establishing-qa-in-a-new-company-models-guidelines-to-follow/15351#15351

    http://sqa.stackexchange.com/questions/17878/how-to-set-up-a-software-testing-process

    http://sqa.stackexchange.com/questions/6772/are-there-standards-describing-the-different-processes-for-software-qa-on-softwa

    http://sqa.stackexchange.com/questions/9015/how-to-implement-qa-test-process-for-large-scale-application You will find many more posts that will answer your question.

    – IAmMilinPatel Nov 21 '16 at 09:45
  • Is your question about management or about the testing process? Also you asked a similar question earlier this year, what did you learn? Maybe first read a book like http://agiletester.ca/ then try some stuff and ask us smaller questions. We cannot define your process for you, this something only you and your company can do. – Niels van Reijmersdal Nov 21 '16 at 11:14
  • I'll take my chances with this one- it's not a duplicate, the op has opposition to change and what looks like zero responsibility and power – Rsf Nov 21 '16 at 11:25

1 Answers1

0

This looks almost like mission impossible in your case, cooperation is the foundation to any change.

But there is a small light at the end of this dark tunnel (hopefully not a train coming)- try to arrange demos, small presentations or even corridor chats and explain to those in charge why it is important to have proper practices.

Remember that managers usually react well to cost-benefit numbers, so try and show them that.

This is more complicated than what looks in first sight- you can start in the traditional way of showing the number of reopened bugs or bugs found in the field, talk about wasted time in context switching and lack of focus, show poor automation code since no one is responsible for it but at the end you will be asked how do you suggest to improve this and back it up with numbers.

Justifying dedicated testers as cost effective might not always be simple, personally I found myself not able to justify it even to myself and even obvious things like test automation.

TLDR; spread the word among those who have the power to decide

Rsf
  • 7,079
  • 1
  • 23
  • 36