Re:It Takes 6 Days to Change 1 Line of Code (2015)
by azernik on Tuesday December 06, 2016 @09:08PM
(#13119951)
This is inevitably what happens when the people reporting the issues get to decide their priority (I've seen this even in a two-person dynamic). You have to have discipline, and you usually have to have an impartial outsider (to the issue at hand) who doesn't care about other people's panic to actually set priority levels.
[ Parent
| on HN ]
Re:It Takes 6 Days to Change 1 Line of Code (2015)
by aiiane on Wednesday December 07, 2016 @01:16AM
(#13120828)
I've seen systems that have two fields, e.g. priority and severity. Where severity is "how important the client thinks it is" and priority is "how important we think it is".
Re:It Takes 6 Days to Change 1 Line of Code (2015)
by Pxtl on Wednesday December 07, 2016 @05:43AM
(#13121678)
Our system has another one: Who it impacts. Does it impact a user, a department, or the entire organization? The difference between "my crap's broken" "our crap's broken" or "everybody's crap's broken".