We all knew it

  • best_username_ever@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    Try medical software and devices. The requirements and specs are mandatory before doing anything. It’s actually very fun and I have less burnout thanks to this.

    • RagnarokOnline@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      I couldn’t disagree more.

      In medical I would end up being apart of endless retirement gathering meetings, then draft up the SOW doc only to have stakeholders change requirements when they were reviewing the doc. Then months later once the doc was finally finished and I could do the development, when UAT time finally came, they’d say the build wasn’t what they wanted (though it matched the written requirements).

      Most of the projects I saw executed in the last 4 years either got scrapped altogether or got bogged down in political bs for months trying to get the requirements “just right”.

      It was a nightmare. You could blame me, or the company, or bad processes all you want, but I’ve never had fun on a waterfall project, especially not in medical. (Though, in my opinion, we are severely understaffed and need like 4 more BAs.)

      • francisfordpoopola@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Do you think the problem is that the person driving the requirements doesn’t know what they actually want?

        I think a good BA is critical to the process because lots of end users have no idea how to put their ideas onto paper.

        I also think an MVP helps a lot because people can see and touch it which helps focus their needs.