Programming

17453 readers

102 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

422

Study finds 268% higher failure rates for Agile software projects (www.theregister.com)

submitted 5 months ago by ylai@lemmy.ml to c/programming@programming.dev

137 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] 1800doctorb@lemmy.world 24 points 5 months ago (1 children)

I’m curious what they mean by “failure.” I read the article but didn’t get a clear definition. Isn’t one of the expected outcomes of agile the ability to experiment rapidly and move on when the experiment fails?

So what if you fail 300% more? If you’re able to get 300% more ideas to the stage where you can test their viability, then it’s a success.

[–] themusicman@lemmy.world 2 points 5 months ago

Exactly. Agile is basically guaranteed to deliver something.

The real question is how fit-for-purpose is the resulting product.