We all knew it

  • francisfordpoopola@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    5 months 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.

    • RagnarokOnline@programming.dev
      link
      fedilink
      English
      arrow-up
      14
      ·
      5 months ago

      I would say yes, the problem is stakeholders not having thought critically about what they really wanted from the project.

      The motivation for projects were usually “regulatory told us we need to have this new metric for federal reporting”, or “so-and-so’s company can do this, why can’t ours” rather than, “we’d like to increase retention by 6% and here’s the approach we’ve researched to make that happen”.

      I ended up experiencing that people in the highest positions weren’t experts in their field, but just people who had a strong intuition. This meant they would zero-in on what they wanted by trial and error rather than logic. Likewise, it meant they were socially adept enough so their higher-ups would never get mad at them when we finished “late and over budget”. People lower on the totem received that blame.

      I think humans are just really bad at estimating and keeping their commitments, which is why I enjoy working with agile more. It’s a forgiving framework (imo).