Ppl misjudge the implications of those priorities.
Low priority: your shit is broken, well deal with it during office hours
Medium priority: a whole department’s shit is broken. We’ll stay longer to fix it if needed.
High priority: EVERYONE’S SHIT IS BROKEN HOLY FUCK, SEVENTEEN TECHS ARE IGNORING THE SPEED LIMIT ON THEIR WAY TO FIX THIS RIGHT NOWThat’s IT. In software development?
Important stakeholder wants something: drop everything that’s top priority.
High priority: we’ll get to it next sprint, an important stakeholder wants something right now.
Medium priority: we’ll get to it after all the high priority items are done, but we’re getting an important call from another important stakeholder right now, we’ll get back to you about timelines.
Low priority: you’re starting to sense the pattern here, right?
Code quality, documentation, testability, test automation: lol
I just wish they would call it “normal” instead of “low” priority.
Is the site down? Is email down for everyone? Is CSuite/ the entire business operation down? Then it’s high priority.
Otherwise it’s low priority.
