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

    According to the study, putting a specification in place before development begins can result in a 50 percent increase in success, and making sure the requirements are accurate to the real-world problem can lead to a 57 percent increase.

    Is this not self-evident to most teams? Of course you will not reach your destination if you don’t know where you’re going.

    • iamtherealwalrus@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      5 months 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
        16
        ·
        5 months 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
        11
        ·
        5 months 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
          9
          ·
          edit-2
          5 months 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!”

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        4
        ·
        5 months ago

        How did they know how to break things down into tasks? How did they know if a task would fit in a sprint? 😄

        • Kissaki@programming.dev
          link
          fedilink
          English
          arrow-up
          3
          ·
          5 months ago

          We’re so agile the sprint became a time-block framework rather than a lock-down of tickets that we certainly will finish. (In part because stuff comes up within sprint.)

    • floofloof@lemmy.ca
      link
      fedilink
      English
      arrow-up
      11
      ·
      5 months 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.