Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
black-kite3093336dWhere I used to work, highest priority was 1. You had to drop everything and get to work on that issue right away….. unless, of course, there was a priority 0 that took precedence over anything else
-
TeachMeCode5175336d@MammaNeedHummus tickets raised by devs are sent to backlog and rot for eternity
-
TeachMeCode5175335d@Oktokolo we know the project managers condemn the sin of tech debt tickets bc we care about architecture when it takes a million years to add anything to the system without more weird bugs happening. But we know everyone wants everything fast like a crappy McDonald’s burger that tastes great but leads to plaque buildup in the long run!
-
tellikakneezus9333dThere's a high priority ticket opened by Ben. Then there's a high priority ticket opened by Steve
-
hjk1015731330dLove the Triage systeem. Very clear and you usually don't need more than 4 colours.
In a lot of situations you can bring it down to two or three classifications even. When you can get away with it go for the lowest amount.
We basically have two priorities. 1 urgent e.g. something is not worked. 2. Not urgent, just improvements. Of course we order work so non urgent stuff also gets prioritised naturally for collaboration with other teams and momentum.
Medium priority
High priority
Urgent priority
Immediate priority
Maximum priority
Absolute priority
Did I get the ordering right? This is hard
rant