this post was submitted on 06 Jun 2024
476 points (89.3% liked)
Technology
59589 readers
3332 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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...
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)