We all knew it

  • Echo Dot@feddit.uk
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    I’ve seen it being done even on internal projects though. Things within an organization.

    It tends to be that they start developing a feature and then someone comes along and says, ooh wouldn’t it be nice if it did x, so they modify it to have x feature. Then someone decides it should be able to sync with Azure (there’s always someone that wants that), so Azure sync is added, but now that interferes with x, so that has to be modified so that it can sync as well. Then we get back to original product development which is now 3 weeks behind schedule.

    Repeat that enough times and you can see why a lot of this stuff fails.

    • jj4211@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 months ago

      Even internal projects have a facet of ‘milking customers’ even those customers are internal. There’s a rather large internal team that has managed to last years by milking the fact their stuff always sucks but any moment when they are challenged about their projects they always have a plan to fix all that’s wrong within ‘3 months’.

    • masquenox@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      During my project management days one of the things I learned the hard way is to nail down exactly what something has to deliver and getting everybody involved to sign onto it in black and white - if you don’t, disaster follows.

      Agile seems literally designed to make this impossible.