• iamtherealwalrus@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      2 years ago

      On all the agile projects I’ve worked on, the teams have been very reluctant to make a specification in place before starting development. Often claiming that we can’t know the requirements up-front, because we’re agile.

      • lysdexic@programming.dev
        link
        fedilink
        English
        arrow-up
        12
        ·
        2 years ago

        On all the agile projects I’ve worked on, the teams have been very reluctant to make a specification in place before starting development.

        I don’t think this is an Agile thing, at all. I mean, look at what Agile’s main trait: multiple iterations with acceptance testing and product&design reviews. At each iteration there is planning. At each planning session you review/create tickets tracking goals and tasks. This makes it abundantly clear that Agile is based in your ability to plan for the long term but break/adapt progress into multiple short-term plans.

      • pivot_root@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        2 years ago

        For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen.

        • kippinitreal@lemmy.world
          link
          fedilink
          arrow-up
          8
          ·
          2 years ago

          Also seems like a shitty get-outta-jail-free card. With no design in place, timelines and acceptance criteria can’t be enforced. “Of course we’re done now, we just decided that we’re done!”

    • floofloof@lemmy.ca
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 years ago

      On the other hand you can just call wherever you end up the destination, and no one can prove you wrong. 100% success rate.