• eendjes@feddit.nl
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      1 year ago

      I get that at work too and often it’s a trust issue. The other fella could get it done faster, but could he get it done equally well? Support time will eat future development time.

  • Naia@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    20
    ·
    edit-2
    1 year ago

    I’ve always tried to estimate more time than I think a task will take unless I know it’s only like a simple task.

    If I think it will take a few hours, I estimate a day. A day or so is 3. 3 or more becomes a week.

    I’ve ran into way to many tasks somone else blindly put at a day and when we start to work the ticket we descover a ton of complications. I’ve seen so many 1-3 point tickets I’ve seen take multiple weeks because nobody thought about how deep the rabbit hole could go.

    • TheGreenGolem@lemm.ee
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      I also really like when they ask for an estimate on brand-new tech. How much time? I really, truly don’t know, because I’ve literally never worked with it in my life, nor anybody at the company. It could take 2 days or 2 weeks. Let’s just say I’ll tell you when I’m finished.

    • oce 🐆@jlai.lu
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Ideally, tell them it will take 3 times your estimate and do it in 2 times your estimate. You’ll either look fast or correct.

    • KevonLooney@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      That’s a rookie move. 2 hours can easily turn into 8 hours. If that happens, you still have to work on other things too. For a two hour task estimate a week. Two weeks to test and fix it when it breaks.

    • Ser Salty@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Always multiply your estimates by a factor of 4, so you can gain a reputation as a miracle worker

    • Unaware7013@kbin.social
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      Engineers: We need more accurate SOWs and less feature creep.

      Management: Please add this other feature in the same time period

  • Blapoo@lemmy.ml
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 year ago

    Never give firm estimates. It’s done when it’s done. Feel free to check in.

    • hemko@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Customers kinda want to know in advance if a task will take 2 hours or 200 hours in advance

    • SokathHisEyesOpen@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      As someone who has been doing this for two decades, I disagree. Give a firm estimate, and always deliver before you said you would, just make sure you pad the fuck out of that estimate so that it would be virtually impossible not to accomplish it.

    • CosmicTurtle@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      My favorite is when project managers try to tell you it will be easier with more people.

      For some things that’s true.

      But for some, it really just takes a while.

      I tried to explain to a PM that maybe we should ask his wife next time if she can split up her pregnancy between two women. Baby could be born in half the time.

      He didn’t appreciate my feedback and wrote me up for it. Probably my proudest moment.