We have a bug process that is currently being worked.
We have 3 levels of bug:
- P1 bug: Bugs that prevents users from working. They must be solved on the spot.
- P2 bug: Bugs that are impacting but users can work
- P3 bug: Bugs that are not impacting and where users can work.
P1 is mandatory and must be dealt on the spot. But for for P2 and P3, we judge on a case by case basis.
With the 3 levels that we have, the team has the tendancy to work on more pressing new developments asked by the customers, instead of dealing with P2 and P3, which is almost like non urgent.
Questions are the following:
Should I add another level of priority, like having a P4?
Should I also assign them targets for dealing with non urgent tickets like in this week, when not assign a coding task, you should treat at least 1 P2?
Currently, we do not have objectives like I raised above but my concern is that giving them such objectives can be brutal. The thing that is certain is I need to talk to them about the objectives, the team like to be involved in discussion especially when we are setting objectives.
I was proposed this question in term of similarity. However it is not similar, at all.
My question is how to have people deal with bugs, without imposing a strict agenda and yet to have it resolved. So no, the question implied does not help me. Still, thank you.