(Meaningless graph representing nothing)
If I don't work – how to know if I am not doing my job? Got similar question couple days ago, and we started small discussion about tester and how to check their progress.
Imagine situation – there are 100 bugs and release is in a week. Till release date – 25% of bugs was reopened and 30% had to be tested in release period. Developers starts to fixing reopened bugs, merging them in release branch. Release is going on, everybody working their asses off. And finally regressions are done and release is sill not fully tested. More bugs are merged there. There was so much things to do in a week, that correctly test expected bugs amount was to difficult task.
So did I done my work or not?
Two weeks before release – there was 80 bugs fixed, but not tested. In next week 20 more appeared, was fixed, but not tested. And then I jump to work. In this situation I have one question – what I did last three weeks?
It doesn't matter what, but definitely not my job.
If in this case my manager would have looked to amount of new code lines in release, I think I would be fired. To check progress is not hard, but this need to be done, and even if I don't have manager, I should check my progress just to know if I could sleep next couple days, or I will be working as horse to catch up.
To make your whole team sweat – just do Your job late. It definitely will make every one enjoy extra stress.
This case is just theoretical idea we discussed, and most of thoughts was not even mine. But using both approaches can be useful – for example if You hate Your job and coworkers, well just do what You wouldn't do if You appreciate Your job. Or just extra stress before Christmas is useful for every one.
Imagine situation – there are 100 bugs and release is in a week. Till release date – 25% of bugs was reopened and 30% had to be tested in release period. Developers starts to fixing reopened bugs, merging them in release branch. Release is going on, everybody working their asses off. And finally regressions are done and release is sill not fully tested. More bugs are merged there. There was so much things to do in a week, that correctly test expected bugs amount was to difficult task.
So did I done my work or not?
Two weeks before release – there was 80 bugs fixed, but not tested. In next week 20 more appeared, was fixed, but not tested. And then I jump to work. In this situation I have one question – what I did last three weeks?
It doesn't matter what, but definitely not my job.
If in this case my manager would have looked to amount of new code lines in release, I think I would be fired. To check progress is not hard, but this need to be done, and even if I don't have manager, I should check my progress just to know if I could sleep next couple days, or I will be working as horse to catch up.
To make your whole team sweat – just do Your job late. It definitely will make every one enjoy extra stress.
This case is just theoretical idea we discussed, and most of thoughts was not even mine. But using both approaches can be useful – for example if You hate Your job and coworkers, well just do what You wouldn't do if You appreciate Your job. Or just extra stress before Christmas is useful for every one.
Your friendly neighborhood Tester.
Komentarų nėra:
Rašyti komentarą