We all knew it

  • chakan2@lemmy.world
    link
    fedilink
    English
    arrow-up
    41
    arrow-down
    2
    ·
    edit-2
    5 months ago

    Pbpbpbp…agile fails fast by design.

    The counter from the article is you need a specification first, and if you reveal the system wasn’t going to work during requirements gathering and architecture, then it didn’t count as a failure.

    However, in my experience, architects are vastly over priced resources and specifications cost you almost as much as the rest of the project due to it.

    TLDR…it’s a shit article that confuses fail fast with failure.

    • MechanicalJester@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      5 months ago

      Thanks for pointing that out so I didn’t have to.

      What’s the alternative? Waterfail?

      Yeah because business requirements and technology is changing at an ever slower rate…

    • bionicjoey@lemmy.ca
      link
      fedilink
      English
      arrow-up
      8
      ·
      5 months ago

      Fail fast is the whole point and the beauty of agile. Better to meet with clients early and understand if a project is even workable rather than dedicating a bunch of resources to it up front and then finding out six months in (once the sunk cost fallacy has become too powerful)