• psud@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I loved agile as an analyst, we used to use waterfall and you’d hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs

      Also I absolutely love the job of scrum master which had no equivalent in waterfall

      • Lysergid@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.

        Not to mock you. My point is that methodology is not import when team consists from responsible professionals

        • gravitas_deficiency@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          There are some instances in which waterfall is not only entirely appropriate, but also the best possible choice in terms of work organization.

          There are some instances in which agile is the best fit. Likewise kanban.

          Different domains have different optimal workflows.