Bug-Fixing Process

This process is used for fixing bugs in the process. It contains followed major steps:

• First of all - reporting the bug - somebody found the bug and should report it;
• Next step - is Tester Job - project Tester should be able to analyze the bug to classify it and make decision - is it bug, is it Feature :) is it duplicate for some other bug and so on. Tester should be able to reproduce the problem. During this step Tester may communication with bug-reporter as well as with Project manager to make correct decision
• After it bug (if it is really a bug) come to the Manager to make a dicision: in that milestone this bug should be fixed and who should do a fixing;
• Then Bug is assigned to Milestone and Developer, specified developer should make a fixing the bug. If, by some reasons, developer feel that this bug is not in his responsibility and it is better to reassign to to somebody else - or, seems it will not be possible to fix bug during assigned milestone and it is better to reassign bug to some other milestone - Developer should ask manager for Reassignment.
• After bug is fixed Tester should check - is it really fixed (since Tester was able to reproduce the bug and now know how to check it) If bug is really fixed - it is closed. If it is not fixed - it is rejected and returned back to developer.