• Arghblarg@lemmy.ca
    link
    fedilink
    arrow-up
    28
    ·
    1 year ago

    Everywhere I’ve ever been,

    If it’s lower than “High” or “2”, it’s as good as “backlog” :)

    (There can never be a priority “1” and seldom “Highest”, never “Blocker”, otherwise the CEO gets a text or something.)

    • jubilationtcornpone@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      28
      ·
      1 year ago

      Scrum Master: “Do we really have to make it a blocker?”

      Me: “Uh yeah. It’s blocking these three other tasks.”

      Scrum Master: “But is it really?”

      Me: “Yes.”

      Scrum Master: “Let’s just leave it on in development and we can review the progress tomorrow.”

      Me: “That’s what you said yesterday.”

      Scrum Master: “Alright guys. I’m going to give you back five minutes of your time today.”

      • dan@lemm.ee
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        Holy shit that’s too real. I come here to get away from work!

      • Carighan Maconar@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Don’t forget breaking everything up into ever-smaller tasks just so that something, anything, can be closed every day. 😂 Because the process matters, not the work.

    • FoxBJK
      link
      fedilink
      English
      arrow-up
      27
      ·
      1 year ago

      At every company I’ve worked at there were basically 3 priority levels - normal, stuff the client says is urgent, and the stuff that’s actually urgent. “We’ll fix it later” is basically for the week in December that everyone’s on vacation and the juniors have nothing to do.