• @dragnucs
    link
    22 years ago

    While this is true for a few projects I would disagree. This highlight that the team is misusing the agile method. Agile helped many of the projects I experienved to deliver and act fast to deadlocks and unexpected issues.

    • ☆ Yσɠƚԋσʂ ☆OP
      link
      52 years ago

      My experience with agile is that it often simply creates a different set of problems. In particular, I find that agile tends to encourage short term thinking where people primarily focus on short term deliverables without considering the bigger picture. This often results in projects growing organically like a ball of mud.

      • @personwithakeyboard
        link
        4
        edit-2
        2 years ago

        Agile makes sense from the POV of the startup entrepreneur - make it work just long enough for the investor money to come in or for the first wave of idiots to buy the product.

        Then you ride that for as long as you can while maintaining a POS product that gets more and more difficult to manage and finally you get bought by a big company or go bankrupt.

        As capitalism reaches its final days, the cycle of “get money, make money our of bullshit, go bankrupt” increases in speed. Agile is a consequence of that.

        • ☆ Yσɠƚԋσʂ ☆OP
          link
          02 years ago

          Yeah, that’s basically how software development works in the industry.

      • @dragnucs
        link
        12 years ago

        Scrum is not intended for long running products. It is intended for product mode, where you get an 8 to 12 months or so of build phase–prior planing required–then you switch to a more relaxed way of development.

        At $EMPLOYER we have three phases:

        1. Build
        2. User Acceptance testing
        3. Maintenance

        All of them are agile but are different enough to be adapted to product phase.

        • ☆ Yσɠƚԋσʂ ☆OP
          link
          02 years ago

          Thing is that you generally don’t know how big or how long lived a project will get in practice. I’ve worked with lots of projects using scrum before, and early decisions to solve short term goals often cut velocity later on as the project started getting more complex.

          So, yes short feedback loop is good, but it needs to be combined with larger scale planning as well. Somebody has to think about the bigger picture and see how each sprint fits into it.

          • @dragnucs
            link
            02 years ago

            Well this does not prove we should avoid scrum. One needs to think and plan before jumping. However, if knowledge about the project is small, then maybe, something agile is required.

            • ☆ Yσɠƚԋσʂ ☆OP
              link
              22 years ago

              I’m simply pointing out that agile isn’t the silver bullet people make it out to be. It carries a different set of trade offs from waterfall, and can often lead to a different kind of mess. Having short feedback loops is obviously good, and I’m not arguing against that anywhere.

              What I’m saying is that short term goals have to be balanced against long terms ones and it’s important to keep the bigger picture in mind. Scrum doesn’t account for this problem.