• @Underwire@lemmy.world
    link
    fedilink
    724 days ago

    When I started working for my current company there were really few meetings and I didn’t know that it was possible. Everywhere I worked we had all the Scrum meetings and tech discussions meetings. At that time it was relatively a small company but not that small.

    Now the company is getting bigger and some persons try to bring all the scrum shit. Even for small features, we do meetings to discuss them and last for hours. Some meetings have a big agenda that we always only tackle half of it. Sometimes we decide to do something with big impact and then someone suggests to include a person from another that doesn’t even know our scope. And then we get “maybe we shouldn’t do this as it will maybe have some negative impacts”, “maybe we should add an exception” without even giving data to support their claim.

    • @spooky2092@lemmy.blahaj.zone
      link
      fedilink
      English
      824 days ago

      It all depends on how time tracking is implemented.

      Tell me I have to account for my time in 15-30 min increments? Fine, I can put it into a spreadsheet and track it.

      Tell me I have to track real time spent? Get entirely fucked, and I hope you’re ok with spending time fixing my time punches because I absolutely am going to forget to open or close a time entry because I’m working on 3-4 tasks at any given time.

      I’ve done both, and while I won’t intentionally sabotage the latter, my rampant ADHD and terrible memory have got my back on that one.

    • @smeg@feddit.uk
      link
      fedilink
      English
      324 days ago

      Yeah but that can be done after you’re finished, definitely shouldn’t be part of planning!

    • λλλ
      link
      fedilink
      323 days ago

      Disagree. My company does it well and I think it helps productivity across the board. My last job called our process agile and it was really just water-scrum-fall. Which was horrible and we devs were all miserable.

      • @thatradomguy@lemmy.world
        link
        fedilink
        121 days ago

        My experience with it was not like that… resources were thin but decision makers were poor at managing and simply wanted to take in the buzz to make it seem like they were doing better than they actually were. They could’ve made another Office Space movie about us. Needless to say, it’s no surprising the CTO left and later on the top division chief left… all the while, management kept putting pressure on making sure we fulfilled the caveats of agile/scrum even though we didn’t have the bandwidth to do all of it. Documentation is important, sure, but when management makes everything a P1 just cuz they failed to see things though… well, don’t find the time to put everything down in the kanban… yada yada yada. No thanks

        • λλλ
          link
          fedilink
          121 days ago

          But, is that a problem with Agile or with your company? That’s my point.

    • @TexasDrunk@lemmy.world
      link
      fedilink
      1124 days ago

      Right? Minute 55-60 is the 15th minute. Fuck that. If it takes that long then the team is too big for agile or the scrum master had lost control.

    • Pika
      link
      fedilink
      English
      224 days ago

      are you sure it’s not blackout? lmao

      • @smeg@feddit.uk
        link
        fedilink
        English
        324 days ago

        Is “blackout” a bingo term for filling every box, or just falling unconscious from overwork?

        • Pika
          link
          fedilink
          English
          224 days ago

          I was meaning filling every slot but that works too!

  • magic_lobster_party
    link
    fedilink
    2124 days ago

    ”All features are xy problems”

    ”PM adds new features to the sprint faster than they’re solved”

    ”Each release require two weeks of testing”

    ”Each release introduces new bugs for customers despite the two weeks of testing”

  • @rational_lib@lemmy.world
    link
    fedilink
    12
    edit-2
    23 days ago

    Let’s not forget “We need this right away!” then it takes weeks to deploy because the people who requested it weren’t actually ready for it yet (if they don’t change their mind and decide they don’t actually want it at all).

    • @spooky2092@lemmy.blahaj.zone
      link
      fedilink
      English
      324 days ago

      That’s what I do at work, even though I’m salary.

      Management decided to hire a new guy and then have a round of layoffs within 6 months, effectively canning someone to replace him. Since then, we’ve had multiple times where we have hundreds of tickets sitting unassigned because there’s more work than people. So shit sits and falls through the cracks until someone has time or something is on fire.

      It fucking sucks, but eventually the bean counters will see that we actually needed that extra body…

      • @Korhaka@sopuli.xyz
        link
        fedilink
        English
        324 days ago

        We did have well over 100 tickets in the queue, now they split the support team into multiple sub support teams and each sub team has fewer tickets in their own queue. The total number is still massive but compartmentalising the problem makes most of it go away! I can filter it down to such a degree my queue is almost single figures by just ignoring everything else because that is someone elses problem.

        Also my sub team doesn’t have anyone to cover 1st line on some products so I am covering 1st line there as well as 2nd line. Upside is my stats look brilliant now that I am doing all the password reset tickets.

    • Squiddlioni
      link
      fedilink
      2624 days ago

      It’s me, I do it. But only when I need something to do to stay awake in hour five of today’s meetings to address the “quick turnaround” patch that I finished coding three weeks ago, but now they want a label to change and no one on the six teams that have somehow become involved seems to know who owns the package that the field the label represents belongs to, but they’re absolutely certain we need to programmatically retrieve the text in case the package owner changes it at some point, and someone remembers that the original developer wrote code to get the label text 16 years ago, but it was removed from the program two years before the project started using source control, and they have an old installer around here somewhere that we can decompile or trace with Wireshark to get the right RPC name (sharing their screen while they have a rummage for it, natch), and someone else volunteers that they might know how to get a version of the server application from around that time since the client and server versions have to match, but it’s technically the intellectual property of a different subcontractor who was just a guy in Alaska who passed away five years ago, but they’re sure they can convince his estate to burn it to a disk and mail it to me if they can just find the contact information…