Software test processes can be difficult.
Many companies struggle with it.
There are so many paradoxes in getting the thing build right... sometimes it's even hard where to begin the improvements in the software test process.
The longer you are a software tester, the better you know that it is true. And also the better you know what you can do about it. It least that's my experience...
I find that, improving the software test processes is much like re-arranging a bookcase....
Many companies struggle with it.
There are so many paradoxes in getting the thing build right... sometimes it's even hard where to begin the improvements in the software test process.
The longer you are a software tester, the better you know that it is true. And also the better you know what you can do about it. It least that's my experience...
I find that, improving the software test processes is much like re-arranging a bookcase....
Most of the companies I worked for have software testing 'somewhat organized'. They can find what they need, and they work with it, but it's not optimal. Then they start to improve the processes. Which in many cases leads to more clutter for a while. (2)
Then sadly, what I have experienced is that a lot of companies stop the test improvements because for some managers or CEO's it looks like "ohw now it's even worse, this is not an improvement". And they quit or stop putting effort into it.
Some companies on the other hand, -but not the bigger part-, continue and after a while there software processes (bookcase) is a lot more optimized. (3)
Then sadly, what I have experienced is that a lot of companies stop the test improvements because for some managers or CEO's it looks like "ohw now it's even worse, this is not an improvement". And they quit or stop putting effort into it.
Some companies on the other hand, -but not the bigger part-, continue and after a while there software processes (bookcase) is a lot more optimized. (3)
