You could put the direct image link https://i.imgflip.com/7x89o9.jpg into the post URL to view the image directly through lemmy.
Thanks, that's better
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 NOW
That'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.
Everyone thinks service desk exists for them and them alone.
I understand that all the networked phones aren't working and the PoS is no longer accepting valid orders and the server backups are all corrupted and half the company cannot access emails while the other half are replying to emails that's causing a weird data sync issue and all the printers are jammed...
But can you PLEASE move my ticket request of "Right Mouse click makes funny noise when I click it exactly 7 times" to the top of the stack? It's disrupting my flow. Thank you you lazy fucks.
I LITERALLY cannot do my job while this is happening!
it's dns
What about the unicorn m e d i u m p r i o r i t y
That's low priority, but someone has complained so it got "bumped up"
High priority is usually a company wide outage, so... yeah.
But did you try turning off and on again?
Hello shadow IT.
Now even more Silos. Thanks IT
Shadow IT is a management failure, not an IT failure.
Personally im inclined to let buisness units blow themselves up if they like. I'll pick up whatever pieces I can, but if I can't, all well. If we dont support it and you use it, things get really simple for us.
IT mangement is still IT.
But it's more gatekeeping by IT in my experience. Old roles that can't hand over control, so they get piles of work that they cannot handle..
Hence "LOW PRIORITY"
Management is always management first, but sure.
Gatekeeping at the lower IT level comes from "responsibility." Lots of people want unlimited power, but the minute there is an issue, they throw the problems back over the fence, fingers a' pointin'.
If a different part of the org takes actual ownership, I'm always happy to let them fully control whatever. When you do the backup/monitoring/logging/provisioning/licensing/securing/load balacing/etc, go nuts.
It's why shadow IT is fine by me, but if you want to fuck shit up and then try to tell me to clean it up, nope nope nope.
This is why I do everything myself if I have permission.
Post funny things about programming here! (Or just rant about your favourite programming language.)