• Norgur@kbin.social
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    1 year ago

    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

    • Pxtl@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      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