▲ 422 ▼ Study finds 268% higher failure rates for Agile software projects (www.theregister.com) submitted 2 years ago by ylai@lemmy.ml to c/programming@programming.dev 135 comments fedilink hide all child comments
[–] fruitycoder@sh.itjust.works 1 point 2 years ago (1 child) Never heard of UP, what is that? permalink fedilink source parent hideshow 2 child comments replies: [–] Carighan@lemmy.world 2 points 2 years ago Unified process, which, despite usually not being called that way and/or being codified in the way it is nowadays, is how virtually all early software companies did their development work post-punchcards (when you no longer had to get things done in a single step). It's why the "agile is better because iterative hoooo!" is so laughable, because even though we didn't yet call it iterative - as a distinction from pre-planned, since we thought in punchcards+mainframe vs after that - we did iterative work. Of course we did, software development is naturally iterative and Waterfall was the contrived contrasting example of how a non-iterative process would look. permalink fedilink source parent
[–] Carighan@lemmy.world 2 points 2 years ago Unified process, which, despite usually not being called that way and/or being codified in the way it is nowadays, is how virtually all early software companies did their development work post-punchcards (when you no longer had to get things done in a single step). It's why the "agile is better because iterative hoooo!" is so laughable, because even though we didn't yet call it iterative - as a distinction from pre-planned, since we thought in punchcards+mainframe vs after that - we did iterative work. Of course we did, software development is naturally iterative and Waterfall was the contrived contrasting example of how a non-iterative process would look. permalink fedilink source parent